What it does
Constellation Space is building an operations layer for large satellite networks. Its ConstellationOS product connects telemetry through one schema, predicts signal, traffic, weather, jamming and conjunction problems, and can route data or hand off under operator policy. The YC profile describes autonomous network handoffs, thermal load balancing and sub-second optical routing; the current homepage presents a 30-day shadow-pilot path.
The fit is a satellite operator or mission-operations team whose network has outgrown reactive monitoring and middleware. The product is not a dashboard refresh. Its value is in correctly predicting and acting on fleet-level failures while leaving an auditable operator policy and safe fallback.
Why I’d look closer
Constellation’s public workflow is concrete: connect ground telemetry, predict network and environmental conditions, then route data or isolate failing streams. The company launch reports more than 100,000 telemetry messages per second, failure prediction at 90%+ accuracy and autonomous rerouting in under two seconds. Those are company-reported operating claims, not independently validated performance.
The homepage points evaluators to a 30-day shadow pilot and the docs expose a quickstart, live topology, telemetry replay, forecasting, HTTP API and deployment guides. That makes the first conversation practical: compare its predictions and recommended actions against an existing mission-ops baseline before granting authority to route traffic.
The founder context is directly relevant. The YC biographies describe Kamran Majid with SpaceX and NASA experience, Laith Altarabishi with satellite-mission-assurance work, Raaid Kabir with Blue Origin, and a COO with space-systems context.
What I’d ask
Which telemetry protocols, constellations and ground architectures are supported? What is shadow-only versus autonomous, how are model errors surfaced, and how are operator policies tested? I’d ask for replayable outage scenarios, the audit trail, latency under load and the exact handoff from prediction to action.
My editorial take
Constellation Space is one of the better hard-infrastructure fits in this batch because the product has a clear shadow-pilot route and public docs. The right purchase test is not the 90% headline; it is whether the system makes fewer dangerous surprises visible without creating an opaque new control plane.
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer fit | Satellite operators and mission-operations teams |
| Workflow | Telemetry connect → failure prediction → policy-controlled action |
| Pilot path | Homepage advertises a 30-day shadow pilot |
| Public pricing | Not exposed in the sources checked |
Sources checked
Checked 2026-09-19.
| Source | Used for |
|---|---|
| YC company profile | Product, founders and company-reported operating claims |
| Constellation homepage | Current product surface and shadow-pilot offer |
| Constellation docs | Console, telemetry, API and deployment surface |
Cohort context
Constellation Space is listed in Winter 2026. In our 2026-09-18 directory snapshot, 126 of 199 listed companies in that cohort have YC’s primary industry label B2B (63.3%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19 16:20 UTC in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Observed |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
