Sandbox
Your code, running only when something needs it.

Your code, running only when something needs it.

Deploy a container and get an address that always works. It starts when a request arrives — or when a player joins one of your servers — and stops again when nothing is happening.

Request an inviteRead the docs
SandboxAvailable now

This includes:

  • An address that works whether or not anything is running
  • Starts on a request, or on a player joining one of your servers
  • Every deploy kept, and one click back to it
  • Secrets fetched at launch, never baked into an image
Drawn from your plan’s creditPricing

Starts when a player joins

Attach your code to something that actually happens in your game. Somebody joins, a server goes quiet — your container runs, and you did not have to keep anything listening for it.

A trigger on your lobby — have somebody join

on-joinActive
Failed deliveries 0

When

A player joins

On

lobby

POST to

/hooks/player-joined
PlayerDeliveryTook
No deliveries yet

Nothing is running and nothing is listening. Have somebody join the lobby.

Nothing running, nothing charged

A quiet afternoon costs nothing. The address keeps working, and the first request that arrives starts it again in seconds.

A sandbox scaled to zero — send it something

match-resultsScaled to zero
https://match-results-7k2q.eu-west-2.plany.run

Instances

0

of 3 · 1 vCPU · 512 MiB

Held at the edge

0

waiting, not refused

Served

0

none failed

not running
not running
not running

Nothing is running and the URL still answers. Send it something.

Roll back to what was working

Every deploy is kept exactly as it was, down to the image it actually ran. Going back is picking one, not rebuilding it and hoping.

Revisions — the latest deploy failed

rewardsServing r-003 · latest deploy is not serving
RevisionStateImageDeployed
r-004Failedv49c1e04b7a2d3…4 min ago · ci@arcade
r-003Readyv34be7f10c93a8…2 days ago · ci@arcadeServing
r-002Readyv2d02a6e91f4c7…9 days ago · sam@arcade
r-001Readyv171f3c8a0e5b2…3 weeks ago · sam@arcade

v4 failed to start, so v3 never stopped serving — nobody calling this sandbox saw the bad deploy. Want to go further back? Pick a revision and serve it.

Bring the container you already have

Push the image you build today. It runs the way it runs on your machine — same entrypoint, same environment, same working directory.

Grows with the traffic

One request or ten thousand. You set a ceiling so a busy night is a busy night rather than a surprise, and the rest is handled.

Credentials that stay yours

Point at a secret by name and it is fetched when the container starts, by the container, every time. Rotate it once and every deploy picks it up.

Run it on Sandbox.

Pick one we already run, or point us at yours. Every plan comes with credit to spend, and you only spend it while people are playing.

Request an inviteSee pricing