Top 10 Best Indoor Routing Software of 2026

GITNUXSOFTWARE ADVICE

Transportation Logistics

Top 10 Best Indoor Routing Software of 2026

Top 10 indoor routing software picks ranked for routing quality, with indoor map references and tradeoffs for teams. Includes Skydio, Google, HERE.

29 min readUpdated AI-verified · Expert reviewed
How we ranked these tools
01Feature Verification

Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.

02Multimedia Review Aggregation

Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.

03Synthetic User Modeling

AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.

04Human Editorial Review

Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.

Read our full methodology →

Score: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

Indoor routing software turns indoor location and venue data into turn-by-turn paths using a routed graph, live positioning inputs, and configurable map data pipelines. This best-list ranks platforms by routing accuracy, navigation behavior in complex layouts, integration options via APIs and SDKs, and evidence-ready evaluation signals for operators and technical teams.

Esri ArcGIS Indoors is the best fit for GIS teams that need governed indoor routing and shared venue map publishing, while IndoorAtlas is a strong alternative if you want repeatable route guidance tied to an SDK for venue apps.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Esri ArcGIS Indoors

Indoor navigation graph stored in the ArcGIS Indoors data model with routing-ready connectivity.

Built for fits when GIS teams need governed indoor routing and shared venue map publishing..

2

Pointr

Editor pick

Waypoint-driven guided routing combined with geofencing outputs for scripted indoor experiences across venues.

Built for fits when venue teams need turn-by-turn navigation plus event triggers across multi-floor spaces..

3

IndoorAtlas

Editor pick

Navigation APIs that consume live indoor location estimates for dynamic rerouting behavior across a venue graph.

Built for fits when venues need repeatable indoor route guidance tied to SDK location..

Comparison Table

1
enterprise
9.2/10
Overall
2
enterprise
8.9/10
Overall
3
API-first
8.5/10
Overall
4
enterprise
8.2/10
Overall
5
enterprise
7.8/10
Overall
6
API-first
7.6/10
Overall
7
API-first
7.2/10
Overall
8
API-first
6.9/10
Overall
9
API-first
6.5/10
Overall
10
API-first
6.3/10
Overall
#1

Esri ArcGIS Indoors

enterprise

Enterprise indoor mapping and wayfinding platform built on ArcGIS.

9.2/10
Overall
Features9.1/10
Ease of Use9.5/10
Value9.0/10
Standout feature

Indoor navigation graph stored in the ArcGIS Indoors data model with routing-ready connectivity.

ArcGIS Indoors centralizes indoor navigation inputs in an indoor GIS data model that links facilities, floors, POIs, and connectivity edges so route computation has consistent topology. It provides map rendering for indoor layers, configurable search and navigation experiences, and integration points that let teams embed indoor maps into web and mobile client experiences. Automation is largely driven through ArcGIS workflows and publishable services rather than a standalone indoor-only engine.

A key tradeoff is that high-quality routing depends on disciplined venue data preparation, especially for CAD floor plan ingestion and connectivity alignment between floors and transitions. ArcGIS Indoors fits venues that already operate in an ArcGIS-centered environment and need shared governance across IT, facilities, and operations. Teams can use it to publish consistent wayfinding across kiosks, internal dashboards, and guest-facing apps when indoor datasets and update processes are in place.

Pros
  • +Indoor graph-driven routing built from consistent venue connectivity data
  • +CAD-to-indoor map ingestion supports repeatable venue publishing workflows
  • +REST services and client-friendly map layers for embedding wayfinding experiences
  • +ArcGIS governance supports RBAC-aligned publishing across teams
Cons
  • Route accuracy drops when floor transitions and paths are poorly digitized
  • Requires ArcGIS ecosystem skills to configure publishing and routing services
  • Indoor data updates can be operationally heavy for frequently changing venues
  • Advanced accessibility routing needs careful constraint configuration
