Roadmap

Now, next, later.

What is shipped, what is coming soon, and what we intend. Three columns, no dates, no quarters. The changelog records what actually landed; this page says what we are working toward.

now

Shipped

Live today. Each card links to the page that explains it.

License

One organization license, unmetered

Every builder, every app, every environment — including live apps serving end users. No tokens. No credits. No meter. You bring the AI subscription you already pay for.

How it works
MCP

The control surface: approximately 100 named operations

Authenticated on every request; the agent acts with your permissions; edits are staged, previewed as an entity-level diff, committed once, or rolled back.

How it works
Environments

Dev, staging, production

Custom frontends promote develop → staging → production one way, under owner / editor / viewer roles, with non-destructive rollback. Platform apps publish Current → Testing → Production in one step.

How it works
Custom frontends

Vite/React through the same pipeline

When the renderer is not enough: a standard repository, a seven-phase build, static output, the same environments and audit trail as everything else.

How it works
Custom backend functions

Server-side code for custom frontends

Functions run server-side alongside a custom frontend: a curated package allowlist rather than an open registry, sandboxed workers with a dry-run check before anything runs, and short-lived, tenant-scoped invocation tokens so a function reaches only the data its caller can. Agents create and manage them through the same named, authenticated operations as everything else.

How it works
Desktop app

Desktop installers for Windows and macOS

Windows and macOS builds are ready and handed over when an invite is approved — there is no public download link while access is invite only. A Linux build is not ready yet.

How it works
Security hub

Receipts for the person who has to say yes

Architecture, data and tenancy, governance and audit, compliance status as it stands, and a disclosure process — each claim mapped to a mechanism.

How it works
How to ask for something

Tell us what you are trying to ship.

The most useful request names the app, the step where the platform stopped you, and what you did instead. Send it through the contact form with the support topic; if you were building through your agent, include the operation you called and the exact error text. Requests are read by the people who build the platform.

How to read this page

Shipped means linked.

  • Now links to a live page. If it is here, it works today and the page shows how.
  • Next carries a roadmap badge and no date. When it ships it moves to Now and the changelog records it.
  • Later is intent. Things can leave this column as readily as they arrive.
  • There is no tier column. Today there is one organization license, and it is not metered.
Invite only · early access

Bring us something you want built.

CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive. You bring the AI subscription you already pay for.