OPEN SOURCE & HOSTING
Two ways to run it.
podblocks is the product. Hosting is the service. It is the Red Hat model: the engine is Apache 2.0, and you can run all of it yourself. The hosted tier sells operation, not withheld code.
SELF-HOST VS HOSTED
Same engine. Different operator.
| Self-host (AVON model) | Hosted | |
|---|---|---|
| License | Apache 2.0 | Apache 2.0 engine, operated by BMD |
| Where it runs | Your infrastructure | Managed control plane, your workers |
| Executes your code | Your own worker host | Never. Workers stay customer side |
| Multi-tenant isolation | Single tenant | Postgres row-level security per org |
| Identity & SSO | Optional single user | Email, password, and OIDC with roles |
| Support & SLAs | Community | Operated, with SLAs |
| Telemetry | None | None |
HOSTED LIMITS
What a plan governs.
Hosted plans are shaped by a handful of limits, not a feature paywall. Every plan gets the whole product; plans differ on capacity and retention.
- Pods
- Per-plan cap on stored pod definitions.
- Resident pods
- Per-plan cap on long-lived, continuously reacting pods.
- Workers
- Per-plan cap on connected worker processes.
- Event rate
- Per-org event throughput cap, enforced with backpressure.
- Retention
- How many days of causal posets are kept.
PORTABILITY
Move between them, both directions.
An OSS data directory exports to a tarball and imports into a hosted org, and the reverse works too. You are never locked into the hosted tier, and never locked out of it.