Use scenarios
  • Facilities and GIS operations teams

    Maintain multi-floor venue wayfinding

    Fewer map mismatches during updates

  • Retail and venue digital teams

    Embed indoor directions in web kiosks

    Consistent guest navigation UI

Show 2 more scenarios
  • Enterprise developers

    Build custom routing experiences

    Custom apps on shared datasets

    They consume routing and map services through REST endpoints and supported client integrations.

  • Accessibility and compliance stakeholders

    Run barrier-free navigation

    Routes aligned to accessibility needs

    They apply accessibility constraints during route computation to respect barrier-free path requirements.

Best for: Fits when GIS teams need governed indoor routing and shared venue map publishing.

#2

Pointr

enterprise

Location platform for indoor positioning, navigation, and digital wayfinding in complex venues.

8.9/10
Overall
Features8.9/10
Ease of Use8.7/10
Value9.0/10
Standout feature

Waypoint-driven guided routing combined with geofencing outputs for scripted indoor experiences across venues.

Pointr’s core workflow centers on converting CAD and venue layouts into an indoor routing data set, then using that data for navigation graph traversal during runtime. It supports multi-floor pathing and delivers route guidance suitable for blue-dot tracking experiences in venue apps. It also includes eventing for location-aware triggers such as geofencing, which pairs with waypoint-driven experiences like assisted routes and kiosks.

A key tradeoff is that routing quality depends on clean floor plan inputs and map alignment, which adds upfront content work before runtime routing is reliable. Pointr fits teams that already manage venue map updates and want deterministic routing behavior across frequently visited zones, including malls, museums, and hospitals.

Pros
  • +Indoor routing graph traversal supports turn-by-turn guidance
  • +Geofencing event outputs fit location-aware navigation flows
  • +Waypoint sequencing enables guided routes for kiosk and mobile
  • +Multi-floor routing supports venues with vertical circulation
Cons
  • Routing quality is sensitive to CAD to map alignment
  • Automation and API coverage can require engineering involvement
  • Complex venue updates may require reprocessing routing data
  • Accessible routing depth depends on venue data preparation
Use scenarios
  • Retail operations teams

    Route shoppers to promotions and departments

    Higher route completion rates

  • Hospital digital teams

    Direct patients through accessible paths

    Fewer wayfinding mistakes

Show 2 more scenarios
  • Museum experience teams

    Run guided tours across exhibit clusters

    More structured visitor flows

    Waypoint sequencing supports tour steps that adapt to where visitors are.

  • Venue app engineers

    Embed navigation and handle route events

    Shorter integration cycles

    SDK and API endpoints support embedding routing with custom UI and analytics.

Best for: Fits when venue teams need turn-by-turn navigation plus event triggers across multi-floor spaces.

#3

IndoorAtlas

API-first

Indoor positioning platform with navigation and route guidance for mobile and location-aware applications.

8.5/10
Overall
Features8.2/10
Ease of Use8.7/10
Value8.8/10
Standout feature

Navigation APIs that consume live indoor location estimates for dynamic rerouting behavior across a venue graph.

IndoorAtlas supports SDK embedding for mobile apps that need blue-dot tracking and routing updates tied to indoor location estimates. Venue onboarding workflows connect CAD or map sources into a navigable indoor graph used for multi-floor pathfinding. Routing output can be consumed through REST navigation APIs and integrated into custom front ends that render route guidance on venue maps.

A key tradeoff is that location stability depends on the site setup quality, including sensor conditions and map alignment, which can require iterative tuning. IndoorAtlas is best suited for venues that already run indoor maps as an operational asset and need repeatable routing for kiosks, mobile staff tools, or passenger wayfinding across multiple zones.

Pros
  • +Indoor routing integrates directly with indoor positioning SDK outputs
  • +Multi-floor navigation works from venue graph traversal primitives
  • +Map ingestion supports practical onboarding from venue map sources
  • +REST navigation API fits custom app UX and map rendering
