Demo mode

Demo mode lets you explore the console with a sample fleet before connecting your own telemetry. Inspect assets, ask the assistant for statistics and charts, simulate gateway outages, and watch an imaging mission move through capture, orbital compute, and ground delivery.

Open the demo

Open the console as a Guest to explore the demo fleet. If signed in, open Settings → Fleet and enable Demo mode. Turn it off to return to your account's fleet view; live data requires an eligible account and a configured connection.

Demo mode does not unlock prediction access.

Demo and live workspaces keep separate histories and analysis artifacts. Switch back to the workspace where you created a chart, report, or scenario to find it. Saved work remains local to your browser profile.

Explore the fleet

Try these requests in order. Results depend on the loaded assets, available samples, and selected time.

Request	What to inspect
"Summarize the loaded fleet."	Asset counts, health, and the data available for analysis.
"Show mean utilization by ground station over the last hour."	The grouped chart, actual history coverage, and excluded samples.
"Simulate an outage at the busiest gateway."	The gateway selected from measured traffic and the resulting connectivity changes. If traffic is unavailable, choose a named gateway from the scene.
"Which scenario changes are active?"	The mutations currently affecting analysis.
"Reset the scenario."	Return to the original fleet before starting the next experiment.
"Show service availability over Tokyo for the next 24 hours."	Passes, service gaps, coverage, and the model's assumptions and asset exclusions.

Select nodes and links on the globe to inspect their details. Use the timeline to pause, scrub, or replay the loaded window. The assistant's tool reference explains the available calculations and scene controls.

Run an imaging mission

Ask:

Image the Panama Canal.

Other supported target examples include the Strait of Hormuz, South China Sea, Odesa, and Port of Rotterdam. A recognized target still needs a feasible pass and route within the loaded scene window.

The run_mission tool plans a simulated sequence:

1. An operator ground terminal sends tasking through a communications satellite.
2. The task reaches an Earth-observation satellite, which captures the target during a suitable pass.
3. The raw image travels over inter-satellite links to orbital compute.
4. The modeled inference job processes the image.
5. The processed result returns through a communications satellite and downlinks to an available operator terminal.

The downlink destination is a ground terminal, not the place being imaged. Watch the highlighted route, capture beam, and mission log in chat. The log reveals events as the simulation clock reaches them. The console adjusts the camera and playback for the mission; longer workloads may play at an accelerated rate.

A dispatched mission is scheduled to play out. Capture, compute completion, and ground delivery are separate milestones. A result can finish processing and remain onboard if no downlink contact is available.

Try distributed orbital compute

Ask:

Image the Panama Canal with a heavy workload and spread the inference across orbital data centers.

run_mission supports three workload presets:

Workload	What it demonstrates
standard	A single-scene job intended to fit on one orbital data center.
heavy	A larger collect that can require several reachable compute assets.
maximum	A more demanding collect for exploring compute and route constraints.

Work is divided among reachable orbital data centers according to modeled thermal headroom. Inspect participating assets during the run to see compute allocation, power, battery state, temperature, and throttling. The number of participants and whether the job completes depend on the scene and available compute window.

What the image and simulation mean

The displayed image is illustrative reference imagery, not a new satellite acquisition. The console uses location imagery from Esri World Imagery, with a labeled synthetic illustration if the image cannot load. The displayed image does not establish that a real spacecraft captured or processed it.

Mission routing, hardware, link budgets, inference, and thermal behavior are modeled. The demo demonstrates the workflow; it does not send tasking commands to operational spacecraft.

If a mission cannot run

Result	Next step
Unknown target	Try a recognized place name from the examples above.
Missing imaging, compute, or ground capabilities	Use a demo scene with the required roles. Changing the target cannot supply missing capabilities.
No feasible pass or route	Try another target or a different available replay time.
Processing incomplete or no ground delivery	Inspect the log for compute or contact constraints; do not treat dispatch as successful delivery.

Demo datasets and predictions

The bundled demo uses authored fleet data and simulated behavior. Some demo builds also offer archive replay, with recorded scene data and a fixed historical span. Available assets, history, and prediction panels can differ between datasets.

In archive imaging demonstrations, Earth-observation roles come from fleet catalog classifications. Orbital data centers are assumed demo roles assigned to existing assets, not verified operational spacecraft capabilities. Mission hardware and thermal values remain model assumptions.

Check each result's source and timestamps. Measured telemetry, replayed values, synthetic demo outlooks, and model forecasts have different meanings. SNR inference requires backend access and may be disabled in a particular build; unavailable predictions do not indicate zero signal quality.

Keep an analysis

Capture an analytical assistant answer into a report, add notes about the demo dataset and assumptions, and export it for sharing.