OrbitFlow Dynamics is the first true autopilot for satellite constellations. We generate the complete, ready-to-execute maneuver command, coordinate it across the fleet, and guarantee its safety mathematically. The human operator retains final authority with a single "Approve & Execute" click — turning your team from ground operators into mission supervisors.
We react to unknown objects in minutes (not days) and handle both cooperative fleet members and non‑cooperative targets (debris, silent spacecraft) with equal rigor.
Close-approach events scale with every satellite added to orbit. Legacy alert systems hand you a risk score and walk away — the planning, coordination, command generation, and execution are still left to your ground team.
Legacy providers stop at the conjunction alert. They tell you something might hit — but they don't tell you what to do about it. You are left to build the maneuver command manually.
When each satellite dodges on its own, fleets burn more propellant than necessary and can create new conflicts while resolving old ones.
Traditional systems wait 24–48 hours for a full tracking record before acting. In a dense LEO environment, that delay is a luxury you cannot afford.
We are an autopilot, not another warning light. Our proprietary stack plans efficient routes, generates ready-to-execute commands, coordinates the entire fleet, reacts to unknowns in minutes, and guarantees safety before every burn.
Our proprietary planning engine generates safe, low‑fuel trajectory options for each satellite. Every candidate is physically realistic and fully explainable — no black box, full regulatory auditability.
A sophisticated decision layer selects optimal joint maneuvers across the fleet. For cooperative operators, we share intent and de‑conflict jointly. For non‑cooperative targets (debris, silent satellites), our adaptive layer responds safely without requiring their cooperation.
Every proposed maneuver is checked against hard separation constraints before it is ever sent to the spacecraft. The final output is a ready-to-upload command file, bundled with its mathematical safety certificate for your review and approval.
While legacy systems wait 24–48 hours for a full tracking record, OrbitFlow reacts safely to unexpected objects — even fresh debris with no tracking history — within minutes. Our adaptive layer handles both cooperative fleet members and non‑cooperative targets with equal rigor.
Prototype walkthrough: intelligent path planning, command generation, fleet‑wide coordination, and adaptive response to unknown objects resolving a multi‑satellite encounter.
LeoLabs, Slingshot Aerospace, COMSPOC, and the 18th SDS are alert engines — they hand you a risk score and walk away. We are a decision engine: we plan, generate the command, coordinate, and guarantee the outcome — while you keep final authority.
Monitoring & alerting — conjunction data messages (CDMs).
Full autopilot — plans, generates commands, coordinates, and guarantees maneuvers.
Manual, or left entirely to the customer's flight dynamics team.
Automated, optimized low‑cost detours with ready-to-upload command files.
None — isolated, satellite‑by‑satellite decision‑making.
Joint optimization across the entire fleet, cooperative & non‑cooperative.
Waits 24–48 hours for tracking before acting.
Reacts safely within minutes to fresh debris/unknowns.
Statistical, probabilistic collision‑probability warnings.
A hard, deterministic safety shield with an audit log and safety certificate.
Delivers a suggestion — operator must manually build and upload the command.
Delivers a ready-to-execute command file with safety certificate; operator reviews and approves.
Operator is the executor — does the heavy lifting to act on the alert.
Operator is the supervisor — reviews the guarantee, clicks "Approve & Execute".
This isn't a nice‑to‑have. It's fuel, staffing, unknown‑object readiness, compliance, and human oversight — the five things that determine whether a constellation is profitable and insurable.
Every unnecessary or oversized avoidance burn shortens a satellite's revenue‑generating lifespan. Finding the mathematical minimum ΔV detour preserves months to years of extra station‑keeping capability.
Close‑approach events scale roughly quadratically with fleet size. No operator can hire enough engineers to hand‑review thousands of daily alerts — OrbitFlow automates the routine 95%+ of screening, planning, and command generation.
Fresh debris appears without warning. Legacy systems wait for a track to build. OrbitFlow's adaptive response layer reacts within minutes — giving your fleet the best chance to avoid an unfolding threat.
Insurers and regulators (FCC, FAA, EU Space Strategy) are demanding stricter, auditable avoidance plans. Our deterministic safety filter and command certificate provide the mathematical proof they require.
OrbitFlow generates the optimal, ready-to-execute command file with a mathematical safety certificate. You review the proof and click "Approve & Execute" when ready. For routine events, set auto-authorization — transforming your team from ground operators into mission supervisors.
The Launch and Early Orbit Phase is the highest‑risk window in a satellite's life — beginning at separation from the rocket and lasting until the satellite reaches its operational orbit and passes initial testing.
The satellite detaches and tumbles chaotically; ADCS fires magnetorquers or reaction wheels to stabilize it.
Ground stations establish telemetry links to verify health, power, and thermal status.
On rideshare launches, dozens of satellites deploy in tight clusters — tracking radars can't easily tell them apart for the first 24–72 hours.
Thrusters raise the satellite from deployment altitude to its assigned operational slot.
Payloads and cross‑links are calibrated before the satellite transitions to normal operations.
Conjunction alerts are now a standing operational cost for every constellation operator. But alerts are not solutions. As maneuver volume climbs toward one million per year, independent per‑satellite avoidance stops being merely inefficient and starts actively working against itself. Operators no longer need another alert system — they need an autopilot that plans, generates commands, coordinates, and guarantees the fleet's response, while keeping them in the loop.
Target customers: LEO constellation operators, SSA providers looking to extend beyond screening into autonomous maneuver planning, and satellite insurers who need an auditable safety case.
Full orbit propagation, two‑stage conjunction screening, verified frame transforms, and the intelligent path planner already run end‑to‑end on synthetic scenarios — including adaptive responses to simulated unknown objects and command-file generation.
Coordination layer integrated with the path planner — a fast, working multi‑satellite baseline.
Unknown‑object detection and minutes‑not‑days reaction logic developed and benchmarked.
Multi‑satellite avoidance and unknown‑object response demonstrated against realistic scenarios.
Pilot deployment with a constellation operator or SSA provider on real conjunction data.
To fund the path from prototype to a validated multi‑satellite autopilot demo, and to bring on a technical co‑founder with orbital mechanics / controls background. We're also looking for a pilot conversation with a constellation operator or SSA provider.
Space Systems Engineer. M.Sc. Satellite Technology, Würzburg / Carleton. Spacecraft autonomy, GNC, and applied machine learning across five countries and seven institutions.
github.com/menatallh →Space Systems Engineer. M.Sc. Satellite Technology, Würzburg / Carleton. Reinforcement learning for constellation design at ZFT Würzburg. Published researcher in spaceborne optical navigation.
github.com/mayhammad277 →