Briefing · Investors
A governed command path for AI agents in satellite operations.
Every agent command through deterministic gates and operator approval, signed and replayable.
- What we sell: a governed command path
- Start with one queue, then widen
- Traffic compounds; every decision still needs an owner
- The market, from public counts
- Where we win and lose against classical methods
- One product, one SDK, one safety envelope
- The questions investors ask first
- Roadmap
- Why this founder
- Request an investor briefing
ⓘ
0 of 1,952 commands unsafe in the scored runs of the released code, with an operator that approved everything (the gates held it); an earlier build's two-person defect (1,281 of 2,434 unsafe) was found and fixed.
What we sell: a governed command path.
- What an engagement delivers: the stack running in the operator's own AWS account; integration with their ground segment, command path and flight rules; and ongoing benchmarking and assurance with each release. How we deploy, stage by stage →
- What is being bought: safety and assurance as code across the operations queue: deterministic gates, the two-person rule, deadline-aware uplink and a signed, replayable record of every decision.
- The thesis: Operators already automate. Today the gate, the second approver, the deadline and the audit trail are spread across procedures, console checks and logs. ConstellOps makes them one code path that signs and replays every decision, model- and solver-agnostic.
- Pricing: not published; discussed in a briefing.
Start with one queue, then widen.
- Wedge: the governed path first. The gates are deliberately model-agnostic: they can govern a classical solver's decisions as well as an agent's, so an operator can adopt the governed command path first and add agents workflow by workflow.
- Expansion: five operations queues on the same gates (conjunctions, fleet anomalies, cross-domain incidents, staged rollouts and storm surges), each added one scope at a time, from shadow mode to gated pilot to production.
- Platform: the Agentic Operations Stack, for engineering teams that build their own operations agents on space and other physical systems.
Traffic compounds; every decision still needs an owner.
From public sources only. About 40,000 objects are tracked in orbit, about 11,000 of them active payloads, and about 1,900 more active payloads than a year before. A typical low-orbit satellite gets collision alerts by the hundreds each week, and collision-avoidance events rise every year ([8]). Each of those decisions still needs someone accountable for it, and auditors will ask who approved what, on which inputs, and whether it can be reproduced ([9]). Language models can now triage; what has been missing is the layer between the agent and the uplink.
The market, from public counts.
About 11,000 active payloads are in orbit, about 1,900 more than a year before; each one is screened for conjunctions, raises alarms, takes software updates and is exposed to storms. About 2 alerts per satellite per week need hours of analyst follow-up. Collision avoidance is growing quickly at the largest constellation: SpaceX reported 50,666 manoeuvres in June to November 2024 in its FCC report (as summarised by Kratos), and Starpath reports 207,152 in December 2025 to May 2026. We publish no dollar market size: we have no reputable public estimate for this layer to cite.
Where we win and lose against classical methods.
| Workflow | Result against classical methods |
|---|---|
| Safety floor, scored runs of the released code (operator approved everything; the gates held it) | Unsafe commands sent: 0 of 1,952; an earlier build's two-person defect (1,281 of 2,434 unsafe) was found and fixed |
| Conjunctions | Tie at a higher cost: a tuned classical solver matched the agent's miss count with about a third of the unneeded manoeuvres and far less fuel (full trade-off) |
| Fleet anomaly | Loss: slower to the cause and no alarm reduction, where classical methods were faster and reduced alarms |
| Gateway outage (partial match) | Detects fastest (1.0 min; event-driven, while the classical solver checks every 5.0 min); the classical solver restores service faster |
| Staged rollout, storm surge | No matched comparison. Measured alone: bad rollouts halted before the full fleet in 20 of 20 runs; 0 of 11 high-risk storm events missed |
Read the full section
The full tables, with their caveats, are on the Benchmarks page. Two workflows trail classical methods today; both are published. All figures come from scored simulated runs, not flight operations.
One product, one SDK, one safety envelope.
- ConstellOps provides gated AI operations agents across five workflows, with an operations console built for approvals under contact-window deadlines. Current release: v1.0.0.
- The Agentic Operations Stack is the safety-gated agent SDK underneath it: gated actions, autonomy levels, the two-person rule, contact-window deadlines, a signed decision log and record-and-replay. Current release: v1.0.2.
- A separate conformance and benchmark harness scores the product against published results, classical methods and written runbooks on the same seeds, losses included.
The questions investors ask first.
Would a tuned classical rule do just as well? On conjunction accuracy, yes, and on fleet anomalies classical methods did better. The case is not accuracy on one metric: it is the governed path (gates, two-person approval, deadline-aware uplink and a signed record) around every decision, whichever model or solver makes it.
Who are your customers? There are no customers, design partners, letters of intent or advisors yet. We are inviting one design-partner operator to take one workflow through shadow mode and a gated pilot, measured against its own baselines.
Read the full section
Who owns the code, and can we inspect it? Proprietary, all rights reserved. Earlier releases (the SDK up to v1.0.2; the other three up to v1.0.0) were Apache-2.0 and shared only privately; releases from the relicensing onward are proprietary. Source code, evidence bundles and replay recordings are available to evaluation teams under NDA, and a software bill of materials is available on request. All IP is owned by the founder; built independently, with no claim from any current or past employer.
What if the one person behind it is unavailable? ConstellOps is built by one person, and a hiring plan is not yet decided. The stack is deployed in the operator's own account, every decision is replayable offline, and the gates encode the operator's rules.
Export control and certifications? No formal export classification has been made yet, and no certifications are held: no SOC 2, ISO 27001, FedRAMP or flight-software assurance certification.
Market and cost? The market section above is built from public counts; we publish no dollar market size. Pricing is not published; it is discussed in a briefing. Model cost in the benchmark storm was $0.468 per 10-event episode at list price.
Roadmap.
| Now | Next | Later |
|---|---|---|
| Results for all five workflows published with their losses, including held-out conjunction runs; v1.0.0 released; one design partner sought | Faster common-cause diagnosis and an alarm-volume reduction; fewer unneeded manoeuvres without giving back missed events | Shadow mode and a gated pilot with a design partner |
No dates are given. Items move when their evidence exists.
Why this founder.
Designed and developed by Vivek Raja: AWS AI Hero; open-source contributor to Strands Agents, Strands Robots (Physical AI) and harness-sdk.
ConstellOps applies the founder's open-source work on agent frameworks and physical AI to the operations problem where a wrong action is most expensive. Flight-operations authority stays with the operator by design: their Flight Director signs off every stage and their flight rules become the gates. Adding flight-operations depth to the team is an open decision.