Beam Cloud

license

AGPL-3.0(OSI, copyleft)

source

public

managed-tier

Beam (beam.cloud) fully-managed GPU cloud (proprietary)

core-gated

ungated(the whole AGPL-3.0 stack is in the repo - gateway, scheduler, worker, proto, deploy manifests and even the billing service - with no second license file and no license-key module, and Beam sells concurrency, seats and retention on the hosted cloud)

AGPL-3.0 (OSI copyleft) engine with the managed Beam cloud sold beside it. The 1,281-entry untruncated tree carries one governing LICENSE plus a single vendored one, no enterprise or ee/ directory, and no license-key module; the whole server stack ships - gateway, scheduler, worker, protos, Docker and Kubernetes manifests - and even pkg/gateway/services/compute/billing.go, the metering the hosted product runs on, is inside the AGPL tree. Beam’s pricing tiers concurrency, seats and log retention on the hosted cloud, names no capability the source lacks, and advertises a self-hosted product that "runs entirely in your own environment". That is a separate managed service around a complete open core, which the rubric says does not gate it.

• https://github.com/beam-cloud/beta9 recorded 2026-06-04

  AGPL-3.0 license; open source serverless AI runtime; engine powering managed Beam cloud (beam.cloud)

• https://api.github.com/repos/beam-cloud/beta9/git/trees/main?recursive=1 recorded 2026-08-12

  Full untruncated recursive tree, 1,281 entries. Two license paths: the root LICENSE and one vendored sdk/src/beta9/vendor/pathspec/LICENSE. No ee/, enterprise/, commercial/ or proprietary/ directory. The top level carries the complete server stack - cmd/, pkg/, proto/, deploy/, manifests/, docker/, sdk/ - and the paid-service plumbing is open too: pkg/gateway/services/compute/billing.go is in the AGPL tree.

• https://api.github.com/repos/beam-cloud/beta9 recorded 2026-08-12

  Repo metadata: language Go, license spdx_id AGPL-3.0, 1,741 stars, default branch main.

• https://www.beam.cloud/pricing recorded 2026-08-12

  Three tiers - Developer ($0 + usage), Team ($89/mo + usage), Growth (contact). They differ on concurrency, seats and log retention: 5 vs 50 vs 1,000+ concurrent GPU containers, 1 vs 3 vs unlimited seats, 30-day vs 1-year retention. No feature is named as absent from the open source, and the page states "We also offer a self-hosted product which runs entirely in your own environment, ensuring that no data leaves your VPC."