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 E2B 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 E2B 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 E2B. Set SUPERSERVE_API_KEY in your environment and CI secrets.
2

Map the API

Most calls keep their names. The main changes: every sandbox needs a name, timeouts are in seconds, and a timeout pauses the sandbox instead of killing it.
To rebuild an E2B template, see Create a template.
3

Update your code

Change the import, add a name, and convert timeouts to seconds.
4

Move existing sandboxes with the migration script

The script copies /home/user from each E2B sandbox into a new Superserve sandbox. It does not change or delete your E2B sandboxes; it removes only the temporary archive. If a copy fails, the script deletes the new Superserve sandbox. Run it with both E2B_API_KEY and SUPERSERVE_API_KEY set.
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 only. Running processes and memory do not move. Start your services again in the new sandbox, then take a Superserve snapshot to keep that state.
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 E2B

After the cutover, remove the e2b package and delete E2B_API_KEY from your environment and CI secrets.

Known differences