Skip to main content

Enterprise

Enterprise on Constellation OS is not a longer feature checklist; it is a different deployment model. Where standard tenants share an environment's API deployment (each already with a physically dedicated data plane), enterprise tenants run dedicated stacks: their own AWS account, their own API deployment, their own domain.

Dedicated tenant stacks​

A dedicated stack gives a program:

  • Its own AWS account. The full stack (API, data plane, secrets, keys) lives in an account vended for that tenant, giving an account-level blast-radius and audit boundary.
  • Its own API domain, on the codename.api.constellation.space pattern. This is shipped precedent, not a diagram: the whitney tenant runs at warpware.api.constellation.space in its own account today.
  • A registry of one. The stack's tenant registry contains only that tenant; there is no co-resident data plane to be misrouted to.
  • The same API contract. A dedicated stack serves exactly the surface documented in the API reference, so integrations built against a shared environment carry over unchanged.

How a stack is provisioned​

Tenant spin-up follows a nine-phase runbook, summarized:

  1. Vend the tenant's AWS account.
  2. Scaffold the infrastructure stack for the tenant.
  3. Bootstrap the account for deployments.
  4. Provision the tenant's API key secrets.
  5. Promote the current platform release image into the account.
  6. Apply the stack and mint the data-plane tokens.
  7. Tighten cross-account trust to the minimum.
  8. Optionally enable weather ingest into the tenant's data plane.
  9. Register the stack as a release target, so it receives future platform releases through the same promotion pipeline as the shared environments.

The last phase matters most operationally: dedicated stacks are not forks. They stay on the release train.

GovCloud and sovereign readiness​

Constellation OS maintains a parallel GovCloud deployment family, with the development environment live at api.dev.gov.constellation.space and gov staging and production accounts established. The same stack pattern that vends a commercial dedicated account applies on the government side, which is the foundation of the sovereign posture: tenant-scoped keys, per-tenant encryption, account-level boundaries, and auditable release promotion, on infrastructure matched to the program's jurisdiction.

What enterprise plans add in the console​

On the console side, the Enterprise plan includes every prediction fidelity tier plus custom-trained models, SSO, and dedicated support; see Plans and billing for the plan table.

Engaging​

There is no self-serve path to a dedicated stack, and pricing is per engagement. Start a conversation at contact@constellation.space with a sketch of your program: asset count, telemetry volume, jurisdiction requirements, and whether you need commercial, GovCloud, or both.