Nomos Orbital
What we can do, what we will not pretend, and where we are going.
Nomos reasons over real orbital and infrastructure data to determine how a request should move through the space stack. The intelligence layer is live. Missing integrations are labeled, never invented.
- LIVE
- Working in the product now, on real data.
- REFERENCE
- Real public facts in the registry, with citations.
- SIMULATED
- Modeled behavior, always labeled as such.
- PLANNED
- Requires provider integration. Never claimed early.
Today
Live product capabilities
Safe to claim on customer surfaces. Each capability carries the truth class visitors will see on a mission brief.
CAP · 01
- Provider
Public catalog search
Discover real Sentinel scenes over a drawn area of interest via Microsoft Planetary Computer STAC.
- Calculated
Contact opportunity calculation
SGP4 / Skyfield pass windows from CelesTrak TLEs, live when fresh and pinned when not.
- Estimated
Feasible route comparison
Rank satellite, ground, and cloud patterns with explicit feasible, conditional, and rejected plans.
- Live
Truth-labeled mission briefs
Every headline value carries a truth status. Assumptions and unavailable integrations stay visible.
- Live
Private anonymous planning
Visitor missions stay in an HttpOnly session. Share links are explicit; missions are not enumerable.
- Observed
Owner CPU demo
Optional fixture GeoTIFF crop and thumbnail on the production worker. Measured durations are observed, not invented.
Boundary
Requires provider integration
These appear on plans as unavailable or conditional. Nomos does not invent tasking, reservations, or prices.
CAP · 02
Not connected
Satellite tasking
Plans that need a tasking API remain conditional until a provider is connected.
Not connected
Ground-station reservation
Coordinates may be public. Operational booking is not live.
Not connected
Onboard execution
Edge and satellite compute providers are cited from public facts, not claimed as connected.
Not connected
Private telemetry
No private fleet feeds. Public TLEs and catalog metadata only.
Not connected
Commercial pricing guarantees
Cost fields stay unavailable until a real pricing source exists.
Aspire
The direction we are building toward
Aspiration, not a shipped claim. The near-term product earns this future by staying useful and honest today.
CAP · 03
01
Legible orbital decisions
Every workload route should remain something a human can direct, audit, and trust as compute moves farther from Earth.
02
Satellites as collaborators
Machinery in orbit should become agentic partners on human missions, not opaque schedulers that discard most of what they collect.
03
A planning layer above operators
Nomos is not a satellite operator or data reseller. The long product is the verification layer that binds those systems together.
Forward
Moving on from here
Ordered by dependency, not marketing urgency. Nothing below is claimed as live until it ships with sources.
CAP · 04
Near
- Provider sandbox and partner connections beyond public-data citations
- Live catalog asset download where allowlists and signing permit
- Richer ground-track geography when the API can expose coordinates
Next
- Accounts, organizations, and enterprise authentication
- Real node adapters for connected cloud and edge providers
- Commercial pricing once a verifiable source exists
Later
- Live satellite tasking and station scheduling through partners
- Onboard and orbital GPU execution with observed results
- Webhooks and cryptographic event signing
Prove it
See the network’s real output, or run your own request.
Curated examples disclose what is real, calculated, estimated, simulated, and unavailable. The historical job demo remains for developers who want routing scores and lifecycle events.
Prefer the customer path. The historical simulation demo uses a production API with SIMULATED execution and detections.