SpecBridge Two ways to run SpecBridge
SpecBridge ships as either a multi-organization SaaS (Cloud) or a single-tenant, self-hosted deployment (Enterprise). Both run the exact same product — specs, spaces, projects, the AI assistant, Git integrations, notifications — the difference is entirely about who owns the infrastructure and how many organizations share it.
(orgs, plans, billing, platform audit log)"] ORG1["Organization A
own database"] ORG2["Organization B
own database"] ORG3["Organization C
own database"] REG -.provisions.-> ORG1 REG -.provisions.-> ORG2 REG -.provisions.-> ORG3 end subgraph Enterprise["Self-hosted Enterprise"] SINGLE["Your organization
one database"] end
Cloud
Sign up, create an organization, and start working — SpecBridge Cloud provisions an isolated database for your organization automatically the moment you create it. A separate Registry service is the source of truth for everything that spans organizations: who exists, what plan they're on, billing, and a platform-wide audit trail. Nothing about your organization's specs, projects, or members is ever visible to another organization.
Cloud-only capabilities: self-service organization creation, plans and billing, and the Super Admin platform for the small number of people who operate SpecBridge Cloud itself. See the Cloud documentation section for detail.
Enterprise
A single-tenant deployment you run yourself, against one database, with no external Registry service and no billing — there's exactly one organization (yours), so there's nothing cross-organization to manage. This is the simpler deployment to stand up: fewer moving parts, no gRPC/internal-API-key setup, no Stripe. See the Enterprise documentation section for the self-hosted setup guide.
What never changes
Regardless of mode: the tenant/space/project/spec hierarchy, the capability-based permission system, the AI assistant, Git provider integrations, the spec version-control model, and notifications all work identically. If you're a day-to-day user of SpecBridge — writing specs, managing a board, reviewing pull requests — you won't notice which mode your organization runs on.