The Code suite
Ship software without leaving the workspace — and let your agents work where your team does.
The whole loop, in one workspace
Host the repository, edit it, run it, ship it and watch it — without leaving the place your team already works.
Host itRepositories live in the workspace, with the same permissions as everything else in it. No separate account, no separate access list.Edit itA browser editor backed by Jujutsu rather than raw Git. Every keystroke is already tracked, so there is nothing to stage and nothing to lose.Run itIsolated execution with real language runtimes, on the same machines the rest of your work runs on.Ship itBuild an image from a Dockerfile, then run it. Both are resources with a defined lifecycle, not a script someone wrote once.Watch itTraced from the first request. Keys, projects and usage are in the console next to everything else.Four decisions worth knowing about
Jujutsu, not Git porcelain
The editor is built on Jujutsu. There is no staging area and no explicit save — the change you are working on is always recorded, and you describe it when you are ready. Work in progress cannot be lost, and a session can be started from any commit and pushed back. It reads your existing Git history, and it works against repositories hosted here or on GitHub.
Machines with a real lifecycle
An image goes draft, queued, building, ready — and a machine has its own states on top of that. Every transition emits an event, so the interface knows which buttons to enable and the history of what happened is recorded rather than inferred from logs.
Our own compute, not a reseller
The worker agent that builds images and runs virtual machines is ours: Firecracker microVMs on dedicated European hardware, with the image built from a Dockerfile, exported to a filesystem and stored as an artifact. Nobody is between you and the metal.
Agents work here the same way you do
An editing session is addressable, so an agent can open one, read the tree, write files and describe its change — without knowing anything about Git. It gets a scope, and what it did is in the same history as what you did.
Where it stands
Honestly, because you will find out anyway.
Reached the same four ways
Every pipeline, every thread, every ticket.