Cons
  • Indoor alignment and sensor conditions can require iterative tuning
  • Routing configuration may demand GIS and venue layout discipline
  • Limited out-of-the-box admin workflows for complex RBAC patterns
  • Kiosk-grade UX often needs custom front-end work for guidance rendering
Use scenarios
  • Retail operations teams

    Wayfinding across stores and service corridors

    Lowered wayfinding friction

  • Hospital facilities teams

    Barrier-free path routing by ward

    Improved accessibility compliance

Show 2 more scenarios
  • Transit venue developers

    Indoor-outdoor handoff for stations

    More reliable arrival guidance

    Routing can switch from outdoor context to indoor navigation using indoor location estimates.

  • University campus app teams

    POI waypoint sequencing for visitors

    Fewer missed destinations

    Apps can guide visitors between buildings with multi-floor path traversal using venue maps.

Best for: Fits when venues need repeatable indoor route guidance tied to SDK location.

#4

MazeMap

enterprise

Indoor maps and navigation software for campuses, offices, hospitals, and large buildings.

8.2/10
Overall
Features8.1/10
Ease of Use8.4/10
Value8.2/10
Standout feature

Accessible routing that calculates barrier-free options during indoor navigation graph traversal for turn-by-turn guidance.

MazeMap focuses on indoor wayfinding that combines map tile rendering, destination guidance, and multi-floor pathfinding in one navigation flow.

Routing accuracy depends on how the venue is modeled for navigation, including connectivity between floors and walkable spaces.

Integrations are centered on embedding navigation experiences and serving routing requests for kiosk and web surfaces.

Pros
  • +Turn-by-turn indoor routing works across multi-floor navigation flows
  • +Embedded map and navigation views fit kiosk and web integrations
  • +POI-driven guidance supports landmark and destination-based directions
  • +Accessible routing options target barrier-free path requirements
Cons
  • Requires accurate venue map ingestion to maintain routing quality
  • Limited evidence of deep automation for large multi-venue publishing workflows
  • Accessibility behavior depends on how paths and entrances are modeled
  • Real-time rerouting effectiveness varies with on-site positioning signals

Best for: Fits when indoor wayfinding teams need embedded routing plus POI directions across floors for a single venue or rollout plan.

#5

Mappedin

enterprise

Indoor mapping platform for directories, wayfinding, and route guidance across commercial venues.

7.8/10
Overall
Features7.7/10
Ease of Use7.9/10
Value8.0/10
Standout feature

Venue-specific navigation graph generation from imported floor data, which drives turn-by-turn step sequences across floors.

Mappedin converts venue CAD and GIS inputs into navigable indoor maps and then serves turn-by-turn wayfinding with venue-specific POIs. It supports a venue wayfinding graph for multi-floor pathfinding, with configuration for entrances, accessible routes, and kiosk-ready start points.

Routing output can be exported for integration workflows and accessed through an API that returns navigation steps and guidance metadata. The system also supports ongoing map updates so changes to floors, corridors, and POIs propagate to routing behavior.

Pros
  • +Turn-by-turn routing that matches venue geometry and POI context
  • +Multi-floor pathfinding via a venue navigation graph
  • +Kiosk and signage workflows driven from the same map dataset
  • +API access for route results and navigation step integration
Cons
  • CAD floor plan ingestion requires disciplined cleanup for best results
  • Accessibility configuration needs explicit per-venue route constraints
  • Advanced navigation quality tuning takes iterative venue testing
  • Indoor-outdoor handoff behavior depends on how entrances are modeled

Best for: Fits when venues need accurate multi-floor wayfinding with an integration-ready API and controlled accessibility routing.

#6

Navigine

API-first

Indoor navigation and positioning platform for wayfinding, asset tracking, and location analytics.

7.6/10
Overall
Features7.8/10
Ease of Use7.5/10
Value7.3/10
Standout feature

