Spectral Autonomy

pntOS: The Open Plugin Architecture for PNT Sensor Fusion

Part of the Open Architecture Field Guide. All information is derived from unclassified, publicly releasable (Distribution A) sources.

pntOS is a government-owned, open-source plugin architecture for positioning, navigation, and timing. It lets a developer add or swap a navigation sensor or algorithm as a plugin without touching the rest of the system. It is built on the ASPN data standard, originated at the Army's C5ISR Center, and as of June 2026 is governed by the PNT Standards Consortium.

What it does

Fusing navigation sensors into one position solution is hard software, and it has usually been built as one tightly coupled system. Adding a new sensor, or trying a better filter, meant working inside that system and understanding all of it. A specialist in inertial navigation could not contribute a filter without also learning the sensor drivers and the network code.

pntOS separates the pieces. It is a plugin framework. Sensor plugins for GPS, inertial, vision, and signals of opportunity feed a common core, and algorithm plugins for navigation filters and integrity monitoring process what the core provides. A developer writes one plugin in their own area of expertise, in isolation from the others, and pntOS fuses the plugins into a navigation solution.

The pntOS plugin architecturepntOS is a plugin framework. Sensor plugins for GPS, inertial, vision, and signals of opportunity feed a common fusion core, and algorithm plugins for navigation filters and integrity monitoring process what the core provides. Each plugin is written independently.SENSOR PLUGINSGPSInertialVisionSignals of opportunitypntOS coresensor fusionALGORITHM PLUGINSNav filterIntegrity monitor
Spectral Autonomy
pntOS is a plugin framework: sensor and algorithm plugins are written independently and fused into a navigation solution by a common core.

Where it sits

pntOS is part of the PNT family. Its plugins exchange data in the ASPN format, so pntOS and ASPN work as a pair: ASPN standardizes the measurements, pntOS is the software that consumes them. pntOS runs on SOSA- and CMOSS-aligned hardware. As of June 2026, pntOS and ASPN moved from single-owner stewardship to the PNT Standards Consortium, which puts them under the kind of multi-stakeholder governance that other durable standards already have.

The open PNT standards: ASPN and pntOS, used by R-EGI and Army systemsASPN is the shared navigation data standard. pntOS is the open fusion framework built on it. The Air Force's R-EGI and Army PNT systems both build on pntOS and ASPN, which are governed by the PNT Standards Consortium.R-EGIAir ForceArmy PNT systemspntOSopen fusion frameworkASPNshared navigation data standard
Spectral Autonomy
The Air Force's R-EGI and the Army's PNT systems both build on pntOS and ASPN.

Where this fits

FAQ

What kinds of plugins does pntOS support?
Sensor plugins such as GPS, inertial, vision, and signals of opportunity, and algorithm plugins such as navigation filters and integrity monitoring, each written independently.
Is pntOS an operating system?
No, despite the name. It is a plugin architecture and application framework that runs on a normal operating system.
How does pntOS relate to ASPN?
pntOS is built on the ASPN data standard. ASPN defines the measurement format; pntOS is the software that fuses ASPN-format data.
Who governs pntOS?
As of June 2026, the PNT Standards Consortium. It was originally stewarded by the Army's C5ISR Center.

Sources