Platform

The live platform, running the real engine

Everything below executes against live orbital data, the real weather forecast, and the live vendor catalog. No mockups, no canned responses.

Try it

Plan a collection right here

This form talks to the running Zerosat engine. Start the server with zerosat serve, open this page from it, enter a target, and get the optimizer's answer with its full reasoning.

Pick on the map:Click to set the latitude and longitude.
-180-120-60060120180-60060San FranciscoNew YorkLondonMoscowCairoMumbaiBeijingTokyoSingaporeSydneyRioCape Town
An equirectangular coordinate grid, no basemap tiles. Cities are anchors only.
Target a polygon instead of a point
When filled in, this ring replaces the latitude and longitude fields. A single scene must fit the polygon inside its swath; anything wider belongs in cover mode.
Compare two configs side by side
Each config is a JSON object merged over the base request above. For example: {} (no change) vs {"sensor": "SAR"} (force radar).
  zerosat, live
The result will appear here.
Vendor catalog

Every constellation Zerosat plans across

Coverage planning

Plan points, areas, and mosaics

Coverage Report

Per-day pass counts and plan feasibility over a date range.

Live Stream GET /v1/cover/stream

Paris polygon (~15 km cells, 48 h horizon). Each cell result arrives as a server-sent event.

Live Alternatives GET /v1/plan/stream

London (51.5, -0.12), 1.5 m GSD, 24 h horizon. Each scored alternative arrives as a server-sent event before the engine picks the winner.

Cross cue

One sensor tips the next

The multi-INT payoff. An RF geolocation of an emitting vessel that has gone dark on AIS becomes a tip that tasks a confirming SAR collect through cloud or night. Both stages run through the same optimizer, so each carries its own real access, weather routing, and readable rationale.

Pick on the map:Click to set the latitude and longitude.
-180-120-60060120180-60060San FranciscoNew YorkLondonMoscowCairoMumbaiBeijingTokyoSingaporeSydneyRioCape Town
An equirectangular coordinate grid, no basemap tiles. Cities are anchors only.
  POST /v1/cross-cue
Run a cross cue to see an RF detection tip a confirming SAR collect.
Approvals workflow

Propose, approve, bill, order

The spine of the tasking console. A requirement becomes a priced proposal against the live plan, an operator approves or rejects it, and an approval fires a Stripe test mode invoice and a provider order. Nothing is billed to a real card and no live vendor order is placed; this is the human in the loop gate the product runs on.

Pick on the map:Click to set the latitude and longitude.
-180-120-60060120180-60060San FranciscoNew YorkLondonMoscowCairoMumbaiBeijingTokyoSingaporeSydneyRioCape Town
An equirectangular coordinate grid, no basemap tiles. Cities are anchors only.
Loading...
Contention

Competing requests, one pass

Real tasking is contended: two customers want the same satellite minute. Submit a queue and the optimizer plans it as a whole, priority preemption, budgets, and dedup included. Edit the scenario and rerun it.

  POST /v1/plan-queue
Run the queue to see who wins the contended pass.
Standing monitors

Watch a site, replan on cadence

A monitor is a standing requirement: every cadence the engine replans it against live orbits and weather, skips what is already covered, and records the decision to the audit trail. Point monitors compete through the queue; polygon monitors tick as whole mosaics.

Monitor a polygon as a mosaic instead
When filled in, the monitor covers this area as a mosaic every cadence, at scene scale cells.
Loading...