Routing configuration tied directly to imported venue floor assets for consistent multi-floor POI pathing.

Navigine targets venues that need indoor turn-by-turn routing tied to real-time indoor positioning. Its core workflow centers on importing venue floor information, then producing navigation paths between POIs across rooms and multiple levels.

The solution supports BLE beacon grid deployments and can render venue maps for on-device guidance. Administrators control routing behavior through configuration of navigation assets like POIs, entrances, and accessibility options.

Pros
  • +Multi-floor routing that maintains continuity between levels
  • +Configurable POI and entrance definitions for predictable route starts
  • +BLE beacon-based indoor positioning suitable for controlled venues
  • +Venue map rendering for in-app navigation views
Cons
  • Venue data prep and routing configuration require disciplined governance
  • Change cycles can be slow when POIs or paths need frequent updates
  • Indoor accuracy depends heavily on beacon placement quality
  • API use requires integration work rather than simple drop-in mapping

Best for: Fits when venues need multi-floor pedestrian routing with BLE beacon guidance and controlled content updates.

#7

Oriient

API-first

Indoor GPS platform for precise in-building navigation and location-based user journeys.

7.2/10
Overall
Features7.3/10
Ease of Use7.0/10
Value7.3/10
Standout feature

CAD-to-route ingestion pipeline that converts venue layouts into route-ready navigation graphs for waypoint sequencing.

Oriient is indoor routing software focused on turning venue maps into navigable routes for pedestrians across multi-floor spaces. It centers on CAD floor plan ingestion workflows, map rendering for venue environments, and waypoint-based route generation that can be surfaced in kiosks and mobile web.

Automation support is geared toward keeping POI lists, navigation paths, and reroute behavior synchronized when venue layouts change. Integration depth is oriented around embedding routing results into existing apps through a documented API surface and structured exports.

Pros
  • +CAD floor plan ingestion workflow reduces manual map-to-route work.
  • +Waypoint sequencing supports consistent POI-based direction flows.
  • +Indoor-outdoor handoff patterns work for entrances that span map layers.
  • +Export and embed paths help integrate routing into existing apps.
Cons
  • Navigation graph traversal setup needs careful geometry cleanup of plans.
  • Live dynamic rerouting coverage is limited for highly changing crowd states.
  • Advanced occupancy-aware routing requires extra data wiring outside core flows.
  • Kiosk mode configuration can be tedious when menus and exits change often.

Best for: Fits when venue operators need CAD-to-route automation with controlled waypoint flows and app embedding.

#8

Situm

API-first

Indoor positioning and navigation software with SDKs, mapping tools, and route guidance.

6.9/10
Overall
Features7.1/10
Ease of Use6.8/10
Value6.7/10
Standout feature

Situm’s navigation graph and waypoint content pipeline is designed for serving turn-by-turn guidance from a managed venue map without rewriting client logic.

Situm focuses on indoor routing backed by device positioning, with an SDK and venue integration workflow aimed at turn-by-turn guidance. Its core capability is generating navigation-ready maps from venue assets, then serving route guidance through developer-facing interfaces.

Situm also supports BLE beacon grid deployments for positioning in spaces where GPS is unavailable, and it can package waypoint and POI data for client apps. Admin workflows target multi-venue operations so updates to maps and navigation content can propagate without rebuilding client apps.

Pros
  • +SDK-oriented navigation integration for iOS and Android apps
  • +Venue map ingestion workflow supports multi-floor routing
  • +Positioning deployments based on BLE beacon grid enable offline indoor guidance
  • +Navigation content updates can be managed separately from app releases
Cons
  • Indoor accuracy depends on beacon planning and signal consistency
  • Advanced routing outcomes require disciplined map and POI data hygiene
  • Extensibility for custom waypoint logic can be limited without deeper integration work
  • Large venues need careful configuration to avoid routing friction during updates

Best for: Fits when venue operators need developer-controlled indoor routing with repeatable map updates.

