Blaxel

license

MIT(OSI)

source

public(sandbox API, self-hostable via Docker Compose)

managed-tier

Blaxel proprietary perpetual-standby platform

core features withheld

yes — the control plane that creates, suspends and resumes sandboxes - the perpetual-standby platform Blaxel sells - exists in no public repo

Blaxel's MIT-licensed repository publishes only the in-sandbox HTTP API and about thirty Dockerfile image templates. The scheduler that creates, suspends and resumes sandboxes, the perpetual-standby control plane the product is sold on, is absent from every public repository in the org, which keeps Blaxel at open core rather than open source.

• https://api.github.com/orgs/blaxel-ai/repos?per_page=100 recorded 2026-08-12

  All 29 public repos in the org. They are SDKs and clients (sdk-python, sdk-typescript, sdk-go, toolkit, blaxel-mcp-server), integration plugins, image bases and forks of third-party infrastructure (virtual-kubelet, fluent-bit, kubernetes-event-exporter). No repo implements the sandbox control plane the SDKs call; bl-controller is a Kubernetes controller for legacy Beamlit resources.

• https://api.github.com/repos/blaxel-ai/sandbox recorded 2026-08-12

  Repo metadata: language Go, license spdx_id MIT, 26 stars, default branch main.

• https://api.github.com/repos/blaxel-ai/sandbox/git/trees/main?recursive=1 recorded 2026-08-12

  Full untruncated recursive tree, 419 entries, one MIT LICENSE. The entire tree is sandbox-api/ (the HTTP API that runs inside a sandbox: filesystem, process, network), hub/ (about thirty Dockerfile templates - base-image, py-app, ts-app, chromium, jupyter, claude-code), docker/, e2e/ and a docker-compose.yaml for building and testing those images. There is no scheduler, allocator, control plane or standby/resume implementation anywhere in it.

• https://blaxel.ai/pricing recorded 2026-09-29

  The Blaxel pricing page says even the self-hosted option depends on the vendor control plane, quoting "Deploy bare metal servers in your own VPC, and privately connect them to Blaxel control plane for the sandbox runtime".

• https://blaxel.ai/sandbox recorded 2026-09-29

  The Blaxel sandbox product page scopes its open-source claim to the API alone under the heading "Open-source core", saying "sandbox API is fully open-source."

• https://github.com/blaxel-ai/sandbox recorded 2026-07-09

  MIT license; sandbox API self-hostable via Docker Compose (port 8080)

• https://raw.githubusercontent.com/blaxel-ai/sandbox/main/LICENSE recorded 2026-09-29

  The blaxel-ai/sandbox repository LICENSE file on main is the MIT license, opening "MIT License" and "Copyright (c) 2025 Beamlit, Inc." with the standard grant "Permission is hereby granted, free of charge, to any person obtaining a copy".

• https://raw.githubusercontent.com/blaxel-ai/sandbox/main/README.md recorded 2026-09-29

  The blaxel-ai/sandbox README scopes the repo to image templates plus the in-sandbox API, describing it as "a collection of development environment templates" whose base image is "Accessible via port 8080 (sandbox-api)" and whose other templates add only their own app ports, and it sends sandbox lifecycle to the hosted service: "You can find sample on how to create/retrieve/remove a Sandbox at this url: https://docs.blaxel.ai/Sandboxes/Overview"; searched the body for scheduler, control plane, standby, resume and self-host: none.

Blaxel publishes no customer, request or sandbox-count figure, so GitHub stars on its one declared repository are the only adoption signal available. That repository is still new, and a star is not a use, so the resulting reading says more about age than about real-world adoption.

• https://api.github.com/repos/blaxel-ai/sandbox recorded 2026-08-13

  Repository metadata - stargazers_count 27 and forks_count 13 for blaxel-ai/sandbox, language Go, license spdx_id MIT, public and not archived

• https://blaxel.ai/sandbox recorded 2026-08-13

  No usage, customer or request figure is published anywhere on the product page; it sells on 25ms resumes, perpetual standby and auto-suspend after 15s of inactivity

Blaxel's microVMs resume from standby in about 25 milliseconds with full filesystem and memory state intact, and the platform adds auto-suspend, batch jobs and self-hosted or VPC deployment options. What keeps it a step below the category's proven microVM platforms is scale: its request-volume claims come from the vendor and are not independently verified.

• https://blaxel.ai/pricing recorded 2026-09-29

  The Blaxel pricing page describes a self-hosted option, quoting "Deploy bare metal servers in your own VPC, and privately connect them to Blaxel control plane for the sandbox runtime"; it shows no repository license.

• https://blaxel.ai/sandbox recorded 2026-09-29

  The Blaxel sandbox product page says the runtime is built on microVMs, quoting "Every sandbox runs in its own microVM with no shared kernel." and "Resume from standby in 25 milliseconds with full memory state restored, at any time." and "connect under one second"; it lists batch jobs, volumes and static IPs, and its Open-source core block says "sandbox API is fully open-source." without naming a license or the control plane.

• https://docs.blaxel.ai/Sandboxes/Overview recorded 2026-09-29

  The Blaxel sandboxes docs page describes standby, quoting "Blaxel automatically creates a snapshot of the entire state" and "standby mode within approximately 15 seconds", and its description says "sub-25ms cold starts, file system, processes, and an MCP server for agents".

• https://www.computesdk.com/benchmarks/sandboxes/ recorded 2026-08-13

  ComputeSDK TTI leaderboard, independent, 100 iterations per run, last run 7 August 2026, 24 providers on 4 vCPU / 16GB in Northern Virginia. Blaxel records 0.51s median, 0.60s P95, 0.61s P99, 100% success, composite 94.5, ranking 9th of 24 by composite score.