Orblealpha

Docs

From E2B

To run code written for the E2B SDK on Orble, set these two variables, with a key you make in Settings.

export E2B_DOMAIN=orble.techexport E2B_API_KEY=orble_...
main.py
from e2b import Sandbox

sbx = Sandbox.create()
print(sbx.commands.run("echo hello").stdout)
sbx.kill()
Works
Sandbox.create, connect, list, kill, set_timeout, pause, create_snapshot, fork, commands, PTY, files, watch_dir and get_host, in the Python and JavaScript SDKs, and the code interpreter and desktop SDKs
Templates
base (2 vCPU, 4 GiB), m (4 vCPU, 8 GiB) and l (8 vCPU, 16 GiB), all Debian 13 with Python, Node.js and Docker
Pro
network rules: allow_internet_access, allowOut, denyOut and update_network (Egress rules)
Not yet
Template.build, volumes and secrets

From Daytona

To run code written for the Daytona SDK on Orble, set these two variables, with a key you make in Settings.

export DAYTONA_API_URL=https://api.orble.tech/daytonaexport DAYTONA_API_KEY=orble_...
main.py
from daytona import Daytona

sandbox = Daytona().create()
print(sandbox.process.exec("echo hello").result)
sandbox.delete()
Works
create, get, list, start, stop, delete, labels, auto-stop, auto-delete, preview links, snapshots, fork, process.exec, code_run, sessions, PTY sessions, files, signed file URLs, git, LSP and computer use, in the Python and JavaScript SDKs
Sizes
you get the smallest box with the cpu and memory you ask for: 2 vCPU and 4 GiB, 4 and 8, or 8 and 16, all Debian 13 with Python, Node.js and Docker
Pro
networkBlockAll, networkAllowList, domainAllowList and network settings on a running sandbox (Egress rules)
Not yet
your own images, volumes, secrets, and computer use's recordings and accessibility tree