#9

Steerpath

API-first

Indoor positioning and navigation SDK for mobile applications.

6.5/10
Overall
Features6.1/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Waypoint-based routing that keeps direction guidance consistent across multi-floor trips with QR-style destination entry workflows.

Steerpath provides indoor routing for mapped venues, turning a venue map into navigation that can follow multi-floor paths. It supports waypoint-based directions and route guidance for pedestrian use cases, including kiosk-style operation and hands-free flows.

Configuration centers on importing venue geometry and landmarks, then validating navigation connectivity for turn-by-turn guidance. For integration, Steerpath focuses on embedding routing into apps via documented API endpoints and event-style interactions for guidance updates.

Pros
  • +Kiosk-ready guidance flows for unattended navigation sessions
  • +Waypoint sequencing supports multi-destination routing in one trip
  • +Multi-floor routing handles floor-to-floor transitions in a single route
  • +API access supports app embedding of routing and guidance events
Cons
  • Venue map import requires careful geometry cleanup to avoid broken links
  • Limited visibility into route scoring makes optimization tuning harder
  • Dynamic rerouting coverage can lag behind sensor updates during movement
  • Accessibility routing needs extra configuration to reflect venue constraints

Best for: Fits when venue operators need indoor turn-by-turn routing across multiple floors with kiosk and app access.

#10

Proximi.io

API-first

Indoor positioning and navigation platform combining multiple location technologies.

6.3/10
Overall
Features6.0/10
Ease of Use6.4/10
Value6.5/10
Standout feature

REST navigation API that returns navigation and waypoint sequences suitable for embedded kiosk and app turn-by-turn flows.

Proximi.io is an indoor routing software solution focused on turn-by-turn navigation inside mapped venues. It centers routing on a venue graph built from indoor map data and supports navigation delivery via an API for app and kiosk deployments.

Integration work is oriented around connecting a positioning input to the navigation engine and handling multi-floor route continuity. Governance and operations depend on how route data is provisioned and updated across environments.

Pros
  • +REST navigation API designed for embedding routing into apps and kiosk flows
  • +Indoor route computation uses a navigation graph that supports multi-floor travel
  • +Waypoint sequencing supports predictable instruction order along a computed path
  • +Geospatial export compatibility helps integrate with existing mapping pipelines
Cons
  • CAD floor plan ingestion and venue mapping require disciplined preprocessing
  • Dynamic rerouting depends on timely position updates from the selected sensor stack
  • Accessibility-specific routing needs explicit rule mapping in the venue data
  • Map tile rendering and front-end visualization work often require separate integration effort

Best for: Fits when teams need an API-driven indoor navigation graph with consistent multi-floor routing across apps and kiosks.

Conclusion

After evaluating 10 transportation logistics, Esri ArcGIS Indoors stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Esri ArcGIS Indoors

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

How to Choose the Right indoor routing software

Indoor routing software connects venue floor maps to navigable paths so apps and kiosks can produce turn-by-turn guidance across multi-floor spaces.

This buyer’s guide covers Esri ArcGIS Indoors, Pointr, IndoorAtlas, MazeMap, Mappedin, Navigine, Oriient, Situm, Steerpath, and Proximi.io to compare routing graph design, API integration depth, and admin governance over venue publishing.

The tool stack varies from ArcGIS Indoors graph-driven routing built for GIS teams to REST navigation APIs like Proximi.io that target embedded kiosk and app workflows.

Indoor routing software for multi-floor wayfinding graph traversal and route delivery

Indoor routing software turns imported venue layouts and POI definitions into a navigation graph that clients can traverse to generate route steps and waypoint sequences.

Esri ArcGIS Indoors stores routing-ready connectivity in the ArcGIS Indoors data model so it can deliver indoor graph-driven routing with controlled venue publishing workflows.

Pointr pairs waypoint-guided routing with geofencing event outputs to support scripted indoor experiences across floors when the CAD-to-map alignment is kept tight.

