Platform and availability
Current compute, runtime, and access information. For dated component observations and incidents, see service status.
Last reviewed:
Compute placement and regions
Containers run on Cloudflare infrastructure. Mainbrella does not offer a customer-selected compute region or guaranteed data residency. The API does not publish the region of an individual container; Cloudflare’s network footprint is not a list of guaranteed Mainbrella regions.
Machines and runtimes
| Capability | Current availability |
|---|---|
| Machine size | All plans: five sizes, from Lite (1/16 vCPU, 256 MiB RAM, 2 GB disk) to XL (4 vCPU, 12 GiB RAM, 20 GB disk). |
| Default runtime | Node 24 image with shell access. |
| Other runtime images | Catalog IDs may include Python, Rust, Go, and DevOps. Availability depends on the deployed catalog returned by GET /containers. |
| Custom images | Account-owned images can be launched when ready. Building depends on buildsEnabled from GET /images. |
| Access | HTTP execution and files, SSH through cloudflared, and a browser terminal. |
| Network and storage | Outbound internet is enabled by default. Snapshot stop/resume, filesystem forks, destination rules, and secret injection require their corresponding flags from GET /capabilities. Saved workspaces can be restored into fresh containers. No memory/process resume or persistent volumes. |
See Images for environment selection and Limits for command, file, connection, and build bounds.
Developer capabilities
Source implementation and deployed availability are separate. Check live capabilities before use. The following additions need matching API/runtime support and an SDK release.
| Feature | Status and limits |
|---|---|
| Stateful Python | Source implementation. Generation-scoped contexts; requires Python in the image. Contexts end on timeout, runtime restart or stop. |
| Streaming transfers | Source implementation. Atomic file uploads and streamed downloads up to 64 MiB; separate from the basic file API. |
| Prewarming | Source server-managed pools with automatic replenishment, expiry and retry-safe acquisition; gated by pools.managed. SDK-local pools also remain available. Waiting inventory consumes normal start and compute budgets. |
| Image versions and tags | Immutable image IDs/digests with owner-scoped movable tags. Customer builds still require deployment configuration and qualification. |
| Image reuse | Source owner-scoped build cache and digest-pinned private base imports. Requires a private build repository, migration, configuration and live qualification. |
| Desktop automation | Source SDK helpers for Linux mouse/keyboard control, application launch and screenshots on compatible images. Uses bounded interpreter sessions. No VNC viewer, recording or Windows support. |
| Agent integrations | Source stdio MCP server plus published HTTP/SDK and skill integrations. No managed language server. |
| Telemetry | Source OTLP JSON pull export for lifecycle logs and enabled workload metrics. Metrics and webhook release gates still apply. |
| Memory-preserving pause | Unavailable. Filesystem snapshots do not preserve RAM or running processes. |
| Managed persistent volumes | Unavailable. External object-storage mounts require a compatible image, bucket credentials and runtime qualification; they do not provide local-disk semantics. |
See the generated API and SDK references for usage and limits.
Internal networking
Private Services is a local HTTP prototype for connecting independently managed machines through named .internal endpoints. Explicit network membership and exact-generation checks govern access; a backend needs no public preview. Production support has not been qualified. Require networking.privateServices: true from GET /capabilities. Only bounded plain HTTP is supported, with no arbitrary TCP, HTTPS, WebSockets, private IPs or direct database protocols.
Plan capacity
| Plan | Billing | Unit-hours/month | Concurrent units / containers | Starts/UTC month | Session / idle |
|---|---|---|---|---|---|
| Prepaid | $5 minimum top-up | $0.02/unit-hour | 128 / 100 | 10,000 | 24 hours / 30 minutes |
| Builder (legacy) | $5 | 250 | 28 / 5 | 1,000 | 1 hour / 10 minutes |
| Pro (legacy) | $180 | 9,000 | 128 / 100 | 10,000 | 24 hours / 30 minutes |
| Scale (legacy) | $999 | 50,000 | 640 / 500 | 100,000 | 72 hours / 60 minutes |
Failed starts count toward the monthly start limit. Prepaid accounts consume purchased credit for elapsed compute, including startup and idle time, within their monthly spending cap; existing legacy plans retain fixed compute allowances. Concurrency and session limits also apply. Every size is available on every plan. Returned account limits govern access; check them before launching parallel work.
Service access and commitments
Sign in and add prepaid compute credit. Use the dashboard for interactive containers or the Quickstart for API access. Self-service accounts have no uptime SLA or guaranteed support response time.