Polyrhythm Software Founded to Build Software for Aerospace Programs

Polyrhythm Software launched in Dayton, built for the engineering culture around Wright-Patt. Founded by John Farrier, Polyrhythm brings senior engineering judgment to advanced software, modeling and simulation, mission systems, and flight-test support.

DAYTON, Ohio, October 31, 2023. Polyrhythm Software launched as a Dayton-based software engineering company serving organizations that need software they can integrate, test, secure, and change without losing control.

Polyrhythm was founded by John Farrier, who previously co-founded Hellebore Consulting Group, a Dayton-area software company. Polyrhythm builds on that history of engineering support for hard aerospace problems, especially where software has to work with hardware, test data, security constraints, and mission operations.

Polyrhythm’s founding team brings prior experience leading software architecture, DevSecOps, simulation, hardware integration, and flight-test support for advanced aerospace programs. That background matters because the most expensive software problems on complex programs often start before code volume is large. They start when interfaces are vague, test evidence is weak, or the delivery path is built after the system design has already hardened.

“Software gets expensive when interfaces blur, evidence weakens, and every change becomes a rediscovery effort,” said Farrier. “Polyrhythm was created to help teams keep control of the software layer before integration debt becomes the program.”

Based near Wright-Patterson Air Force Base, Polyrhythm is shaped by the Dayton region’s long connection to aviation, research, acquisition, and flight test. That ecosystem rewards engineering teams that can connect design decisions to evidence and fielded support.

The company initially plans to support experimental aircraft developers with hardware and software design. That includes early architecture decisions for embedded software, ground support tools, data flows, simulation hooks, and test artifacts. The goal is to help teams choose patterns that can survive integration, test, and fielded use instead of forcing a late rebuild when prototypes turn into programs.

Polyrhythm’s model is intentionally focused: small, senior teams; direct technical ownership; reusable engineering patterns; and practical artifacts that program teams can review, test, and sustain. That model is meant for situations where a few strong engineers can clarify the boundary between system behavior, software behavior, test evidence, and operational constraints.

That focus also keeps the company close to the work. Polyrhythm expects its engineers to write code, review interfaces, shape tests, and help teams understand the risks behind a design choice. The work may start with a prototype, a simulation, a data path, or a troubled integration. In each case, the company looks for the point where clearer software architecture can reduce program risk.

Polyrhythm Software launched with a narrow view of growth. The company is not trying to be a broad staffing firm. It is built to take ownership of specific engineering problems where architecture, interfaces, evidence, and maintainability shape whether a system can move from concept to use.

“The goal is not more software,” Farrier said. “The goal is the right software the program can leverage, field, and evolve.”