From branded sandbox to production, in scoped stages
A branded sandbox can be configured quickly using the tenant-configuration approach demonstrated on this site. Production timelines depend on your identity, data, integration, and compliance requirements — this page outlines the stages, not a fixed timeline.
1. Branded preview
We configure a tenant using the same JSON-driven approach shown in the "Upload your logo, set your palette" example on the main page: display name, logo, hero copy, and crisis-line number are set per organization with no forked code. This is the fastest stage and the one shown live in this site's demo links.
2. Identity & access
SAML/OIDC SSO and, where relevant, CAC/PIV smart-card authentication are connected to your identity provider. This is demonstrated as an active connector in the sandbox today; wiring it to your specific IdP is a scoped, typically fast-turnaround step.
3. Data & integrations
This is the stage that varies most by organization. The platform ships with a live REST API and webhook framework — demonstrated in the operations console — that already supports pushing events out and pulling data in. Connecting it to your specific accounting system, CRM, EHR, HR platform, or SIEM is a bespoke integration project scoped to that system's API and your data model. We do not pre-build these connectors speculatively; we scope them once we know which systems you're connecting.
4. Compliance review
BAA terms, data retention, and compliance documentation (including any FedRAMP/FISMA-relevant packaging for federal or defense-adjacent organizations) are handled in a dedicated security and implementation brief rather than on this marketing site. See the security overview for what's demonstrated today.
5. Go-live
Once identity, data flows, and compliance sign-off are in place, the branded environment configured in stage 1 becomes the production environment — there is no separate rebuild step.