Environments
Constellation OS runs three hosted console environments and four platform API environments, plus GovCloud and dedicated-tenant hosts. Use the pair that matches your program; API keys are environment-scoped and never work across environments.
Consoles
| Environment | URL | Purpose |
|---|---|---|
| Production | console.constellation.space/app/ | Operator console for production tenants |
| Development | dev-console.constellation.space/app/ | Latest merged features; wired to the sandbox platform API |
| Staging | staging-docs.constellation-io.com/app/ | Internal promotion target between dev and production |
The console detects its environment from the hostname; the environment name is shown in Settings, API along with the API endpoints that environment resolves to.
Platform API
| Environment | Base URL |
|---|---|
| Production | https://api.constellation.space |
| Stage | https://stage.api.constellation.space |
| Development | https://dev.api.constellation.space |
| Sandbox | https://sandbox.api.constellation.space |
| GovCloud development | https://api.dev.gov.constellation.space |
Every environment exposes the same surface: GET /health, GET /topology, POST /telemetry, and GET /predictions. Authentication is the x-api-key header on every request except /health; see API authentication. Dedicated tenants get their own hostname under the <codename>.api.constellation.space pattern, and GovCloud programs run on separate gov hosts; see Enterprise.
What the sandbox is
The sandbox is a seeded evaluation environment: it holds a pre-ingested demo fleet (an hour of OneWeb-style topology and telemetry) that the development console reads in live mode. It is the right target for trying the API before your tenant exists, and for integration tests that must not touch production data. Sandbox data is pinned to a fixed epoch, so time-scoped reads should pass an explicit as_of_utc rather than assuming "now" has fresh samples.
Key prefixes
Credentials generated in the console are prefixed by environment so a leaked key identifies its blast radius at a glance: cos_live_ (production), cos_dev_ (development), cos_sbx_ (sandbox). Note that a key generated in the console browser is not usable against the platform until the platform team provisions it; see Authentication.
Documentation and marketing
| Site | URL |
|---|---|
| Knowledge Base (this site) | docs.constellation.space |
| Marketing | constellation.space |
Choosing an environment
- Evaluating the product: production console as a guest, or the development console against sandbox data.
- Building an integration: sandbox API first, then your tenant's production endpoint with a production key.
- Operating a fleet: production console and production API only.
Full host-by-host tables, including the console's local-development proxy paths, live in URLs and hosts.