Roadmap
& Vision.
Direction — April 30, 2026
We are showing the roadmap to everyone using Drift now. The product is still early, but the shape of the system is getting much clearer. See what is live today, what is experimental, and what is planned for the 1.0 launch.
Request Feature01 / v0.50 beta
What exists now
Drift is still in its early beta stage, with core systems live and several new ideas already available behind experiments.
LifeOS is the personal operating layer for goals, energy, health, and relationships, with memory for the people and commitments you want Drift to keep track of.
Thinkspace is an experimental distillation layer for thinking, synthesis, and collecting loose material while we test how it fits into the wider system.
Anchor is now capable of handling dashboard changes and management requests more directly from conversation.
02 / Toward 1.0
What is coming next
The next milestone is a wider platform release supported by stronger infrastructure and deeper product logic.
Desktop and mobile apps are planned for the 1.0 launch target on April 30, 2026.
The intelligence layer is being upgraded so the system is not just plain AI output, but also backed by stronger product logic and algorithmic structure.
Import paths from other note and node-based tools are in progress so migration into Drift becomes much easier.
03 / Migration
Infrastructure shift
We are moving the product from a rough beta setup into something that can support real work with less friction.
Hosting is moving from a dedicated server setup toward a more production-grade serverless environment.
Vector-backed memory infrastructure is being hardened so migration stays seamless as 1.0 gets closer.
For v1.0, Drift is planned to move off third-party models and onto in-house models that are fine-tuned and trained specifically for Drift.
04 / Paid users
Access and feedback
Once Drift is out of beta, access is expected to move fully behind the paid plan because of inference costs and infrastructure overhead.
Paid users can contact the developers directly to request or push for features they need most.
Experimental features will keep changing while we test names, flows, and what deserves to survive into 1.0.
The long-term direction is for Drift to manage past context, present work, and eventually more future-facing planning in one place.