A LEO satellite operator running a constellation of more than 40 spacecraft came to us with a problem on a clock. Their mission control system processed thousands of telemetry parameters per second, issued commands with zero margin for error, and was built on Java Swing and Oracle Forms two decades ago. It was scaling badly, and the engineering team that knew it best was getting smaller every quarter.
We delivered the replacement in 16 weeks.
What was breaking
Three problems drove the project:
- Telemetry lag. Operators saw multi-second delays rendering heavy telemetry graphs at peak load. In orbital operations, latency is a liability, not an inconvenience.
- A development wall. Adding a single feature — visualizing a new antenna beam, for example — took weeks of refactoring against a tangled code path. The interface itself raised the operator error rate.
- No remote access. The system required a heavy client on dedicated workstations. Remote diagnostics and mobile access were structurally impossible.
The team had already evaluated the obvious paths. React and Angular failed performance proof-of-concepts: virtual DOM diffing produced visible jank rendering 50,000+ data points per frame. Low-code platforms like Retool and Appsmith couldn’t handle the custom binary CCSDS protocols or the write-back command logic.
That’s where DEX Framework came in.
Why DEX fit the workload
DEX Framework isn’t a wrapper around React. It’s a compiled TypeScript framework built specifically for data-intensive enterprise applications, and two architectural decisions matter for satellite work.
No virtual DOM. Telemetry flows as a continuous high-frequency stream. A virtual DOM forces the framework to diff the entire component tree on every frame. DEX compiles surgical bindings between the data stream and DOM nodes directly. A dashboard rendering 20 real-time charts and a 10,000-row grid consumed 80% less CPU than its React equivalent in side-by-side benchmarks.
View-Service separation. CCSDS packet decoding usually ends up tangled inside UI components. DEX enforces a split: a TelemetryService class runs in a Web Worker, parses binary packets, manages WebSockets, and buffers data. The MissionControlView subscribes to the processed output. Backend and frontend engineers worked in parallel without blocking each other for the duration of the project.
How the 16 weeks unfolded
Weeks 1 to 4: logic migration. Instead of rewriting thousands of lines of PL/SQL and Java by hand, we ran the legacy code through DEX Forms, our migration engine. Command validation rules — including constraints like prevent solar panel deployment if the satellite is spinning — extracted automatically into type-safe TypeScript services. 100% of business rules survived without manual reverse engineering.
Weeks 5 to 8: the high-performance grid. Operators need situational awareness at a glance. We deployed the native <DEX.Grid> component, which sidesteps the re-render pitfalls common in libraries like ag-grid when custom cell renderers are in play. A heatmap view of battery status across the constellation updates cell-by-cell without re-rendering the surrounding row.
Weeks 9 to 12: UX and accessibility. The new UI introduced a high-contrast dark mode for dimly lit control rooms, full keyboard navigation for rapid response, and WCAG 2.1 compliance out of the box. The last item alone unlocked government contracts the legacy system could never bid on.
Weeks 13 to 16: testing and deployment. Because the services were decoupled from the views, the team wrote thousands of unit tests simulating satellite anomalies without ever clicking through a UI.
The numbers after launch
| Metric | Legacy system | DEX Framework |
|---|---|---|
| Cold start | 45 seconds | 1.2 seconds |
| Telemetry latency | 2 to 3 seconds | under 50ms |
| Access | Dedicated workstations | Any browser |
| Licensing | Oracle and Java | $0 |
| Operator onboarding | 3 months | 2 weeks |
The takeaway for technology leaders
Mission-critical systems are where framework choice stops being a preference and starts being an outcome. General-purpose frameworks excel at e-commerce and content sites. They become bottlenecks under high-frequency data. Low-code platforms move fast until the requirements get specific. DEX Framework occupies the gap: native-grade performance, type-safe code, and a development cadence that lets engineering focus on the actual work — in this case, safely operating assets in space.