Skip to main content

Export control and deployment options

Constellation runs two ways: as the shared hosted service, or as a dedicated Enterprise deployment for one organization. If your program is export-controlled, agree the deployment and how your data is handled with Constellation before any controlled data reaches it. Until then, evaluate on the demo fleet and public data.

Deployment options​

Shared serviceEnterprise deployment
Platformhttps://platform.constellation.spacehttps://platform.<your-company>.constellation.space
APIhttps://api.constellation.spacehttps://<your-company>.api.constellation.space
Sign-inGoogle or email; each person has an accountCode name, then your company's sign-in or the team password; one shared account
DataShared storage, kept apart by accountA deployment of its own. See Tenant isolation.
FeaturesSet by planEnabled for your deployment by Constellation
KeysWork only on the shared serviceWork only on the deployment that issued them

Your Constellation contact confirms an Enterprise deployment's addresses during onboarding. See Constellation for Enterprise and Environments.

Releases reach Constellation's own dev and stage environments first. A release that passes stage then goes to the shared service and to each Enterprise site separately. An Enterprise site changes only after its own release is approved, so a change to the shared service never reaches it on its own.

What leaves your network​

WhatHow it travels
Telemetry, pass logs and raw filesYou send them: POST /telemetry, the fleet agent, or file uploads over HTTPS or SFTP
Your network configGround station positions, antennas, satellites and their radios, including RF values such as EIRP, G/T, carrier frequency and MODCOD. See Topology config.

Nothing connects into your network. Your mission control system (MCS) pulls results through a connector inside it, outbound over HTTPS; see Connectors. Destinations you connect, such as Amazon S3, Grafana Cloud or a webhook, receive results pushed from Constellation.

Picks from the public asset catalog and the orbit catalog are public data. The catalog never fills an RF value for you.

What to agree before controlled data goes in​

Write to your Constellation contact, or contact@constellation.space, and settle each of these in writing:

  • What is controlled. Which of your data counts as controlled technical data: often the network config's RF values, telemetry and pass logs.
  • Where it runs. An Enterprise deployment, its hosting and region. The Enterprise price card names GovCloud and air-gapped hosting; confirm what is available for your program before you plan on either.
  • Who can reach it. Your identity provider for sign-in, and which Constellation staff may access the deployment for support.
  • How long it is kept. Retention, backups and the long-term archive, and how deletion works. See Data handling.
  • What connects where. API hosts, ingest endpoints and the connectors that pull results.
  • How releases arrive. Who approves each release to your site.

These docs make no claim of export-control compliance or certification. What applies to your program is what you agree with Constellation.