Dedicated Deployments#
Co-Vibe runs as a hosted service, and teams that need stronger isolation can get a dedicated deployment: a private instance of the Co-Vibe control plane operated for a single organization, with its own database, domain, and sign-in. The product is identical — only the isolation boundary changes.
What does the standard hosted service look like?#
On the standard service at co-vibe.dev, every workspace shares one control plane. Tenant data is isolated with PostgreSQL row-level security: every query runs inside the requesting tenant's scope, and cross-tenant reads are rejected at the database layer, not just in application code. The local companion CLI is the only component on developer machines — repo snapshots, agent configuration, and usage-counter reads happen locally and sync out through authenticated MCP calls.
What changes with a dedicated deployment?#
A dedicated deployment moves the entire control plane — web console, MCP API, and PostgreSQL storage — onto infrastructure that serves only your organization:
| Component | Standard hosted | Dedicated |
|---|---|---|
| Control plane | Shared, multi-tenant | Private instance |
| Database | Shared cluster, RLS-scoped | Own database |
| Domain and sign-in | co-vibe.dev | Your domain, your SSO |
| Local companion | Developer machines | Developer machines (same) |
| Operations | Operated by Co-Vibe | Scoped per engagement |
What stays on developer machines either way?#
The local companion owns repo snapshots, per-agent configuration, and local usage-counter reads. The companion never uploads your source code in either model: agents report work items, session activity, and telemetry through MCP tools, and the privacy model is the same as the standard service — see Privacy and telemetry.
How do I arrange one?#
Dedicated deployments are set up per team. Contact hakan@spaceflow.tech with your team size and requirements, and we will scope the deployment together.