QodariumRoadmap & release gates
The sequence matters: prove the personal workspace, validate small-team collaboration, then turn repeated value into a supported product.
On this page
From a useful foundation to a sustainable product
Community Alpha
Validate the core loop: project setup, Codex sessions, files, terminal, worktrees, history and understandable failure states.
Community Beta
Improve installation, updates, recovery, backups and documentation through repeatable use on real projects.
Team Alpha
Validate shared projects and history, simple membership, handoff acceptance and the review loop with small teams.
Team Beta
Test the remote-access and operational experience, including relay, PWA, push and support expectations.
Paid validation
Confirm that teams repeatedly use and value the collaboration workflow before scaling commercial packaging.
What success needs to demonstrate
A developer should be able to start useful work, leave it, return with the context intact and understand the result. A teammate should be able to accept a handoff without reconstructing the entire task.
Installation, upgrade and recovery quality are part of that result. The workspace has to remain understandable when the happy path breaks.
What is deliberately outside the first scope
The initial direction does not include enterprise identity systems, a large role hierarchy, general production deployment orchestration or stable support for every agent runtime.
Additional runtime integrations should earn a release gate through verification rather than appear as unqualified logos on the landing page.
Keep up with the build
Read the journal, subscribe to RSS or follow Qodarium on Threads. Concrete release information belongs in a versioned announcement and its associated documentation.