Automotive & Embedded
Build in-vehicle navigation, companion apps, and fleet systems with Farun map data, routing, elevation, nautical layers, and deployable map bundles for Android Automotive OS and embedded Linux.
Early Access: The automotive SDK is in active development. Contact us to discuss your platform requirements and join the early access programme.
MapLibre
GL Native renderer
OSRM
Local routing
API
Companion tools
Embedded bundles for vehicles. APIs for connected software.
Automotive Problems
Some vehicle systems need deployable map bundles and local routing. Companion apps and back-office tools need APIs. The important thing is choosing the right product for the system you are building.
OEMs, embedded teams, and mobility platforms need control over maps, routing, styling, and data deployment instead of relying only on consumer navigation products.
Google Maps Platform and Mapbox stream routes, destinations, and position data to their own cloud infrastructure. Vehicle operators lose control of where that data goes and who sees it.
Commercial map providers restrict layer styling, POI sets, and branding. You can't fully adapt the map experience to match your vehicle's HMI language without rebuilding on an open renderer.
Most navigation SDKs cover roads. Vehicles that operate across terrain or near coastlines commercial trucks, agricultural equipment, marine support vehicles need elevation and nautical data as well. That typically means two separate data vendors.
SDK Architecture
The embedded stack uses MapLibre GL Native, an open-source renderer with a proven track record in production vehicle platforms, combined with Farun's spatial dataset and routing engine.
MapLibre GL Native
The Farun Automotive SDK is built on MapLibre GL Native, the open-source fork of Mapbox GL Native. It runs on Android Automotive OS and embedded Linux without any proprietary runtime. Farun provides the offline map tile bundles, routing engine, and spatial data that power it.
Offline Map Bundles
Map data is delivered as MBTiles bundles, compressed vector tile packages for a specific region. Load them onto the device's storage once and render, route, and search entirely without a network connection. Update bundles via USB or OTA when a connection is available.
On-Device Routing
The routing engine is OSRM-based, packaged to run on the same device as the renderer. Route calculation, rerouting, and POI search happen entirely on-device. The vehicle doesn't need a data connection to navigate from A to B.
Spatial Data Coverage
The same data that powers the Farun GPS Navigator hardware is available for SDK deployments. That includes 30m SRTM elevation data and rich POI database, all accessible from the same offline bundle, with no separate data vendor required.
Without Farun
With Farun
Location APIs
Farun APIs are for developers building mobile companion apps, fleet dashboards, service booking tools, web HMI, and back-office systems on top of the same spatial dataset.
APIs are separate from embedded map bundles. Use them when the workflow lives in connected software.
View all APIsServe MVT tiles from Farun's dataset into your MapLibre GL style for companion apps, web HMI, and pre-baking offline bundles.
Route calculation for companion apps, fleet dispatch tools, and back-office systems running against the same road graph as the on-device engine.
Generate road-network reachability zones for service coverage analysis, dealer catchment mapping, and depot planning.
Early Access
Tell us your target platform, Android Automotive OS, embedded Linux, web HMI, companion app, or fleet backend and what spatial data your application needs.