About
Who builds OrbitRoute
OrbitRoute is built by Clayton Camera, a technical founder in Orlando, FL — solo, from the live SGP4 physics engine to the published SDKs to the 700+ tests behind every deploy, with 5 USPTO provisional applications filed on the methods. It answers one question: for a given GPU workload, when does orbital compute beat terrestrial cloud — priced honestly, physics included.
If you got a cold email from us, this page is the human behind it. No sales team, no growth department — every reply comes from the person who wrote the routing engine.
What's real today
- Live SGP4 tracking of 11,000+ satellites from public TLE feeds, refreshed continuously.
- Physics-honest scoring engine — ground-station pass windows, eclipse/battery power state, weather-dependent link choice, and queue depth all feed every routing decision.
- Published SDKs and a public, documented API.
- Public SLA calibration scoreboard — every managed job is graded predicted-vs-actual, in the open, at /sla.
- 700+ automated tests behind every deploy.
What's not yet
- No commercial orbital capacity exists to route to. Nobody sells orbital GPU-hours today — so execution on orbital targets is simulated, and every API response labels it that way. Our pricing model puts early orbital capacity at a multiple of terrestrial cost, which means terrestrial wins on price today and our engine says so. The simulated execution path is the integration seam: the day an operator sells real orbital GPU-hours, they plug into a routing layer that already works.
- 0 paying customers yet. We're early — which is exactly what a design-partner seat buys you: the founder directly, and an engine shaped around your real workloads. If you run GPU jobs at scale, that seat is open.
Intellectual property
5 USPTO provisional patent applications filed (March 2026) covering the routing and scoring methods.
Contact: hello@orbitroute.ai — we reply within 1 business day.