Skip to main content

Platform architecture

Constellation OS is a control plane for mixed-vendor constellations: one telemetry schema, one fleet graph, one prediction layer, and one operator console.

System diagram

Gateways / fleet agent


Constellation HTTP API ──► Telemetry store
│ │
├── Prediction service │
│ │
▼ ▼
Web console ◄──── Operators / automation (IDE, CI)
(globe · timeline · assistant)

Components

ComponentRole
ConsoleGlobe, timeline, assistant, settings
HTTP APITopology, telemetry ingest, predictions, federation
Fleet agentEdge CLI for topology pull and telemetry push
Telemetry storeTime series keyed to node_id and link identifiers
Prediction serviceTiered ML models (bronze → custom)
IdentityCognito SSO; API tokens with server validation
Knowledge BaseAuthenticated documentation (this site)

Data flow

  1. Topology defines nodes and links—the fleet graph.
  2. Telemetry ingest writes metrics aligned to that graph.
  3. Console reads topology + telemetry for live view and replay.
  4. Predictions consume context (node, link, time) and return forecasts.
  5. Assistant orchestrates queries, charts, and model calls over the same context.

Deployment topology

SurfaceHosting
MarketingStatic export
Console SPAS3 + CloudFront at /app/
Knowledge BaseS3 + CloudFront at docs.*
API & modelsRegional services per program (cloud or customer VPC)

Enterprise programs run dedicated regions on AWS, Azure, GCP, GovCloud, or air-gapped infrastructure.

Repository layout (engineering)

PathRole
apps/console-appConsole SPA
apps/docsKnowledge Base
packages/fleet-agentEdge agent
infra/AWS CDK, SSM, deploy IAM