Roadmap

1. January 2027

   Maia OS ready on canary

   The Maia OS capabilities that the private alpha needs are ready to run from a canary build.

   planned

2. January 2027

   Maia Cloud private alpha (C3) with a first private-alpha tenant

   Accounts and organizations, then the console for the first private-alpha tenant, who runs managed Nodes.

   planned

3. February to March 2027

   Design partners

   We recruit design partners for Maia Cloud, starting from the requests for the private alpha.

   planned

4. No date

   Public launch

   General availability waits for its evidence gates.

   planned

1. Hosting (C2)

   The infrastructure that Maia Cloud will run on: tenant machines and sandboxes, EU regions first, backups, monitoring and incident response. Its owner builds and operates it apart from the console, and Maia Cloud connects to it through an agreed contract.

   Depends on: The hosting infrastructure and its owner.

   planned

2. Private alpha (C3)

   Accounts and organizations, then the console for the first private-alpha tenant, who runs managed Nodes. It covers tenant provisioning and decommissioning, the first-owner bootstrap, compute choice in the console, export and restore, restore drills, and support access only with the customer's approval, and the first always-on agent computers (see Agent computers and model sign-in below).

   Depends on: C2, and the Maia releases it relies on.

   plannedTarget: January 2027

3. Commercial and payments (C4)

   Plans, seats, billing and payments, and the legal texts that go with them: the terms, the privacy policy, the processor agreement and the subprocessor list.

   Depends on: C3.

   planned

4. Public launch (GA)

   Public launch happens when its evidence gates pass. No date is set.

   Depends on: C4, and the gates below.

   planned

1. An always-on computer per agent

   Each agent gets its own computer that keeps its files and state. It sleeps when idle, which aims to cut idle compute cost, and wakes on a message or a schedule. A person from the tenant can watch it live, take over, then hand it back. Each takeover leaves an audit entry (who, when, which agent) in the control plane; what was on screen stays in the tenant's environment. The first version, with C3, keeps state, stops when idle, starts on a message and allows live takeover. Waking on a schedule and resuming without a cold start follow in the design-partner phase.

   Depends on: C2 tenant machines with a start, stop and wake contract; Maia OS contained execution of vendor harnesses, then routines and event triggers for schedules.

   plannedPriority: MustTarget: First version with C3, January 2027; schedules and fast resume February to March 2027

2. Bring your own subscription

   Each tenant signs its agents in with its own Claude or ChatGPT plan instead of an API key. The sign-in stays in that tenant's environment, and Maia Cloud never resells or pools model usage.

   Depends on: The always-on computer above, per-tenant secret storage, and each provider's terms for using its plans this way.

   plannedPriority: ShouldTarget: Design-partner phase, February to March 2027

Maia ships canary builds, and no stable release is planned.

1. Finish the foundation

   • Acceptance closure and source organizationplanned
   • Measurement of the work Maia doessource-implemented candidate
   • Portfolio reads and persistent Workspace conversationsplanned
   • Open coordination work between Sessionsplanned

2. Enterprise foundation

   • Vulnerability disclosure and supply-chain controlsplanned
   • Grants per Workspace and Projectsource-implemented candidate
   • Contained execution of vendor harnessesplanned
   • Usable local executionplanned

3. Workflows

   • Agentsplanned
   • Routines and event triggersplanned
   • Tasks and goalsplanned

4. Evaluation and learning

   • Reusable evaluationplanned
   • Scorers and routersplanned
   • Datasets and custom modelsplanned

5. Execution at scale and operations

   • Server setupplanned
   • Execution Nodes and a pool of local and remote workersplanned
   • Session capsplanned

6. Human layer

   • Web clientplanned
   • Personal agentplanned

7. Distribution and release

   • Signed releases with provenanceplanned
   • Seamless updatesplanned
   • Windows CLI and SDKplanned
   • Self-managed deployment recipesplanned

8. Later

   • Messaging between organizations, with no shared authorityplanned
   • More chat connectorsplanned
   • Governed browser and computer useplanned
   • Short-lived Execution Nodes from an operator-run provisionerplanned