Aller au contenu

Roadmap

Roadmap

Maia Cloud will run Maia OS for organizations that would rather not operate it themselves. This page lists what comes next, in order. Dates are targets, not commitments, and every Maia Cloud milestone is planned.

Targets

What we aim for next. A target is a goal we are working towards, not a promise.

  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.

    Prévu

  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.

    Prévu

  3. February to March 2027

    Design partners

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

    Prévu

  4. No date

    Public launch

    General availability waits for its evidence gates.

    Prévu

Maia Cloud milestones

Each milestone depends on the one before it. Maia Cloud has no tenant feature yet, so every milestone reads 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.

    Prévu

  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.

    PrévuTarget: 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.

    Prévu

  4. Public launch (GA)

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

    Depends on: C4, and the gates below.

    Prévu

Gates to the public launch

The public launch follows these gates, in this order. Each one needs evidence before the next begins.

  1. Design-partner letters of intent
  2. A self-hosted licence
  3. A managed pilot
  4. Invited paying customers
  5. General availability

Agent computers and model sign-in

Two capabilities shape the private alpha and the design-partner phase. Both are planned; neither exists yet.

  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.

    PrévuPriority: 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.

    PrévuPriority: ShouldTarget: Design-partner phase, February to March 2027

Maia OS delivery plan

Maia OS is the software Maia Cloud will run, and it is in private alpha. These phases overlap: a piece starts once what it depends on holds. Every item shows its status word.

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

  1. Finish the foundation

    • Acceptance closure and source organizationPrévu
    • Measurement of the work Maia doesCandidat implémenté depuis les sources
    • Portfolio reads and persistent Workspace conversationsPrévu
    • Open coordination work between SessionsPrévu

  2. Enterprise foundation

    • Vulnerability disclosure and supply-chain controlsPrévu
    • Grants per Workspace and ProjectCandidat implémenté depuis les sources
    • Contained execution of vendor harnessesPrévu
    • Usable local executionPrévu

  3. Workflows

    • AgentsPrévu
    • Routines and event triggersPrévu
    • Tasks and goalsPrévu

  4. Evaluation and learning

    • Reusable evaluationPrévu
    • Scorers and routersPrévu
    • Datasets and custom modelsPrévu

  5. Execution at scale and operations

    • Server setupPrévu
    • Execution Nodes and a pool of local and remote workersPrévu
    • Session capsPrévu

  6. Human layer

    • Web clientPrévu
    • Personal agentPrévu

  7. Distribution and release

    • Signed releases with provenancePrévu
    • Seamless updatesPrévu
    • Windows CLI and SDKPrévu
    • Self-managed deployment recipesPrévu

  8. Later

    • Messaging between organizations, with no shared authorityPrévu
    • More chat connectorsPrévu
    • Governed browser and computer usePrévu
    • Short-lived Execution Nodes from an operator-run provisionerPrévu
Read the full Maia OS plan

We recruit design partners from the requests for the private alpha.

Request access