Which deployment model should I pick first?

In the managed model we operate the runtime — Postgres, Redis, ClickHouse, the monolith, and the customer-facing apps — under your branding. You manage the business, the catalog, the pricing, and the operations. Most rollouts go live in weeks rather than months.

Picked by operators who want to launch fast, validate the market, and put engineering effort into product differentiation rather than infrastructure.

Self-hosted deployments give your team root access to the runtime. You run the containers, hold the database, and operate the observability stack. We provide the same builds we run in production, the migration tooling, and direct engineering support for the rollout.

Picked by operators in regulated industries, those with strict data residency requirements, or teams that prefer to operate every part of the stack themselves.

Ask three questions before committing to a model:

1. 1How quickly do we need to be in production with real users?
2. 2Are there compliance or data residency rules that constrain where the data can live?
3. 3Will our team be measured on platform uptime, or on commercial performance?