Security
How spec0 protects your specs.
spec0 holds your internal API specs and serves them to your agents. This page is for the security teams who need to sign off — how we keep your specs isolated, encrypted, and yours.
Data residency
Hosted and processed in the EU
Your specs, metadata, and the registry run in the European Union. Data isn't moved or processed outside the region as part of normal operation.
Tenant isolation
Org isolation enforced at the database
Every query against a multi-tenant table carries a server-enforced org filter, so one organisation can never read another's data — even a bug in application code can't return it. Resource-level access then runs through attribute-based access control (ABAC) on top.
Authentication
Managed identity, OAuth-protected MCP
The dashboard authenticates through a managed identity provider (Clerk). The MCP endpoint your agents hit is OAuth-protected. CLI, CI, and agents use org-scoped, revocable access tokens with explicit scopes — never a shared password.
Authorization
Least-privilege, role- and scope-based
Access is governed by per-organisation roles (RBAC) and per-resource ABAC. Tokens carry only the scopes they need (read specs, write specs, manage mocks…), and can be disabled the moment they're no longer needed.
Encryption
Encrypted in transit and at rest
All traffic is served over TLS. Specs are encrypted at rest. If you bring your own LLM provider key for the optional AI features, it's envelope-encrypted with a per-org key and never written to logs.
Your data & LLMs
We hold specs — not your prompts
Spec0 stores your OpenAPI specs and their metadata, and serves slices of them to your agents over MCP. We never see your agent's prompts, its responses, or your end-users' data — your agent talks to its model directly. Hosted-AI features are opt-in and use your own provider key.
Auditability
Every query and change is logged
MCP queries and privileged changes are recorded with the actor, organisation, and timestamp — so you can answer 'who accessed what, and when' for your own org.
Open source
Auditable by design
The mock server (MIT) and the CLI (Apache-2.0) are open source — your team can read exactly what they do before running them in your environment.
Sub-processors
The third parties involved in running the service.
Compliance & questions
We're pre-GA and onboarding design partners. We're glad to walk your security team through the architecture in depth, sign a DPA, and work through your security questionnaire. Formal certifications are part of our path to GA — happy to share where we are.
Building something specific into your review? Reach out — we'd rather answer the real question than point you at a PDF.