Skip to main content

Sandboxes backed by Brezel

Customers see an InferCrane sandbox: a durable workspace that runs commands safely, sleeps when idle, exposes short-lived previews, and can call an approved InferCrane model endpoint. Brezel is the execution backend, not a customer identity or browser dependency.
This remains a private-tenant CPU preview. Map one InferCrane tenant to one dedicated Brezel project. The current host uses host-local workspace durability; do not promise survival after complete host loss until encrypted backup and restore or replicated storage is implemented and tested.
The browser never receives Brezel tokens, project credentials, engine IDs, node capability tokens, internal addresses, workspace IDs, or provider sandbox IDs. Every operation starts by resolving the customer-facing InferCrane ID and checking its tenant ownership.

Configure the provider

Create immutable Brezel environment and connector revisions first. Then mount a dedicated owner-only service token and configure the stable mappings:
The token file must be a non-empty regular file readable only by its owner. Production origins require HTTPS; loopback HTTP is accepted for local development. None of these values may use a NEXT_PUBLIC_ prefix. For a model-enabled sandbox, Brezel injects only a short-lived connector session:
The client sends the lease to the gateway path for the immutable connector revision selected by InferCrane. The gateway checks the live computer and route policy before adding the real credential outside the guest. Long-lived InferCrane, provider, GitHub, and cloud secrets must never enter guest environment variables, command arguments, files, snapshots, receipts, or logs.

Customer API

Create records InferCrane metadata first, creates a durable Brezel workspace, attaches it at /workspace, then creates the sandbox from an approved environment. Partial failure is compensated and remains visibly failed or cleanup_pending; uncertainty is never rewritten as running.
Commands are bounded tasks, not an interactive PTY. The response stays an incremental NDJSON stream: output chunks are base64-encoded and the terminal exited event carries the exit code. Files are streamed with a 32 MiB limit. Preview leases are re-brokered through an InferCrane-scoped URL; the original provider path never reaches the browser.

Usage and privacy

InferCrane maintains an append-only, idempotent usage ledger for running time, standby time, command duration and exit class, transfer bytes, and preview request counts. The dashboard calls this usage, not an invoice. The ledger never records command text, stdout, stderr, file names or paths, file contents, source code, prompts, model responses, preview URLs, or lease tokens. Brezel Prometheus metrics remain operational metrics and are not the customer billing ledger.

Public edge and operations

Run the included Caddy edge with BREZEL_PUBLIC_HOST=sandbox.infercrane.com. Only ports 80 and 443 are public; restrict SSH to an operator network and never publish lifecycle, node, database, Redis, or metrics ports. Cloud IAM used to administer the host is a separate operational credential and must be rotated without changing the dedicated Brezel service token used by InferCrane. Verify the public https://sandbox.infercrane.com/readyz boundary. Query /v1/capabilities through InferCrane with the dedicated service credential; an unauthenticated request must return 401. Then run the full lifecycle through InferCrane: create, command, file write/read, HTTP preview, pause, resume, persistence check, delete, and cleanup confirmation.

Production qualification

The bounded Scaleway production tuple was qualified on 2026-09-21:
  • Host: one dedicated Ubuntu 24.04 x86-64 KVM node
  • Public edge: https://sandbox.infercrane.com with active DNS and TLS
  • Dedicated project: one tenant-scoped Brezel project
  • Approved environments: immutable, operator-installed environment revisions
  • Model connector: one immutable, policy-scoped connector revision
The production workflow passed creation, streamed commands, file persistence, preview brokering, sanitized receipts, pause/resume, model connector access, usage recording, deletion, and cleanup through InferCrane. The service token remains host-side in an owner-only file and its value is not part of this evidence. See Scaleway Brezel evidence for the exact qualification boundary.

Current boundary

This release does not claim GPU passthrough, interactive PTY/SSH, arbitrary OCI builds, public shared multitenancy, unrestricted internet with controlled egress, or host-loss durability. Direct internet access stays disabled by default. For E2B, Modal, Kubernetes, or another externally owned runtime, use external sandbox access. Those routes bind scoped model access but never mutate the external runtime.