Free to start. Speak to us for the rest.
Managed machine time is counted in credits; runtimes on your own hardware cost nothing. Paused workspaces cost their disk and no more.
Free
One person, or a small team finding the shape of it.
- 30,000 credits of managed machine time a month
- Up to 3 people and 3 projects
- 1 workspace at a time on managed runtimes, 2 on your own launchers
- Machines up to size m
- Idle workspaces pause after 30 minutes
- Every agent, every template, the app, the CLI and MCP
Enterprise
An organisation that needs more room, or its own infrastructure.
- Everything in Free
- More people, projects and workspaces running at once
- Larger machines, up to a whole xl
- Your own Kubernetes clusters as runtimes
- Optimised templates that launch from a captured disk
- Longer idle windows and workspace lifetimes
smedja is in early access: sign-in is by invitation, and nothing is billed yet.
Questions people actually ask
What is a credit?
One unit of machine for one minute. The smallest size is one unit, so a credit is a minute of it; larger sizes are multiples. A paused workspace costs a little for its disk. Runtimes on your own hardware are never charged.
What happens when credits run out?
New launches on managed runtimes are refused, and workspaces already running carry on through a short overdraft before they pause. Nothing is wiped, archived or erased for credits, and your history is never behind a balance.
Who pays for the model?
You do, directly: every agent runs on a credential you add — a Claude subscription, or an Anthropic, OpenAI or Gemini key. Tokens are billed by your provider and never counted here.
What happens if someone leaves?
The workspaces they sponsored pause with the reason attached, and a project admin can take them over. Nothing is deleted by a removal.