Fast enough to throw away.
Durable enough to keep.
Your files, caches, and git history stay put. The compute under them is spun up on demand and replaced freely, so losing it costs nothing.
Three steps. No infrastructure to manage.
Create a cella, run your work, then walk away. Come back to exactly where you left off.
From the dashboard, the CLI, an API call, or your agent. Ephemeral self-deletes on a deadline; persistent survives every stop.
Run a command, open a terminal, stream logs. Secrets arrive as files; every command is logged to the account behind it.
$ latere cella exec bird-7x2
-- go test ./...
ok ./... 0.42sGoes idle? Compute stops on its own; the workspace stays. Come back tomorrow to the same shell, or delete it and it is gone.
Separate what is durable from what is replaceable.
The workspace stays. Compute attaches on demand and cycles through its life, so losing it costs nothing.
The workspace stays. Compute attaches on demand and is replaced freely, so losing it costs nothing.
Functions are too short. Machines are too much.
Cella sits in between: a workspace you keep, on compute you can throw away.
Dies the moment the call ends. No room for a ninety-minute test matrix or an hour-long agent run.
Always on, and yours to run, patch, and pay for, whether or not anything is happening on it.
Starts in about 300ms, stops itself when idle, and keeps only the workspace that is worth keeping.
The key never enters the sandbox.
Your agent holds an opaque placeholder. The real secret is swapped in at the egress edge — and only for the hosts you allow. Sent anywhere else, the placeholder is worthless.
Substitution fires only toward a credential’s allowed hosts. A leaked placeholder exfiltrates nothing.
Locked down by default.
An allowlist travels with every cella. It starts closed; an admin opens only the hosts you need.
One record of every action.
Every command, secret read, start, and stop, recorded against the account behind it.
One workspace, three ways in.
Create, run, and manage the same cella from the browser, your terminal, or the public API.
Create a cella, run a command, leave, and come back.
The CLI and public API are both live. Start in the dashboard for the shortest path, or install the CLI when you are ready to automate.