Self-hosting

Cbox ID is source-available (Elastic License 2.0): you can run the same app that serves cboxid.com on your own infrastructure. Everything else in these docs applies unchanged; where a page writes cboxid.com or <environment>.cboxid.com, substitute your own hosts.

Get it running

1. Requirements — exactly what the app needs to run, as composer.json enforces it.
2. Self-hosting quickstart — from a checkout to a signed-in platform console in a few commands, or by claiming an empty deployment from the browser.
3. Installation & first run — the same, step by step: the first operator, the deployment shape, the first environment and organization.

Run it in production

• Deployment — a fresh server to a hardened instance: the workers, the reverse proxy, security headers, the health probe, and the IdP-surface gate that keeps the root host from acting as an identity provider.
• Configuration — every environment variable that matters, and the secure defaults.
• Day-2 operations — backing up the crypto key, key rotation, upgrades and break-glass.
• Queue workers — what runs in the background and how to size it.
• Security — the operator-facing security surfaces and the compliance view.

Then

Create an environment, then follow a quickstart to sign in to your first app against it. Planes and hosts explains which of your hosts serves what.