Across the category, the differentiators show up in how each platform builds and serves the routing graph, how API surfaces accept live position estimates for dynamic rerouting, and how admin tooling supports repeatable venue updates and POI change cycles.

Indoor routing graph design, API surface, and venue governance

Indoor routing quality depends on how each platform builds a navigation graph from venue assets and POI definitions so clients can traverse edges into route steps and waypoint sequences. Esri ArcGIS Indoors emphasizes an ArcGIS Indoors data model that stores routing-ready connectivity built for governed venue publishing workflows.

  • Routing-ready connectivity stored for governed publishing

    Esri ArcGIS Indoors keeps routing-ready connectivity inside the ArcGIS Indoors data model so routing stays aligned with repeatable venue publishing workflows. Mappedin also generates a venue navigation graph from imported floor data to drive turn-by-turn step sequences across floors.

  • API-driven route delivery for embedded kiosk and apps

    Proximi.io provides a REST navigation API that returns navigation and waypoint sequences for embedding into kiosk and app turn-by-turn flows. Situm supports SDK-oriented navigation integration for iOS and Android apps so clients receive guidance from a managed venue map without rewriting routing client logic.

  • Waypoint sequencing tied to event triggers

    Pointr combines waypoint-driven guided routing with geofencing event outputs for scripted indoor experiences across multi-floor venues. Steerpath uses QR-style destination entry with waypoint sequencing to keep direction guidance consistent across multi-floor trips.

  • Dynamic rerouting behavior from live indoor positioning estimates

    IndoorAtlas focuses on navigation APIs that consume live indoor location estimates to support dynamic rerouting across a venue graph. Esri ArcGIS Indoors can deliver graph-driven routing with controlled publishing, but route accuracy drops when floor transitions and paths are poorly digitized.

  • Accessibility and barrier-free route generation

    MazeMap performs accessible routing that calculates barrier-free options during indoor navigation graph traversal for turn-by-turn guidance. Mappedin offers controlled accessibility routing but needs explicit per-venue route constraints to produce consistent barrier-free outcomes.

  • CAD-to-route ingestion workflow depth and cleanup expectations

    Oriient runs a CAD-to-route ingestion pipeline that converts venue layouts into route-ready navigation graphs for waypoint sequencing. Indoor routing quality in Navigine also depends on venue data prep tied to imported venue floor assets, and it can slow change cycles when POIs or paths update frequently.

Choose based on routing graph control, automation depth, and client integration shape

The main fork is whether indoor routing should be governed inside a GIS ecosystem with repeatable venue map publishing or operated as a navigation graph service for app and kiosk embedding. Esri ArcGIS Indoors fits governed indoor routing and shared venue map publishing for GIS teams, while Proximi.io targets API-first delivery across apps and kiosks with a REST navigation interface.

  • Select the venue publishing model that matches the organization

    If venue content needs to be governed through consistent map publishing, Esri ArcGIS Indoors provides an indoor navigation graph stored in the ArcGIS Indoors data model with routing-ready connectivity. If venue teams prefer venue-specific graph generation from imported floor data, Mappedin generates a venue navigation graph from imported floor data to drive multi-floor turn-by-turn step sequences.

  • Match the integration shape to the client stack

    If the deployment uses embedded kiosk and mobile apps that expect an API response, Proximi.io returns navigation and waypoint sequences via its REST navigation API. If the deployment expects SDK-oriented navigation integration, Situm provides iOS and Android SDK navigation integration from a managed venue map.

  • Decide between event-triggered scripting and live-position dynamic rerouting

    If the indoor experience needs scripted flows that react to location boundaries, Pointr combines turn-by-turn guidance with geofencing event outputs across multi-floor spaces. If the indoor experience needs rerouting behavior driven by live location estimates, IndoorAtlas focuses on navigation APIs that consume indoor positioning SDK outputs for dynamic rerouting.

  • Plan for accessibility constraints in the routing workflow

    If barrier-free route calculation is a core requirement, MazeMap calculates barrier-free options during indoor navigation graph traversal for turn-by-turn guidance. If accessibility rules are expected to vary by venue, Mappedin requires explicit per-venue route constraints to deliver consistent accessibility routing.

  • Validate CAD alignment and route geometry cleanup capacity

    If CAD-to-map alignment can be maintained with tight geometry control, Pointr can deliver turn-by-turn guidance through routing graph traversal but is sensitive when CAD and map layers misalign. If the process includes CAD cleanup and iterative tuning, Oriient and IndoorAtlas both expect careful geometry cleanup and alignment, with Oriient converting CAD layouts into route-ready graphs and IndoorAtlas tuning indoor alignment and sensor conditions.

