Platform and availability

Current compute, runtime, and access information. For dated component observations and incidents, see service status.

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

CapabilityCurrent availability
Machine sizeAll 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 runtimeNode 24 image with shell access.
Other runtime imagesCatalog IDs may include Python, Rust, Go, and DevOps. Availability depends on the deployed catalog returned by GET /containers.
Custom imagesAccount-owned images can be launched when ready. Building depends on buildsEnabled from GET /images.
AccessHTTP execution and files, SSH through cloudflared, and a browser terminal.
Network and storageOutbound internet enabled. Files are temporary and lost after stop; no snapshots or resume after stop.

See Images for environment selection and Limits for command, file, connection, and build bounds.

Plan capacity

PlanUSD/monthUnit-hours/monthConcurrent units / containersStarts/UTC monthSession / idle
Builder$525028 / 51,0001 hour / 10 minutes
Pro$1809,000128 / 10010,00024 hours / 30 minutes
Scale$99950,000640 / 500100,00072 hours / 60 minutes

Failed starts count toward the monthly allowance. Plans determine monthly compute allowance, concurrency, and session duration. 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 choose a monthly plan or redeem a valid trial code. Use the dashboard for interactive containers or the Quickstart for API access. Self-service plans have no uptime SLA or guaranteed support response time.

Service status · Startup benchmarks · Trust center