Quickstart: explore the demo fleet
Load a ready-made fleet into the workspace you are in and see what Passes tells you about its next 48 hours: expected GB for every pass, with its range and why. It takes a few minutes, works on the free Explore plan, and needs nothing of your own.
The demo fleet is one Earth observation operator: 5 ground stations with 7 antennas and 6 Earth observation satellites, 5 sun-synchronous and 1 geostationary. NOAA 20, NOAA 21, Suomi NPP, Landsat 9 and Sentinel-2C fly in low Earth orbit on X and Ka band; GOES 19 sits over the Americas on its L-band broadcast. The stations are KSAT Svalbard and Troll, NASA Fairbanks, AWS Ohio and a Singapore teleport, plus the telemetry of the passes in the last two hours. Its polar stations see a pass every orbit, Ohio and Singapore a few a day, and rain puts the Ka passes that rise low, and the ones at the tropical Singapore site, at risk. Its radio values are nominal, not datasheet values.
Every day it plays out the same events, in UTC:
- Troll is down for planned maintenance from 06:00 to 09:00. Its passes in that window are dropped from runs and never offered as a swap backup, and its telemetry has a gap.
- A rain cell crosses Singapore from 17:00 to 20:00. Its Ka passes there fade by about 14 dB at 40 degrees, so rain-fade swap moves one to Troll or Svalbard. Every 48 hours ahead holds one, so a swap is always waiting. The step is labeled Simulated wherever Passes shows where a value came from, and the run's line carries a neutral Demo rain chip, apart from the amber chip of a model fallback. Your own stations never get this rain.
- GOES 19 never sets over Ohio's L-band antenna. Passes shows it as one continuous link with its GB per day, kept out of the pass counts and the expected total.
- Each antenna needs time to lock at the start of a pass, and some passes lose the modem for a minute or so: their telemetry has gaps, and the sample pass log lists them as short. It also lists passes failed in the rain cell or in maintenance, and passes missed while the antenna was busy.
The data is simulated. The mission names, NORAD ids, orbits and station sites are real and public; the antennas, acquisition and slew times, maintenance, the rain cell, the link telemetry and the outcomes of its passes are simulated. None of it is telemetry from, or access to, these missions.
1. Load the demo fleet
Sign in. Fleet opens, and on an account with no fleet it says No fleet on this account yet. Choose Load the demo fleet. It loads into the workspace you are in, the one named in the account menu.
Fleet, Passes, Forecasts and Automations now sit in a frame labeled Demo fleet. The tabs read with a session made from your sign-in, so no key is needed to see them. With satellites or stations of your own beside it, the frame goes but the label stays, as Demo fleet · beside your own, and on Fleet each of the demo's rows is marked Demo; Passes labels the demo workflows' runs Demo fleet, never Live.
Keep it current, reset it or remove it
The demo's telemetry ends when it loads, and its runs price the 48 hours from then. So while the workspace holds the whole demo and nothing of your own, the Platform loads it again once a session: the telemetry is rewritten to end now, and a demo workflow whose newest run ends within 24 hours gets a new run. Your edits stay. Once satellites or stations of your own sit beside it, the Platform no longer reloads it on its own.
- Reload the demo, in the line under the top bar, does the same on demand. It also adds back any demo satellite or station you removed.
- Reset the demo, on Fleet, also puts today's demo back over every demo satellite and station you edited, and starts a new run of each demo workflow. Your own satellites, stations and workflows stay, and so does a demo satellite you moved to a NORAD id of your own: it is yours from then on.
- Remove the demo, beside them in the line under the top bar, asks first, then removes the demo's satellites, stations and workflows from the workspace. Your own assets stay. The demo's simulated telemetry is not deleted: it names only the demo's antennas, so once the demo is gone nothing reads it, and it ages out with telemetry retention.
The demo's telemetry never counts toward your telemetry usage, however often it reloads.
2. Passes is already priced
The load also saves two workflows, Pass yield (pass-yield) and Rain-fade swap (rain-fade-swap), and starts a run of each over the next 48 hours. Open Passes: within a minute it shows every pass of the window priced. A workflow of your own under either name is never replaced.
Both deliver over the API only: they send nothing to a mission control system or destination, so on Automations their Health reads Ready · readable over the API. On Explore their runs are test runs: they price every pass and deliver nothing. A paid plan's runs deliver; on a trial, each swap reads as what Act, which sends recommendations to your mission control system, would do; on Operator each swap is shown as advice; on Operator + Act, each swap waits for your approval under Waiting on you.
3. Read the next 48 hours
Upcoming shows:
- Expected: the GB the window should deliver, with the floor it would reach if every pass had its low case;
- At risk: the passes that could fail or that a step could not price, and how many fall under a contract minimum if you set one;
- the timeline of passes per ground station, and the passes that need a look.
To price the window again later, choose Price the next 48 hours; see Price the window.
4. Open a pass
Choose any pass. The right pane opens with one sentence on what it should deliver and what could stop it, then its expected GB with its range, and under Why each step's value, unit and source, from SNR and weather fade to expected GB. Copy API call gives the request behind it. Reading a result explains each part.
5. Go further
- Audit a past week. Choose Upload 7 days of pass logs, in the line under the top bar, and use the sample pass log the audit offers for the demo fleet. See Free audit.
- Try a what-if. Take an antenna down, or add fade, under Scenarios on Forecasts.
Move to your own fleet
The demo and your own fleet can share a workspace, but they are easiest to tell apart when they do not:
- Recommended: a new workspace. Under Settings, Workspaces, choose + New workspace, switch to it, and build your fleet there from the catalog; see Planned fleet. The demo stays where it is, for when you want it.
- In this workspace. On Fleet, choose Choose from the catalog. With your first picks the catalog asks what happens to the demo: Replace the demo with these (the default) removes the demo's own satellites and stations in the same save, and Keep the demo beside them keeps it, each of its rows marked Demo. When the last demo satellite and antenna go, the two demo workflows go with them, unless you saved over them.
- Remove the demo at any time, as above.
With the API
The Platform reloads an all-demo workspace once a session; with the API, load it again after a break with the call below: it keeps your edits to the demo, rewrites the telemetry to end now, and runs the demo workflows again where their newest run ends within 24 hours. Add ?reset=true to put today's demo back over your edits. You do not need to reload before forecasting; ask for SNR with at at a time inside a pass, as in the quick start; a demo link has fresh telemetry only during a pass, so link_ids answers no_telemetry between them. The same fleet is one call, POST /topology/demo-fleet, with a key that has config:write, and telemetry:write for the telemetry:
curl --fail-with-body -sS -X POST \
-H "x-api-key: $CONSTELLATION_API_KEY" \
"https://api.constellation.space/topology/demo-fleet"
An account with a network config of its own answers 409 network_config_exists and is left as it is. To remove the demo, send DELETE to the same path; see Remove the demo fleet. The demo's satellites never count toward Explore's limit of 2 satellites of your own, in the network config, in runs or in pass lists, and they are never billed. Only a demo load marks them: the same satellites sent in a network config of your own, or a demo satellite moved to another NORAD id, count as yours. With satellites of your own past 2 beside them, Passes asks which 2 of yours to price; see Price the window. The same fleet is on Hugging Face, as the dataset constellationspace/demo-fleet-v2, to study offline.
Next: make your first automation.