Who benefits from indoor routing software built on graph traversal and waypoint delivery

Venue operators and integrators benefit when indoor routing can be embedded into apps and kiosks with multi-floor traversal, repeatable venue updates, and predictable POI direction steps. Esri ArcGIS Indoors and Navigine suit teams that treat venue connectivity as managed content tied to map publishing workflows.

  • GIS teams and venue map publishers

    Esri ArcGIS Indoors stores routing-ready connectivity inside the ArcGIS Indoors data model and supports CAD-to-indoor ingestion for repeatable venue publishing workflows with governed connectivity.

  • Venue operations teams running event-driven wayfinding

    Pointr pairs waypoint-guided routing with geofencing event outputs so venue apps and systems can trigger actions during turn-by-turn guidance across floors.

  • Mobile and SDK integrators building dynamic rerouting

    IndoorAtlas exposes navigation APIs that consume live indoor positioning SDK outputs so routing decisions can update as positioning changes during navigation.

  • Accessibility-focused wayfinding deployments

    MazeMap calculates barrier-free options during indoor routing graph traversal for turn-by-turn guidance, which reduces the need to bolt on accessibility logic at the client layer.

  • Unattended kiosk wayfinding programs

    Steerpath is built around kiosk-ready guidance flows with waypoint sequencing and QR-style destination entry for multi-floor trips without on-site staff.

Common failure points when deploying indoor routing graph services

Route accuracy fails when floor transitions, paths, and entrances are poorly digitized or misaligned across CAD and map representations. Esri ArcGIS Indoors routing-ready connectivity still drops accuracy when floor transitions and paths are poorly digitized, and Pointr routing quality is sensitive to CAD-to-map alignment issues.

  • Treating CAD ingestion as a one-time file upload with no geometry cleanup

    Oriient and Navigine both tie routing outcomes to CAD-to-route ingestion or imported venue floor assets, so venue layouts need disciplined cleanup to avoid broken links and incorrect connectivity.

  • Skipping multi-floor entrance and connectivity definitions

    MazeMap and Mappedin rely on indoor navigation graph traversal that must include correct entrances and POI context across floors, so missing entrance definitions cause route steps that jump or dead-end.

  • Assuming dynamic rerouting works without stable sensor and update timing

    Proximi.io explicitly depends on timely position updates from the selected sensor stack, and IndoorAtlas requires alignment and tuning when sensor conditions change across areas.

  • Overlooking accessibility constraints that must be configured per venue

    Mappedin accessibility routing needs explicit per-venue route constraints, and MazeMap barrier-free routing still depends on accurate venue map ingestion to keep routing graph edges usable for barrier-free paths.

How We Selected and Ranked These Tools

We evaluated Esri ArcGIS Indoors, Pointr, IndoorAtlas, MazeMap, Mappedin, Navigine, Oriient, Situm, Steerpath, and Proximi.io using feature depth, ease of deployment for venue publishing and routing configuration, and overall value for indoor routing outcomes. Features accounted for 40% of scoring because routing graph design, turn-by-turn delivery mechanisms, and accessibility handling drive real route quality.

