Sandboxes get pay-as-you-go and a bigger free tier
orkestr sandboxes now run on their own pay-as-you-go tiers, the default small box doubled to 1 GB of RAM, and the free tier runs two at once.
orkestr sandboxes don’t ride your platform plan anymore. As of today they have their own tiers, their own pay-as-you-go billing, and a bigger default box. If you just want somewhere to run agent-generated code, you no longer need a deployment subscription to get the good version.
Their own tiers, not your platform plan
Sandbox limits used to be tied to whether you were on a platform plan. That never quite made sense - someone who only wants to run untrusted code shouldn’t have to buy a deployment plan to get there. Now sandboxes stand on their own, and the tier comes down to one thing: whether you have a card on file.
No card is the free tier - verify your email and go. A card on file unlocks pay-as-you-go and higher ceilings. No platform subscription required either way.
Pay-as-you-go, past a one-time credit
Compute is metered per second on the vCPU and RAM a sandbox actually uses. A small box runs about €0.06/hour while it’s awake, and a paused sandbox stops the clock entirely and it counts to your storage.
Everyone starts on a one-time credit, not a monthly bucket:
- Free gets €10 to spend. It’s time-boxed to one month - when the window’s up, add a card to keep going.
- With a card you get €100 which isn’t on a clock. You spend it down at your own pace and only then move to metered pay-as-you-go.
Bigger boxes, more of them
The default small sandbox doubled. It’s now 1 vCPU and 1 GB of RAM, up from 512 MB. Half a gig was tight for real work - a dependency install plus a headless browser would blow straight past it. 1 GB clears most of that.
Free also runs more at once: two small sandboxes live at the same time, up from one. Medium (2 vCPU / 4 GB) and large (4 vCPU / 8 GB) stay on the card-on-file tier.
Everything else is the same
Same isolation - each sandbox is its own virtual machine on EU hardware in Germany and Finland. Same network controls (off, allowlisted, or open). Same pause and resume. Same SDKs and MCP server. If you’re new to the idea, here’s what a managed sandbox actually is; the full breakdown lives on the pricing page.