Straightforward licensing for engineering teams

A device is any compute unit running the PathVynt runtime binary — typically the SoC on each robot (Jetson, x86). Development workstations and CI runners used for testing but not deployed in the field do not count against your device count.

OEM redistribution rights are available under Fleet license with a negotiated OEM addendum. The Evaluation and Team licenses do not include redistribution rights. Reach out to discuss OEM terms.

The integration layer (ROS 2 bridge, Python bindings, C++ thin wrapper) is fully open. The core fusion, prediction, and localization modules are distributed as compiled binaries with comprehensive headers. Source access to core modules is available under Fleet license for certain use cases.

The runtime begins returning degraded-mode warnings but continues functioning for 14 days post-expiry to give your team time to purchase a license. After that period, the runtime will no longer initialize without a valid license key. Your configuration files, maps, and integration code are not affected — they're yours to keep regardless.

Yes — we offer a startup pricing tier (growing team, fewer than 30 employees, not yet at fleet scale) and an academic research license (non-commercial, university affiliation required). Contact us for details. We're a bootstrapped team and we want other early-stage teams to have access to production-quality perception infrastructure.