← Blog2026-11-22

E2B-compatible sandboxes, in Singapore

LumiCloud runs sandboxes for AI agents in Singapore and serves the E2B API. Code written for E2B moves over by changing two environment variables.

LumiCloud is a sandbox service for AI agents. Each sandbox is a small Linux virtual machine that an agent can run code in, install packages in, serve a port from, pause and resume. It serves the same API as E2B, so E2B's own SDKs talk to it unchanged.

Two environment variables

shexport E2B_DOMAIN=lumicloud.dev
export E2B_API_KEY=<your LumiCloud key>
pythonfrom e2b import Sandbox

with Sandbox.create("base") as sandbox:
    print(sandbox.commands.run("uname -a").stdout)

Nothing else changes: the SDK reads the domain and the key from the environment. Code that passes them in code takes domain= and api_key= instead.

What works

  • E2B's SDKs for Python and JavaScript: e2b, e2b-code-interpreter, and the desktop SDK e2b-desktop.
  • Commands with streamed output, files, every port of a sandbox over HTTPS.
  • Pause and resume, with memory and running processes kept.
  • Public templates: base, code-interpreter-v1, a headless browser with its DevTools open on port 9222, and a desktop for computer-use agents.
  • Templates of your own, built with the SDK's template builder, on Pro.
  • Webhooks with E2B's event payloads, and egress rules that limit where a sandbox may connect.

How we keep it compatible

Compatibility is a claim that rots unless something checks it. lumibox-examples is a public repository of examples, in Python and JavaScript: Claude and OpenAI tool calling with a code interpreter, Claude Code in a sandbox, a browser driven with Playwright, a desktop, a parallel evaluation, npm and pip installs. A job runs all of them against production every day with pinned SDK versions (e2b 2.64.0, e2b-code-interpreter 2.11.10, e2b-desktop 2.7.2, and the JavaScript ones), and a failure pages us. When a new SDK version comes out, it goes into that repository first.

What is different

  • One region, Singapore. A sandbox is created in a median 0.18 s and resumed in 0.32 s, measured from a client in Singapore.
  • A prepaid balance in US dollars. Running sandboxes are charged by vCPU and memory for their running time; paused ones only for the storage of their snapshot.
  • Two plans. Base: no monthly fee, 10 sandboxes at once, up to 4 vCPU and 8 GiB each, runs of up to 1 hour. Pro: $29 a month including $29 of usage, 50 at once, up to 8 vCPU and 16 GiB, 24 hours, templates of your own.
  • Outbound mail ports and UDP other than DNS are blocked.

Prices

$0.035 per vCPU-hour and $0.012 per GiB-hour, the same on both plans. A 2 vCPU, 1 GiB sandbox (the default templates' size) costs $0.082 for an hour of running. New accounts get $20 of credit after verifying a card, to use within 30 days.

Start

Sign up, verify a card in the console, create an API key, and follow the quick start. Questions go to our Telegram group t.me/LumiCloudAI, in English or Chinese.

LumiCloud is not affiliated with E2B. E2B is a trademark of its owner; we use the name to say which SDK our service works with.