Private documentation
Password-protected or workspace-restricted published sites.
Enterprise
Fit the deployment to the organisation—not the other way around.
Enterprise is a security, identity, support, and procurement agreement. It starts with requirements, not a checkout button.
Shipped foundation
Controls available before negotiation.
These capabilities exist in the product today. Contract-dependent services and deployment choices are listed separately.
Project roles
Workspace roles with per-project overrides, plus separate review and publish grants.
Audit history
Attributed events for sensitive workspace, identity, integration, and publishing actions.
Git and export
Customer-owned content repositories and complete portable exports.
Scoped tools
Named API tokens, content API, MCP access, and signed outbound webhooks.
Operational visibility
Status, preflight, metrics, queue workers, and documented deployment checks.
By agreement
Identity, contract, deployment, and support.
These items require configuration, operator work, or written terms. They are not automatic checkboxes on a card.
Connect a proved email domain to the organisation’s identity provider. Configuration and compatibility are reviewed first.
Review architecture, data handling, a DPA, the contract, and required evidence together.
Agree retention, residency where supportable, service levels, invoice billing, and operating responsibilities.
Plan assisted migration, workspace size, documentation sites, and allowances around the actual rollout.
Start with requirements