Early access: 1 VM per user, auto-paused after 15 min

Cloud sandboxes on Firecracker microVMs

Spin up an isolated Linux VM, run code in it over an API, pause it, and tear it down when you're done.

Real isolation

Every sandbox is a Firecracker microVM with its own kernel, rootfs and network port. Not a container.

Boots in seconds

Create a VM with one API call and run commands in it straight away.

Pause and resume

Pause snapshots memory and disk to storage and frees the host. Resume picks up exactly where it stopped.

Exec and files over HTTP

Run commands, write files and create directories with a simple JSON API and an API key.

Expose ports

Start a server inside the VM and get a public URL for it.

Self-hosted

Raw Firecracker, Linux networking and TypeScript. No orchestration frameworks.

Two calls to a running sandbox

curl -X POST https://firecracker.pavitar.dev/api/firecracker/create \
  -H "Authorization: Bearer $FUSE_API_KEY" \
  -H "Content-Type: application/json" -d '{}'

curl -X POST https://firecracker.pavitar.dev/api/firecracker/exec/run \
  -H "Authorization: Bearer $FUSE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":"<vm id>","projectId":"demo","command":"uname -a"}'

Get your API key from the dashboard after signing in.