Deployment modes
Universal AI Bridge is not positioned as cloud-only. The current managed reference topology keeps the web surface on the apex domain while the bridge and Supabase stay on explicit subdomains, with the same env-driven contract still supporting self-hosted and restricted-network deployments.
Deployment messaging stays aligned with what the repository and external deployment guide already support today.
| Dimension | Managed bridge | Self-hosted | Closed-network |
|---|---|---|---|
| What stays the same | One bridge service, explicit session routing, shared capability contracts, and audit-visible outcomes. | The same bridge contract and runtime model, but with your own infrastructure ownership and rollout timing. | The same connector-neutral execution model while keeping bridge, runtime, and data paths inside controlled networks. |
| Best fit | Teams evaluating the platform quickly and wanting a repeatable managed deployment path. | Teams that need deployment control, custom infrastructure policy, or region-specific operations. | Teams with desktop, regulated, or air-gapped requirements where public SaaS is not a fit. |
| Current maturity | The managed bridge path is documented and externally re-verified through Render plus Supabase-compatible services. | Self-hosted rollout is supported through the same env contract, Docker image, migrations, and bootstrap flow. | Closed-network posture is enabled by the Satellite runtime model, fail-closed allowlists, and no requirement for cloud-only execution. |
This is the current rollout posture reflected in the README and the external deployment guide.
Bridge
The current managed deployment path stays intentionally narrow: one bridge container, one managed Postgres-compatible database, one managed Redis instance, and one explicit bridge host that stays separate from the public web apex domain.
Runtime
After restart, redeploy, or secret rotation, the runtime reconnects explicitly and session health is rechecked before smoke or execution traffic resumes.
Verification
The current deployment story includes /healthz, /readyz, migrations, first workspace bootstrap, and authenticated smoke verification.
Domains
The current managed reference uses Vercel for the primary web domain, Render for a dedicated bridge subdomain, and Supabase for a separate auth and storage subdomain.
Next step
Use the docs when you want the current technical contract, or use the enterprise branch when you want a conversation about deployment fit and rollout posture.