Key Takeaways

  • Revel provided the operational control software that Oklo Atomics used to take a nuclear reactor critical.
  • The Southern California hard tech sector expanded from 130 companies in 2024 to 279 by 2026, driving demand for modern development tools.
  • Teams engineering rockets and hypersonic aircraft often rely on legacy software stacks dating back to the 1980s and pre-Windows 98 systems.
  • Shifting to modern physical test platforms increases execution rates from 5 tests per week to 50 tests per week.
  • Revel doubled its headcount to roughly 70 employees to manage test infrastructure across nuclear, rocketry, and aviation programs.

The Pre-Windows 98 Bottleneck in Hypersonics

Scott Morton points out an absurd contrast in modern defense and physical engineering. Teams build Mach 5 aircraft and next-generation nuclear reactors, yet their test facilities depend on operating software built before the dot-com boom.

Morton explained the situation directly: “we're replacing, you know, technology from the 80s and 90s. You have these companies building hypersonic jets and they're stuck with like pre Windows 98 era tech.”

When hardware builders rely on tools from the late twentieth century, the entire engineering loop slows down. Every design iteration in physical engineering demands direct validation on a test stand. Engineers cannot push code or approve CAD models without firing the thruster, cycling the valves, or monitoring thermal loads in real time. If the underlying data acquisition system requires hours of manual calibration or locks sensor readings inside obsolete file formats, teams lose entire days waiting on hardware feedback.

Revel stepped directly into this operational gap. Morton described their core mission: “we're providing a platform for testing and controlling physical systems. So think like you know as I said nuclear reactors, jet engine test facilities, rocket engine test sites.”

That platform recently handled the operational control layer when Oklo Atomics brought a nuclear reactor critical. Morton doubled Revel's headcount to roughly 70 people because high-tempo engineering teams cannot afford to let vintage software dictate their release schedule.

The 10x Velocity Math on the Test Stand

Testing frequency dictates how fast a physical engineering program reaches production. If an engineering team spends weeks preparing a single firing, discovery cycles crawl.

Morton identified testing throughput as the single biggest lever in physical development: “testing at all companies is critical path. And so, you know, if we we enable them to test like 50 times in a week instead of five times in a week.”

The math changes the entire organization. When a propulsion team tests once a day, diagnosing an anomaly takes two weeks of post-run debriefs. When that same team runs ten tests a day, technicians modify parts, fire the engine, inspect the telemetry, and validate fixes by dinner. This cadence turns physical prototyping into a fast feedback loop that moves at the speed of modern code.

This shift arrives as physical technology startups multiply. Morton tracked the Southern California hard tech directory moving from 130 companies in 2024 to 279 by 2026. These teams face tight capital constraints and aggressive delivery milestones. They cannot afford three-year qualification cycles governed by software written thirty years ago.

What to Do With This

Audit your primary testing or build loop this week. Track the exact minutes spent between completing an assembly and viewing verified sensor data. If your engineers spend more than twenty percent of their bench time babysitting manual exports, old interfaces, or manual calibrations, replace the legacy stack with modern control software before building your next prototype.