Skip to content
Self-hosted vs the alternatives

Same capabilities.
Your boxes. Your bill.

Every product in the catalogue has a hosted equivalent — and each is excellent at what it does. They are also priced per request, per minute, or per connection; your data lives on their infrastructure. This page is the honest comparison.

Auto-CMS

Deployment

Media

Messaging

Observability

Registry

Storage

Testing

The common thread

Why self-host any of this?

Every comparison on this page rests on the same few decisions. These are the principles the suite was designed around.

Flat-rate cost model

A self-hosted container costs the same whether it processes 100 jobs or 10 million. SaaS and cloud alternatives meter per request, minute, or connection — costs scale linearly with usage.

Your data stays in your VPC

No cross-border data transfer. No vendor data-processing agreements. Compliance, residency, and audit are simpler when data never leaves.

No vendor lock-in

Every service speaks open standards — MQTT 5, OpenAPI, OCI Distribution, Redis protocol, S3 API. Migrating away is a DNS change, not a rewrite.

One contract across your stack

One platform contract. Once your team learns one service, onboarding the next is an afternoon. Compare to mastering AWS IoT and Document Intelligence and MediaConvert separately.

Scale on the boxes you already have

Every service is stateless HTTP plus a worker pool. Helm charts ship with every image. If you have a Kubernetes cluster, you already have the platform.

Extend without asking permission

Need a custom task, a new notification driver, or a bespoke integration? The source is yours to modify. No vendor roadmap. No feature request backlog.

Ready when you are

Own the stack. Own the invoice.

Every service runs in your cluster, reads from your storage, and bills once — not per request.