Overview
Your own machine, on demand. Forged in seconds, yours for as long as you need, on the cloud you choose.
Your code needs a machine somewhere — to run a branch, run an agent, run a test suite, run a dev session that survives closing your laptop. Each option forces a tradeoff: container sandboxes share a kernel. Microvm sandboxes cap at 8 vCPU and 24-hour sessions. Raw cloud VMs take half an hour of setup. Persistent VPSes leak state and bill you when idle. Workstation environments bundle an IDE you didn't ask for.
Gibil forges a real machine — own kernel, full root, Docker-in-Docker, your repo cloned — in 30–90 seconds. Today's supported providers: Hetzner Cloud (cheap EU/US baseline, ~$0.008/hr at list price) and Vultr (APAC density — Tokyo, Seoul, Singapore, Sydney, Mumbai). Pick a default with gibil init, override per-server with --provider. Set the TTL anywhere from 15m to 30d. When you're done, one command burns it. Nothing left. The CloudProvider interface is built so additional clouds (Fly.io, DO, AWS) plug in without changing the surface.
npm install -g gibil
gibil create --name my-app --repo github.com/you/project --ttl 30m
gibil run my-app "pnpm install && pnpm test"
gibil destroy my-appWhat you get
Every Gibil box is a fresh server with its own kernel, its own IP, full root, SSH, and Docker. Not a container. Not a sandbox. Today's image is Ubuntu Linux, running on Hetzner or Vultr depending on which provider you pick.
| Feature | Gibil | Managed sandbox |
|---|---|---|
| Own kernel (full VM) | Yes | Container (Daytona) or Firecracker microvm (E2B, Sprites) |
| Full root | Yes | Limited (Daytona) or full (E2B) |
| Own public IP | Yes | No |
| Resource ceiling | 48 vCPU / 192 GB | 8 vCPU / 8 GB (E2B) / 16 GB (Sprites) / 16 GB (Anthropic) |
| Lifetime | 15m–30d, extendable | 1h–24h cap (E2B) or quota-bound (Anthropic) |
| BYOC | Yes — your account (Hetzner + Vultr today, more clouds on the roadmap) | No — vendor cloud only |
--json for agents | Every command | Rarely |
How you reach it
Gibil is the box. How you drive it is up to you.
From the CLI
gibil create, gibil ssh, gibil run, gibil destroy. Five minutes from install to a working box.
Through an integration
MCP server for any agent, the agent skill (40+ agents), the VS Code extension, the Sandcastle provider. Gibil is the substrate they plug into.
How it works
FORGE USE BURN
───── ─── ────
gibil create gibil run / gibil ssh gibil destroy
Fresh box in ~30s Full root access Server deleted
Repo cloned Docker ready Keys cleaned up
Deps installed Own IP address No trace leftThe box auto-destroys after the TTL you set. Need it longer? gibil extend. Need it gone now? gibil destroy. The TTL is your lever.
Next steps
- Quick Start — forge your first box in 5 minutes
- How It Works — understand the lifecycle
- CLI Reference — full command documentation