Releases & roadmap

Scellis has not shipped a public release yet. The studio is in development, and this page carries no version history because there is none — the first release will start it, and every one after that will be listed here with what it changed.

What the page carries instead is the roadmap: what has to become true, in the order it has to become true. There are no dates on it. A date on a roadmap is a promise about a future you do not control; the order is the part that can actually be kept.

Where things stand · Today#

The engine is built and continuously verified. Workflows, training on your own GPU, the reference-checked correctness regime, the local database, versioned and citable results, workspaces and live co-editing sessions all exist and are exercised on real hardware. Pooled compute across devices is in active bring-up: its coordinator — exactly-once leases, independent re-execution, receipts — is implemented and tested, but no browser has yet run a pooled shard end to end. Built and reachable in the studio, though not yet released: charts and viewers, access for external AI agents over MCP, the first-run template gallery, and citing and embedding a finished run.
The studio is not open yet. No public release has shipped, so this page has no release history to show — and will not pretend to one. The first release starts it.
What we will not do: ship a capability here before it works. Where a surface is still being built, the pages that describe it say so (the honest limits collect the ones that will never go away).

Being built now · In progress#

Seeing your results — the last pieces. Charts and live viewers are first-class, versioned, forkable content — the same thing a block or a model is, so a figure can be shared, forked and cited like any other result; the remaining viewer work is landing now.
The AI assistant you already use, driving Scellis. External agents reach the platform through the same commands the interface uses, under the same consent rules — and, like the built-in Copilot, they can never spend your money. The connection is built; its final hardening pass is under way.
Connectors that come to you. An inbox and triggers: a file landing in your storage or a message arriving is meant to start a run you approved in advance (how data gets in and out). The inbox and arming a trigger are built; an armed trigger does not yet start its run. Storage and messaging connectors reach the address you approve from a release build, through a sandboxed frame that can reach that address and nothing else.

When the doors open · Next#

Early access. The studio opens to the first users. Computation stays free and unbounded, with or without an account — that is a structural rule, not an introductory offer.
The services switch on. Hosted sync, sharing, live sessions and compute-pool coordination arrive with the paid plans; the marketplace opens with the owner as the first seller.
We publish what does not work yet, too. Every capability page that describes a surface still in development says so on the page itself, and keeps saying so until it is true.

Named, but not yet · Later#

Selling as a user. The marketplace mechanism is already seller-agnostic, and a "become a seller" application is reachable from inside the app. Payouts wait for the operational machinery around them — identity checks and escrow — not for a change in the engine's licence.
Organisation sign-in. Single sign-on and seat provisioning, for institutions that cannot hand out individual accounts.
Persistent identifiers. A citable result already carries its content hash; minting a DOI for it is a step further, and it is not taken yet.
What is deliberately not coming: runs that continue on our servers while your tab is closed. Local compute lives in your tab. We would rather say that out loud than sell you a cloud you did not ask for.

Wondering whether you can use Scellis today, and how to hear when you can? The FAQ answers exactly that. And the limits that will still be there after every phase on this page are collected on honest limits.