Spacecraft mission analysis workstation
Build your mission in one window. Hypersphere works out every pass, eclipse, coverage gap and close approach, puts what needs action first, and keeps every answer current as the mission changes.
The showcase of example missions is open to everyone. Opening one in the hosted workstation asks for the user name and password the owner hands out.
See it in action
From one satellite and a ground station to the whole Starlink catalog, the Moon and a cruise to Mars: each example mission opens in the same workstation, with its 3D scene, events, analyses and assistant side by side.
A 40-second tour without sound. Thirteen example missions open one after another in the workstation’s Analysis mode, each beside the same Objects list, Overview, Events table and Assistant, while its 3D scene turns and mission time plays: one sun-synchronous satellite and its Svalbard ground station, a Walker constellation over its coverage map, ISS passes over Deep Space Network antennas, Sentinel-2 imaging, the Starlink catalog, LEO operations with the Starlink and OneWeb shells and 19,369 catalogued objects, two satellites sharing a geostationary slot, a rendezvous, ephemeris interchange, a relay mission with its plots and report, and an altitude trade study. Then the Lunar Reconnaissance Orbiter circles the Moon, and the cruise to Mars crosses the inner solar system beside a Hohmann transfer. It closes on the Hypersphere name and hypersphere.fly.dev.
The problem
Everyday mission questions usually mean stitching together several tools, scripts and spreadsheets. Every change to the plan means doing it again, and the answers are hard to check and hard to share.
When can my ground stations reach the spacecraft?
Hypersphere: every pass for every station, with its start, end and highest elevation.
When is it in sunlight, and when in shadow?
Hypersphere: sunlight, penumbra and eclipse by every body that can block the Sun.
What is coming close to it?
Hypersphere: close approaches against whole catalogs, with the time and the miss distance.
How well does it cover the places I care about?
Hypersphere: coverage of a region, with its longest gap and how often it is revisited.
How it works
One workflow in one window. Every view shares the same mission, the same selection and the same clock, so nothing drifts out of step.
A 7-second loop without sound, made from the workstation on the LEO operations example. The window comes apart in layers above its 3D globe, where the Starlink and OneWeb orbital planes circle the Earth: the title bar, the Objects and Views cards, the Overview with its orbital population counts, altitude histogram and orbital plane view, the Assistant, the Events table led by two close approaches, the playback bar and the Scene’s tools. The population tiles, the plane view and the Assistant’s input lift off their own cards, then every panel settles back into the one window.
Describe it to the assistant in plain words, or add it piece by piece: spacecraft from orbit presets, element sets, a CelesTrak catalog or an ephemeris file, then ground stations, targets, sensors and whole constellations.
The assistant runs on Claude Haiku 5.5 or Sonnet 5.5, with no key to set up in the hosted workstation; a workstation you run yourself uses your own Anthropic API key and offers Opus 5.5 as well. It works through the same commands as the buttons you click, and everything one answer changes is a single undo step.
Ask for the answers you need and they arrive on their own. Change an orbit, add a station or move the dates, and every answer it affects is worked out again in the background. There is nothing to re-run.
A 6-second loop without sound, made from the Timeline of the LEO operations example: about 18 hours of ground-station contacts from 23:00 UTC on 14 October 2026, the playhead at 06:40. Its rows peel off the card as glass strips and fan out, the Events row and the contact lanes of seven stations (Goldstone, Canberra, Madrid, Kiruna, Kourou, Svalbard and Fairbanks), each with the ISS and with Landsat 9, then settle back over the time axis.
Nine kinds of analysis
Passes between stations, targets, sensors and spacecraft, with elevation masks.
Sunlight, penumbra and umbra, the shadow fraction and the beta angle.
Spacecraft screened against whole catalogs, with miss distance and severity.
The globe, a band or a region: coverage, longest gap and revisit time.
Elements, apsides and nodes, and the local time of the node.
One object seen from another, with range and closest approaches.
Latitude, longitude and altitude over time, with the node crossings.
How many objects fly where: counts and an altitude histogram.
The burns that reach a new orbit or meet another spacecraft, solved for you to apply.
Events from every analysis land in one list, most severe first, so a close approach stands out from routine passes. Pick one and the clock moves to it, and the 3D scene, the timeline and the details follow.
Ask the assistant for a report and it writes one from the mission’s results and opens it. Or export any table as CSV, or open a Python notebook that is already connected to the mission. Results depend only on the mission and its data, so the same mission gives the same numbers every time.
A 34-second recording without sound of the workstation on the LEO operations example, zoomed in on what matters. The request is typed into the Assistant, running Claude Haiku 5.5, in real time: “Create a report on Landsat 9: its ground station contacts and close approaches, then open it.” Shown four times faster, the assistant looks through the mission’s analyses, waits for the contact and close-approach results and adds a contact analysis for Landsat 9 alone; at normal speed it writes the report and opens it, and its summary follows at twice the speed. The report then opens in Reports mode and scrolls by: the passes and access time at each of the 12 ground stations, 251 passes in all, and two medium-severity close approaches with Fengyun-1C debris, at 3.78 km and 1.76 km.
Every kind of mission
The same workflow for one satellite or a whole catalog, around the Earth, the Moon or the Sun.
Constellations
Load Starlink, OneWeb or every active satellite from a dated CelesTrak catalog, or generate a Walker constellation. Satellites that share an orbital plane are drawn as one ring, so a shell reads at a glance.
Cislunar
Fly NASA’s Lunar Reconnaissance Orbiter from its own ephemeris, see its passes over the IM-1 landing site near the south pole, and when the Deep Space Network can see it past the Moon.
Every orbit regime
Low orbit shells, the GPS, Galileo and BeiDou navigation constellations, highly elliptical Molniya orbits, and geostationary satellites with their station-keeping burns and eclipse seasons.
Interplanetary
Design the 2026 Earth-to-Mars cruise about the Sun from a Lambert departure, fly it beside a Hohmann transfer, and follow it against the planets from departure to arrival.
Answers you can trust
Each example mission ships with checks against analytic formulas, published values and independent brute-force searches, and the test suite runs every one of them on every change.
Passes, eclipses, orbits and coverage are compared with NASA, ESA and USGS figures, textbook formulas and searches written without the engine.
An answer depends only on the mission, its data and the analysis, never on playback, open views or how many processor cores do the work.
Every data file is listed with its source, license and checksum. Outside a file’s coverage an analysis stops and names the file, instead of guessing.
A mission is a plain file in its own folder. The engine goes online for one thing only, a catalog download it asks you about first, and in a workstation you run yourself the assistant uses your own key.
Each one opens from the showcase in the hosted workstation after you sign in, as your own copy.
Try it
The showcase holds every example mission: constellation coverage, close approaches against whole catalogs, a geostationary slot, an orbiter at the Moon and a cruise to Mars. Pick one and it opens in the hosted workstation as your own copy. Change anything, and the answers follow.
Anyone can browse the showcase. Opening a mission asks for the user name and password the owner hands out.
For developers. Every capability is one of 71 commands that Python scripts and AI agents (over MCP) can call too, and a command line checks and exports missions without a window. Python, MCP and the command line