Cockpit teams
Build multiple surfaces on one route source of truth.
AutoBuild your programEmbedded software
Navigation Runtime
The route and guidance engine behind every entitled cockpit surface.
Provide device map access, search, routing, guidance, route state, voice and structured display outputs through stable platform-independent contracts.
Value by stakeholder
Built around measurable operating outcomes.
Each product is shaped around the team that buys, integrates, operates or experiences it—not an isolated feature checklist.
Platform teams
Reuse a stable runtime across supported OS and hardware.
Lifecycle teams
Trace and update content and runtime independently.
Capability system
What the product is designed to do.
Final scope, data, territory, vehicle interfaces, performance and availability are confirmed for each OEM program.
Offline map access
Read entitled, versioned and integrity-checked regional content.
Search & route
Calculate profile-aware places and routes within runtime capability.
Guidance state
Produce deterministic maneuvers, progress, reroute and arrival state.
Structured outputs
Publish map, route, lane/junction, voice, cluster and HUD contracts.
Hybrid adapters
Merge entitled traffic, incidents, search and EV information.
Diagnostics
Expose map/runtime/profile/route versions and reproducible traces.
Delivery choices
Fit the OEM ownership model.
- ✓C++/Rust runtime and stable IPC/C APIs
- ✓Android/AAOS, Linux/QNX adapters
- ✓SDK, examples, golden routes and conformance suite
Program guardrails
Claims stay attached to evidence.
- !Identical inputs yield traceable route/guidance results
- !Active offline route survives cloud loss
- !Content/runtime compatibility is checked before use
OEM program workshop
Define the production shape of Navigation Runtime.
Capture the vehicle line, territory, users, surfaces, interfaces, deployment, validation and lifecycle. The result becomes a focused OEM discovery brief.