Skip to main content
Superserve runs cloud coding agents, long-running agents, CI workers, background jobs, evals, and RL environments in isolated VMs. If you run these on Daytona today, most code moves call by call.

How Superserve compares

Ready to switch

Pick how you want to migrate. Do it yourself step by step, or give the prompt to a coding agent and let it change your code.
Before you start
  • Get a Superserve API key. Sign in to the console, or sign up for free (no card required). Open API Keys and click Create Key. See Get an API key.
  • Keep Daytona installed. You remove it only after the cutover, in step 6.
1

Install the SDK and set your API key

Install the Superserve SDK next to Daytona. Set SUPERSERVE_API_KEY in your environment and CI secrets.
2

Map the API

The main changes: a Daytona snapshot becomes a Superserve template, every sandbox needs a name, commands move from process to commands, and an idle sandbox pauses instead of stopping.
To turn a Daytona snapshot or image into a template, see Create a template.
3

Update your code

Build the template once. Then replace the Daytona client with Sandbox, add a name, and convert intervals from minutes to seconds.
4

Move existing sandboxes with the migration script

The script copies a directory from each started Daytona sandbox into a new Superserve sandbox. It does not change or delete your Daytona sandboxes; it removes only the temporary archive. If a copy fails, the script deletes the new Superserve sandbox. Run it with both DAYTONA_API_KEY and SUPERSERVE_API_KEY set. Start a stopped Daytona sandbox first to include it.
Each archive, upload and extract can take up to 10 minutes. For large directories or slow connections, raise TIMEOUT_MS / TIMEOUT_SECONDS.The script copies files. Start your services in the new sandbox, then take a Superserve snapshot to save memory, processes and disk together.
5

Verify and cut over

Run your test suite against Superserve. Check the sandbox list in the console. When the results match, send production traffic to Superserve.
6

Uninstall Daytona

After the cutover, remove the Daytona package and delete DAYTONA_API_KEY from your environment and CI secrets. Older projects use the @daytonaio/sdk (npm) or daytona-sdk (pip) package name.

Known differences