Our own project: software we built and operate ourselves.
AstrOS Engine
You open the page and watch 50,000 satellites move around Earth, with live NASA and NOAA data. Nothing to install. We wrote the engine from scratch in Rust and compiled it to WebAssembly; WebGPU means the math runs on your graphics card, so everything moves smoothly.
Tens of thousands of moving objects live, with no install
Thousands of moving objects at once usually kill smoothness: the CPU and off-the-shelf libraries cannot keep up, frame after frame. We wanted to prove the browser can carry the whole population when the graphics card does the math. No install, a small download, no dropped frames.
All the work on the GPU, zero CPU cost per object
The orbital elements for ~50,000 satellites are uploaded to the GPU buffer one time, from the real CelesTrak catalog or a procedural fallback.
A WGSL shader propagates every object in parallel (Kepler + J2 + drag). The CPU never touches a single satellite.
The render pass reads positions straight from the buffer (vertex pulling): one draw call per layer, with no rewriting of data on the CPU.
The engine is platform-agnostic: the same code builds real pipelines on a native Metal or Vulkan device, which lets it be tested in headless CI without a browser.
Measured, not claimed
faster satellite-catalog load: the scene starts right away instead of making you wait for the browser to crunch raw data.
objects on the slider: you pick the scale of the scene yourself, and smoothness is measured live, not claimed.
the whole app weighs less than one phone photo: it opens instantly, nothing to install.
The baked blob is the array of GPU elements; decoding is practically a copy, with no per-object math. The realism rides the same zero-CPU-cost path as the rest of the engine. The SGP4 reader itself (pure Rust) matches the CelesTrak reference implementation to within 2×10⁻⁷ km.
Check these numbers yourself in the live demoNASA and NOAA telemetry console
A panel sits over the 3D scene and thinks like a flight controller. Instead of five tables you get the conclusion straight, e.g. "ELEVATED: NOAA WARNING G2". A time slider (×0.125–×4096, log scale) speeds up the simulation, and the aurora on the globe reacts to the real Kp index, a measure of geomagnetic storms. It all works on a phone too.
Every choice has a reason
Got a nagging problem? Describe it, I'll code the rest.
One sentence is enough to start. Tell me what's bothering you. Within 48 hours I come back with a clear answer: can it be done, and at what fixed price.