Coupled vehicle-state assessment
Evaluate orbit, attitude, finite-burn mass, covariance, and resource state together when screening a mission event.
PrimeRadiants Orbital · Sovereign physical intelligence · Available now
Your mission.Your decision authority.
Turn mission inputs into bounded maneuver and fleet decisions inside your security boundary. Orbital connects orbit, attitude, propulsion, uncertainty, and resources to authorized action or safe hold—with local, no-egress execution and evidence you can replay.
For satellite operators, flight-dynamics teams, constellation managers, and sovereign space programs.
Space mission operations · Local execution · Deterministic · Air-gap capable
Results for your engineering decisions
Resolve the risk. Preserve the mission.
A maneuver decision must account for more than the encounter. Connect vehicle state, available resources, alternate actions, coordination, and service continuity before authorizing the response.
Admissible maneuver or safe hold
Compare candidate actions and counterfactuals against mission constraints, secondary encounters, and execution authority.
Constellation and fleet coordination
Deconflict actions and evaluate disposal policy, protected mission value, and service continuity across the fleet.
Sovereign mission evidence
Keep ephemeris, telemetry, policy, intent, authorization, and replayable decision records under customer control.
Benchmarks and test conditions September 2026
Fleet decision · p99
Decision benchmark across 10,000 assets.
Service continuity · p99
10,000 assets and 100 service cells in the fleet benchmark.
Decision-record lookup · p99
100 queries across 10,000 records with exact-match replay.
Independent replay programs
Delivered with the module and customer self-test.
What you can do today
From mission state to authorized action.
Connect mission state, tracking data, spacecraft constraints, and operating policy. Compare a maneuver with a safe hold, assess the effect on fleet continuity, and retain the evidence behind the authorized decision.
Explore the supported workflows
- 01
Understand the state
Evaluate orbit, attitude, mass change during a burn, uncertainty, resources, and event conditions together.
- 02
Assess the event
Connect authorized telemetry and tracking information to the operator’s decision workflow.
- 03
Choose a maneuver or hold
Compare alternatives, check secondary effects, and retain coordination and execution authorization.
- 04
Coordinate the fleet
Plan campaigns, deconflict actions, track disposal policy, and assess service continuity.
- 05
Keep mission control
Retain custody of ephemeris, telemetry, mission policy, and operational intent across supported deployments.
Compare the architecture and technical ecosystem
Where the product fits
Scientific models become operating infrastructure.
PrimeRadiants connects native scientific models to sovereign operational decisions. Fusion is the first commercial market; the same PRX architecture spans orbital systems, quantum hardware, electromagnetics, materials, and hypersonics.
Compare the execution models
| Capability | CAE / HPC physics | Learned physics models | Conventional control | PrimeRadiants PRX |
|---|---|---|---|---|
| Scientific basis | Numerical physics solvers | Trained model, often with physics constraints | Control laws and plant models | Native scientific execution |
| Time to action | Workload and solver dependent | Fast inference after training | Real-time control loops | Near-real-time qualified decision transactions |
| Training requirement | No model training required | Model training or fine-tuning | Usually no model training | No training required |
| Required inputs | Geometry, conditions, material models, calibration | Training inputs, validation, operating inputs | Telemetry, setpoints, plant parameters | Authoritative inputs required by the physics transaction |
| Data custody | Local, HPC, cloud, or hybrid | Local, edge, or cloud; model pipeline dependent | Typically on-device or local | Customer-controlled, air-gapped, no-egress capable |
| Design | Engineering analysis and optimization | Prediction and optimization within model coverage | Control-system design and tuning | Integrated scientific design workflows |
| Operations | Simulation and external operational integrations | Inference integrated into operating workflows | Monitoring and regulation of the target system | Integrated physics-to-decision workflows |
| Physical control | Controller integration or co-simulation | Controller integration and assurance | Core function | Bounded, physics-aware, fail-closed control |
| Replay | Solver and saved-state dependent | Model, version, and inputs dependent | Model and control-log dependent | Source-bound independent replay |
| Evidence | Solver outputs and workflow records | Model, dataset, and experiment records | Telemetry and event logs | Native transaction evidence and provenance |
| Deployment | Workstation, cluster, cloud, or HPC | GPU workstation, server, cloud, or edge | Desktop, embedded, or industrial hardware | Terminus Station appliance |
| Across domains | Solver and product-suite dependent | Model training or adaptation by domain | Plant- and application-specific | One reusable PRX architecture across physical domains |
Explore the approaches: CAE / HPCLearned physicsReal-time control
Technical ecosystem references
Orbital brings coupled orbit, attitude, and resource constraints into maneuver decisions and fleet coordination—with mission data and decision history under your control.
NASA CARA
Conjunction assessment, risk analysis, and mitigation form distinct parts of an operational collision-risk workflow.
Our focus
Carry supported mission inputs through event assessment, maneuver-or-hold selection, and operator authorization.
Read NASA CARA documentationKayhan Pathfinder
Conjunction assessment, maneuver suggestions, tertiary-conjunction checks, and operator coordination.
Our focus
Bring coupled spacecraft constraints, fleet continuity, and replayable decision evidence into your own operating environment.
Read Kayhan Pathfinder documentationAnsys ODTK
Orbit determination uses measurement processing, filtering, and smoothing to produce state estimates for mission analysis.
Our focus
Use supported mission-state inputs to compare actions, coordinate the fleet, and preserve the decision record.
Read Ansys ODTK documentationBuilt for your engineering team
Your workflow. Results with receipts.
Run Orbital on Terminus Station and connect supported CCSDS messages and SPICE data to your mission workflow. The evaluation includes native integration tools, saved decision records, independent replay, and a local self-test.
Cryptographic proof pack
Every maneuver has a decision record.
SHA-256Immutable identityContent-addressed evidence
Review the mission state, maneuver alternatives, operating constraints, and authorization behind an action or safe hold. Reopen the same record for independent replay.
- Traceable inputs
- Mission state, telemetry, resources, policy
- Explainable results
- Maneuver alternatives and decision rationale
- Independent checks
- Native replay, authorization, and policy checks
Explore the evidence: One mission decision. Its evidence intact.
Inside the mission proof pack
Carry a maneuver-or-hold decision from assessment through coordination and authorization. Retain the mission-state inputs, policy constraints, alternatives, and record needed for operator review.
4.291 ms
Fleet decision · p99
Decision workflow across 10,000 simulated assets.
0.815 ms
Service continuity · p99
10,000 assets across 100 service cells.
3.709 ms
Record lookup · p99
100 queries across 10,000 immutable records.
69
Native consumer replays
Independent replay programs delivered with the module.
Independent integrity checks
Source, applicability, policy, and verifier failures stop acceptance. The installer validates archive identity before making a verified generation available.
Verify and reuse the saved result
Load and independently replay saved mission decisions with their inputs, constraints, and operator history intact. Retain the evidence needed for review and rollback.
Work with us
Put mission decisions inside your boundary.
Bring your mission data, maneuver or fleet decision, operating policies, and decision deadline. Start with a shadow workflow before granting actuation authority.