Skip to main content
Brezel is an open-source, self-hosted service (infercrane/brezel) that runs stateful Firecracker microVM sandboxes for agents on a host the customer operates. The following table shows what CostGraph runs on this provider. CI runners: no. AutoPilot compares runners by price, and this provider publishes no sandbox price.

​
Connect

Run the dispatcher with provider set to brezel and these variables:
  • BREZEL_API_KEY
  • BREZEL_API_URL
  • BREZEL_PROJECT_ID

​
Key and permissions

BREZEL_API_KEY is the opaque service token issued by the customer’s own Brezel deployment (the installer writes it to .brezel/secrets/service.token; sent as a Bearer token). BREZEL_API_URL is the public HTTPS endpoint of that deployment. BREZEL_PROJECT_ID is the project boundary sent as X-Project-ID (default project brezel-default). No roles or scopes beyond the project: “the credential must already be bound to” the X-Project-ID project, and a token bound to it can create, inspect, list, pause, resume and delete that project’s sandboxes. No finer permissions are documented. Sources: github.com: brezel, github.com: API, github.com: STATUS, github.com: GO LIVE, pypi.org: brezel sdk.

​
Limits

  • Status: ‘Self-hosted private-tenant developer preview’, one organization on one dedicated Ubuntu 24.04 x86-64 host with KVM; not a cluster, HA or public-production system. (source)
  • Lifetime is a per-sandbox TTL plus automatic standby; guest activity can postpone standby but cannot extend absolute expiration. Network egress is denied unless allow_internet is set. (source)
  • Capacity (vCPU/RAM/concurrency) is whatever the operator’s host provides; no hosted limits exist. Host requirements: Ubuntu 24.04 x86-64, KVM, /dev/net/tun, cgroup v2. (source)