Ease/value each accounted for 30% because CAD-to-map alignment discipline, iterative tuning needs, and integration workflow shape onboarding time for venue teams. Esri ArcGIS Indoors separated itself by storing routing-ready connectivity inside the ArcGIS Indoors data model and supporting CAD-to-indoor ingestion workflows that support repeatable venue publishing for governed indoor routing.

Frequently Asked Questions About indoor routing software

How do ArcGIS Indoors and Mappedin build a routing graph from venue assets?
ArcGIS Indoors generates an indoor navigation graph from GIS and venue data and stores the result in the ArcGIS Indoors data model for routing-ready connectivity. Mappedin converts imported CAD and GIS inputs into navigable indoor maps, then serves multi-floor wayfinding based on venue-specific POIs and a wayfinding graph.
Which tool returns turn-by-turn steps through an API that works for both apps and kiosks?
Proximi.io exposes a REST navigation API that returns navigation and waypoint sequences suitable for embedded kiosk and app flows. Steerpath also embeds routing into apps via documented API endpoints and event-style interactions for guidance updates.
How do Pointr and Oriient handle waypoint sequencing for guided indoor navigation?
Pointr provides waypoint-driven guided routing and pairs it with geofencing outputs for scripted indoor experiences across venues. Oriient generates waypoint-based route generation from CAD floor plan ingestion workflows, then surfaces waypoint flows in kiosks and mobile web.
What breaks if IndoorAtlas cannot map live indoor location estimates to the navigation graph?
IndoorAtlas routes depend on navigation APIs that consume live indoor location estimates, so missing or drifting location signals reduce the correctness of dynamic rerouting behavior. MazeMap can keep rerouting behavior tied to its indoor navigation graph and map data, but it still needs a reliable path-following context to adjust turns at the right moment.
When should teams choose Navigine with a BLE beacon grid versus MazeMap for standalone graph traversal?
Navigine targets deployments that need indoor turn-by-turn routing tied to real-time indoor positioning, and it supports BLE beacon grid deployments for guidance. MazeMap focuses on serving embedded wayfinding with POI directions and accessible route options, and it can support dynamic rerouting without requiring beacon grid positioning to rebuild navigation content.
How do Google Navigation SDK integrations typically differ from HERE-style routing engines for indoor map content?
Google Navigation SDK-based indoor flows usually integrate the positioning and turn-by-turn guidance layer into apps through SDK embedding, which shifts indoor map readiness work to the venue content pipeline. HERE-style stacks often emphasize map and routing services that consume venue map layers and produce navigation guidance, so indoor routing quality hinges on the completeness of the venue map schema and navigation graph.
How do admins manage updates to POIs, entrances, and multi-floor connectivity in Situm and Navigine?
Situm packages waypoint and POI data for client apps and uses admin workflows so map and navigation content can propagate to multi-venue operations without rewriting client logic. Navigine centers administrators on routing configuration tied directly to imported venue floor assets, so updates flow through controlled changes to navigation assets like POIs and accessibility options.
What security controls and audit trails are needed for indoor routing configuration changes in ArcGIS Indoors and Mappedin?
ArcGIS Indoors relies on governance features within the ArcGIS ecosystem to manage the content lifecycle across departments that publish indoor maps and routing layers, which supports controlled updates to routing-ready graph content. Mappedin’s integration-ready API exposes routing output and metadata, so configuration governance must cover how venue map updates and accessibility routes propagate into the served navigation responses.
How does each tool support data migration when venues change floor plans or corridor layouts?
MazeMap’s dynamic rerouting can adapt user routes without forcing a full rebuild of navigation content, but floor layout changes still require updating the indoor navigation graph inputs tied to POI and accessible route options. Proximi.io depends on how route data is provisioned and updated across environments, so migration quality depends on whether venue graph and waypoint sequences are re-provisioned consistently with the updated map.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Logos provided by Logo.dev

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.