Top 10 Best Indoor Wayfinding Software of 2026

GITNUXSOFTWARE ADVICE

Transportation Logistics

Top 10 Best Indoor Wayfinding Software of 2026

Top 10 indoor wayfinding software ranked by routing accuracy, with comparisons of Mappedin, MazeMap, Living Map, Google Navigation SDK, Mapbox.

31 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 wayfinding software turns building data models into navigable paths using indoor positioning, routing logic, and map provisioning through APIs. This ranked list targets analysts and technical operators who must compare accuracy, routing behavior, and integration workload across platforms without marketing claims, with entries evaluated on measurable positioning and route-finding performance.

Mappedin is the best fit when venue operators need multi-floor routing with POI search across kiosk and mobile, whereas Situm is the smarter alternative if you’re building an indoor wayfinding app and want an SDK-driven positioning backbone.

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

Mappedin

Turn-by-turn indoor directions are generated from the authored indoor connectivity across floors, not from static overlays.

Built for fits when venue operators need multi-floor routing plus POI search across kiosk and mobile deployments..

2

MazeMap

Editor pick

Venue map authoring that links floor plans to navigable waypoints for turn-by-turn routing across floors.

Built for fits when venue teams need reliable indoor routes and maintain curated maps for navigation..

3

Living Map

Editor pick

Routing built from ingested floor plan geometry into an indoor spatial graph for multi-floor guidance.

Built for fits when venues need multi-floor indoor routing from CAD assets and want API-controlled map publishing..

Comparison Table

1
MappedinBest overall
enterprise
9.4/10
Overall
2
enterprise
9.2/10
Overall
3
enterprise
8.8/10
Overall
4
enterprise
8.6/10
Overall
5
enterprise
8.3/10
Overall
6
API-first
7.9/10
Overall
7
API-first
7.6/10
Overall
8
enterprise
7.3/10
Overall
9
enterprise
7.0/10
Overall
10
API-first
6.7/10
Overall
#1

Mappedin

enterprise

Indoor mapping and wayfinding platform for malls, campuses, hospitals, and workplaces.

9.4/10
Overall
Features9.3/10
Ease of Use9.5/10
Value9.6/10
Standout feature

Turn-by-turn indoor directions are generated from the authored indoor connectivity across floors, not from static overlays.

Mappedin supports venue map creation using CAD-derived floor plans, then ties corridors, entrances, and points of interest into navigation-ready structures. Directions and search operate on the authored venue content rather than ad hoc map layers, which makes reroutes and POI updates manageable when layouts shift. The platform also supports embedding and exports for integration into kiosk apps, web experiences, and other internal surfaces that need venue navigation.

A tradeoff is that indoor routing quality depends on the fidelity of the imported floor plans and the effort spent modeling navigation-relevant paths. Teams get the best results when floor plans are maintained and when doorways, corridors, and accessibility paths are authored with consistent naming and connectivity.

Pros
  • +CAD-based venue authoring helps keep navigation geometry aligned
  • +Multi-floor turn-by-turn routing uses authored indoor connectivity
  • +POI management and search stay tied to map navigation
  • +Embeddable map experiences fit kiosk and internal app deployments
Cons
  • Navigation accuracy depends on floor plan cleanup and path modeling work
  • Advanced integrations can require implementation effort beyond map publishing
  • Cross-venue customization takes governance to keep POIs consistent
Use scenarios
  • Airport operations teams

    Wayfinding from terminals to gates

    Fewer lost travelers

  • Large retail chains

    Storewide routing to departments

    Faster in-store navigation

Show 2 more scenarios
  • Hospital navigation managers

    Department routing in multi-wing buildings

    Reduced navigation friction

    Multi-floor directions connect entrances, elevators, and department POIs into a single search-driven experience.

  • Event venue IT teams

    Rapid venue updates for shows

    Timely map refreshes

    Venue authoring workflows support updates to POIs and navigation paths for changing event layouts.

Best for: Fits when venue operators need multi-floor routing plus POI search across kiosk and mobile deployments.

#2

MazeMap

enterprise

Indoor wayfinding and digital twin platform for universities, hospitals, and office buildings.

9.2/10
Overall
Features9.0/10
Ease of Use9.3/10
Value9.2/10
Standout feature

Venue map authoring that links floor plans to navigable waypoints for turn-by-turn routing across floors.

MazeMap targets venues that already have CAD or vector floor plans and want consistent routing across complex layouts. The workflow centers on authoring indoor maps from provided drawings and linking waypoints to navigable areas for multi-floor guidance. The system can power both mobile wayfinding app experiences and on-site kiosk directory use cases. It also maintains navigation logic in a way that supports venue-specific configuration rather than relying only on generic maps.

A tradeoff appears in mapping effort and ongoing content governance for every floor and frequently changing POI set. MazeMap fits teams that have a floor plan ingestion process and a responsible owner for map updates after renovations or temporary closures. A strong situation is onboarding a new venue or reauthoring an existing site to improve route quality and visitor guidance consistency.

Pros
  • +Turn-by-turn indoor routes across multi-floor layouts
  • +Venue-specific map authoring from provided floor plans
  • +Supports kiosk directory style browsing for on-site guidance
  • +Integration-focused embedding for mobile and web surfaces
Cons
  • Map creation and POI maintenance require ongoing governance discipline
  • Routing quality depends on how accurately areas and waypoints are authored
  • Complex venues need extra authoring effort for edge cases
  • Advanced automation depends on integration work around map content
Use scenarios
  • Property ops and wayfinding owners

    Update POIs after renovations

    Fewer visitor reroutes

  • Shopping center guest experience

    Kiosk directory and indoor routing

    Reduced wayfinding friction

Show 2 more scenarios
  • Healthcare facility navigation teams

    Accessible route planning inside buildings

    More predictable arrival paths

    Navigation flows guide visitors through complex layouts toward clinics and departments.

  • Stadium and arena staff

    Match navigation to event signage

    Better crowd flow guidance

    Routes align with entrances and POIs used during event operations.

Best for: Fits when venue teams need reliable indoor routes and maintain curated maps for navigation.

#3

Living Map

enterprise

Digital mapping and wayfinding platform for transport, healthcare, and corporate estates.

8.8/10
Overall
Features8.8/10
Ease of Use9.1/10
Value8.6/10
Standout feature

Routing built from ingested floor plan geometry into an indoor spatial graph for multi-floor guidance.

Living Map’s core workflow typically starts with importing floor plans, then building an indoor navigation graph from that geometry along with waypoints and place data. Routing supports multi-floor movement using connectivity between floors, which matters for conferences and campuses with vertical circulation. The integration path is geared toward teams that need programmatic map publishing and navigation behaviors rather than a manual-only authoring experience.

A tradeoff appears when venues need highly custom positioning logic, because Living Map is stronger at routing and map publishing than at replacing an entire indoor positioning stack. It fits venues that already have a positioning source and want consistent navigation outputs across maps, kiosks, and mobile screens.

Pros
  • +CAD floor plan ingestion supports fast mapping from existing venue assets
  • +Indoor routing connects multi-floor paths with floor-to-floor transitions
  • +API-first map publishing enables programmatic integration into existing apps
  • +POI management supports consistent place metadata across destinations
Cons
  • Advanced navigation tuning can require governance discipline across teams
  • Deep customization of positioning behavior is limited compared to navigation-heavy alternatives
  • Large POI catalogs can make authoring slower when data lacks structure
  • Iterative improvements may depend on reprocessing map geometry and connections
Use scenarios
  • Venue operations teams

    Map wayfinding for multi-floor events

    Fewer help desk navigation requests

  • Experience platform engineers

    Embed indoor navigation into mobile apps

    One navigation experience across apps

Show 2 more scenarios
  • Facilities GIS teams

    Maintain indoor POI layers from CAD

    Reduced drift between maps and reality

    GIS teams keep place data aligned with floor geometry so routes match current layouts.

  • Customer support analytics teams

    Diagnose where routes fail at entrances

    Targeted fixes to entrances

    Teams use routing outcomes and place metadata to identify friction points around complex approach paths.

Best for: Fits when venues need multi-floor indoor routing from CAD assets and want API-controlled map publishing.

#4

Pointr

enterprise

Indoor positioning, mapping, and wayfinding platform using sensor fusion and machine learning.

8.6/10
Overall
Features8.7/10
Ease of Use8.4/10
Value8.5/10
Standout feature

Venue content provisioning that ties POIs, floors, and navigation flows into one configurable wayfinding setup.

Pointr targets indoor wayfinding through venue map authoring workflows and a configurable navigation experience for mobile and kiosk deployment. It focuses on routing and visitor guidance inside multi-floor buildings with a venue directory and point-of-interest based navigation flows.

Pointr’s integration depth centers on linking map content, navigation destinations, and real-time positioning inputs into a single operational setup. Admin control focuses on managing venue content and application behavior without requiring custom route computation per location.

Pros
  • +POI-driven routing flows reduce authoring friction for common destinations
  • +Multi-floor navigation supports indoor spatial graph style path guidance
  • +Kiosk and mobile guidance can share the same venue content structure
  • +Point-of-interest database organization keeps destinations consistent across surfaces
Cons
  • Advanced route customization needs careful map data and destination design
  • Integrations can require more engineering time than basic deep links
  • Turn-by-turn performance depends on correct indoor positioning tuning
  • Governance for multiple venues needs disciplined content change handling

Best for: Fits when venue teams need indoor navigation content reuse across kiosk and mobile deployments.

#5

Concept3D

enterprise

Interactive 3D maps and wayfinding platform for campuses, museums, and convention centers.

8.3/10
Overall
Features8.5/10
Ease of Use8.2/10
Value8.0/10
Standout feature

Geometry-to-routing generation for multi-floor venues that reduces manual linking between floors and POIs.

Concept3D generates indoor navigation content by turning CAD and spatial inputs into 3D-ready venue maps used for mobile and kiosk wayfinding. It focuses on geometric map authoring workflows and spatial graph generation so routing behaves consistently across multi-floor footprints.

The product workflow supports point-of-interest placement and venue configuration for turn-by-turn indoor navigation experiences. Concept3D is best evaluated on how easily those authored maps connect to the chosen mobile wayfinding app or embedded SDK flow.

Pros
  • +CAD-to-indoor map authoring workflow suitable for multi-floor venues
  • +3D-oriented venue data supports clearer context for navigation tasks
  • +Consistent routing hinges on geometry-backed path graph generation
  • +Point-of-interest placement fits typical kiosk and app wayfinding needs
Cons
  • Outcome depends on input map quality and geometry cleanup effort
  • Automation depth is limited outside the core map authoring workflow
  • Integration work is required to connect maps to external app experiences
  • Governance features like RBAC and audit log are not a core differentiator

Best for: Fits when teams need CAD-driven indoor maps that power turn-by-turn routing across multiple floors.

#6

Situm

API-first

Indoor positioning and navigation SDK combining sensor fusion with building maps.

7.9/10
Overall
Features8.1/10
Ease of Use7.9/10
Value7.7/10
Standout feature

Indoor positioning engine tuned for venue deployment so the same location backbone powers both mobile guidance and kiosk-style entry flows.

Situm delivers an indoor positioning and wayfinding stack that targets venues needing accurate location and guided navigation beyond GPS gaps. Core capabilities center on an indoor positioning engine plus SDK support so mobile wayfinding apps and kiosk flows can compute location and route users through multi-floor spaces.

Situm’s authoring and deployment workflow typically revolves around venue map data ingestion and configuration for indoor areas, points of interest, and navigation logic. The result is a fit for teams that want integration-driven wayfinding with a measurable positioning backbone rather than static directory displays.

Pros
  • +SDK-based indoor positioning enables turn-by-turn routing in custom apps
  • +Designed for multi-floor navigation with indoor spatial awareness
  • +Supports BLE and mobile sensor signals for indoor location continuity
  • +Venue configuration workflow supports repeatable deployment across sites
Cons
  • Strong setup discipline is required to keep positioning stable
  • Wayfinding UI needs custom implementation for complex kiosk experiences
  • Indoor map preparation and POI data quality heavily influence routing success
  • Limited out-of-the-box digital signage and dashboarding compared with mapping SDK peers

Best for: Fits when venue operators need SDK-driven indoor wayfinding with reliable positioning and multi-floor routing.

#7

IndoorAtlas

API-first

Magnetic field-based indoor positioning platform with wayfinding SDKs for mobile apps.

7.6/10
Overall
Features7.3/10
Ease of Use7.7/10
Value7.9/10
Standout feature

Sensor-fusion indoor positioning via the IndoorAtlas SDK, designed to improve location fixes for indoor routing.

IndoorAtlas focuses on indoor positioning and routing for venue apps, kiosks, and embedded SDK experiences. It provides an indoor positioning engine that can fuse sensor signals to generate location fixes for turn-by-turn indoor navigation flows.

Map ingestion, venue metadata handling, and developer tooling support building an indoor spatial graph for consistent routing across multi-floor spaces. IndoorAtlas also supports app-side UX patterns such as proximity-triggered guidance that pair position updates with point-of-interest content.

Pros
  • +Indoor positioning engine designed for BLE and sensor fusion
  • +SDK support for embedding wayfinding into mobile apps and kiosk apps
  • +Multi-floor routing that accounts for venue structure in navigation flows
  • +Indoor geofencing patterns for proximity-based guidance triggers
Cons
  • Venue map authoring and calibration work can require project-specific effort
  • Navigation quality depends on the completeness of POI and path data
  • Complex routing setups may need deeper developer integration work
  • Integration scope can be limited without additional platform components

Best for: Fits when indoor apps need location fixes and navigation guidance across multi-floor venues.

#8

Navigine

enterprise

Indoor positioning and navigation platform for retail, logistics, and transit environments.

7.3/10
Overall
Features7.6/10
Ease of Use7.2/10
Value7.0/10
Standout feature

A navigation workflow that links CAD floor plan ingestion to routing paths and location-aware guidance across floors.

Navigine focuses on indoor wayfinding by combining venue map ingestion with an indoor positioning engine for turn-by-turn guidance. The product supports multi-floor routing by building navigation paths from CAD floor plans and point-of-interest data tied to those maps.

Navigine also supports digital signage-style kiosk flows through configurable wayfinding experiences and location-aware triggers. Integration depth is centered on an automation-friendly API surface and operational tooling for managing map assets and serving navigation to mobile and kiosk clients.

Pros
  • +Multi-floor routing built from CAD floor plan ingestion
  • +Configurable wayfinding experiences for both mobile and kiosk-style use
  • +Indoor positioning integration for blue dot tracking and guidance
  • +Operational tooling for managing venue assets and navigation behavior
Cons
  • Map preparation workload can be high when CAD layers are inconsistent
  • Integrations can require deeper engineering for custom analytics or workflows
  • Positioning accuracy can depend on venue RF characteristics and calibration effort
  • Advanced behaviors need careful configuration to avoid routing dead-ends

Best for: Fits when venues need turn-by-turn indoor routing across multiple floors with configurable kiosk and mobile experiences.

#9

Visioglobe

enterprise

3D indoor mapping and wayfinding SDK for mobile and kiosk applications.

7.0/10
Overall
Features7.1/10
Ease of Use7.0/10
Value6.8/10
Standout feature

POI-centric venue map authoring that drives turn-by-turn guidance across floors and embeds into kiosk-style experiences.

Visioglobe provides indoor navigation by combining indoor map authoring with a point-of-interest layer that supports visitor guidance.

Guidance can be delivered through kiosk deployments and a mobile wayfinding app, with indoor positioning used to update instructions.

Operations center on managing venue content like floors, locations, and guidance assets to reflect layout changes.

Integration emphasis is on embedding and connecting maps into existing visitor touchpoints rather than building a broad developer platform.

Pros
  • +Venue authoring supports multi-floor indoor maps and POI-driven navigation
  • +Kiosk and mobile guidance target different visitor touchpoints
  • +Routing-aware guidance can adapt to venue layout changes
  • +Embedding-oriented distribution supports existing screen and app ecosystems
Cons
  • Automation and API surface details are less explicit than top-ranked SDK options
  • Advanced analytics and heatmap workflows feel less developed than navigation-first competitors
  • High-volume updates require disciplined map publishing and content governance
  • Deep accessibility routing capabilities need validation per venue requirements

Best for: Fits when venues need kiosk and mobile wayfinding with POI-based guidance tied to indoor map authoring.

#10

Steerpath

API-first

Indoor positioning and wayfinding SDK with map management for mobile and web integration.

6.7/10
Overall
Features6.3/10
Ease of Use7.0/10
Value6.9/10
Standout feature

Venue route publishing and accessibility-aware guidance configured for multi-floor indoor navigation.

Steerpath is an indoor wayfinding system for getting people from entry points to destinations across multi-floor venues using configured indoor maps and guidance flows. Core capabilities center on turn-by-turn navigation on kiosks and mobile, plus point-of-interest selection and accessible routing configuration for common accessibility constraints.

Admin workflows focus on map authoring, location and route publishing, and venue-level configuration so updates can be applied without rebuilding apps. Steerpath also supports ongoing operations through analytics views that track how visitors use wayfinding and where drop-off happens.

Pros
  • +Multi-floor route guidance built around configured venue destinations
  • +Configurable navigation experiences for kiosk and mobile deployments
  • +Accessibility-aware route configuration for mobility constraints
  • +Operational analytics that show where guidance fails to convert
Cons
  • Customization depth depends on how its map and routing are modeled
  • Automation and API surface for third-party systems is limited versus more developer-first options
  • Indoor positioning quality depends on venue sensing setup and calibration
  • Complex authoring workflows can require repeated map and POI validation

Best for: Fits when venue operators need kiosk and mobile wayfinding with accessible route options and ongoing analytics.

Conclusion

After evaluating 10 transportation logistics, Mappedin 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
Mappedin

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 wayfinding software

Indoor wayfinding software turns authored indoor maps into turn-by-turn navigation for kiosks and mobile apps, with POI search, multi-floor routing, and venue-specific guidance flows. This guide covers Mappedin, MazeMap, Living Map, Pointr, Concept3D, Situm, IndoorAtlas, Navigine, Visioglobe, and Steerpath based on how each tool handles indoor connectivity, CAD floor plan ingestion, and routing behavior.

Key differentiators show up in how routing is generated. Mappedin generates turn-by-turn directions from authored indoor connectivity across floors, while MazeMap links floor plans to navigable waypoints for multi-floor routing. Living Map builds routing from CAD floor plan geometry into an indoor spatial graph.

Indoor wayfinding software for multi-floor navigation, kiosk and mobile deployments

Indoor wayfinding software provides a venue map authoring workflow and a navigation runtime that guides people to destinations using indoor connectivity, floor transitions, and POI-driven flows. Tools like Mappedin and MazeMap focus on producing navigable routes from venue authoring artifacts, then serving turn-by-turn guidance for kiosk and mobile entry points.

In practice, these platforms connect indoor map creation to routing execution through an indoor spatial model. Living Map emphasizes CAD floor plan ingestion that feeds an indoor spatial graph for multi-floor routing, while Pointr centers on venue content provisioning that ties POIs, floors, and navigation flows into one configurable setup for reuse across kiosk and mobile deployments.

Indoor routing, authoring workflow, and developer integration controls

Indoor wayfinding succeeds when the runtime can generate turn-by-turn guidance from an authored indoor model rather than relying on static floor overlays. Mappedin generates turn-by-turn directions from authored indoor connectivity across floors, which supports consistent multi-floor routing logic.

Authoring depth also determines operations cost after launch. MazeMap links floor plans to navigable waypoints for multi-floor turn-by-turn routing, which makes map governance and waypoint accuracy central to ongoing performance.

  • Cross-floor routing from an authored connectivity model

    Mappedin generates turn-by-turn directions from authored indoor connectivity across floors, not static overlays. Living Map builds routing from ingested floor plan geometry into an indoor spatial graph that connects multi-floor paths and floor-to-floor transitions.

  • CAD-to-waypoint or CAD-to-graph conversion workflow

    MazeMap provides venue-specific map authoring that links provided floor plans to navigable waypoints for turn-by-turn routing. Concept3D focuses on geometry-to-routing generation for multi-floor venues to reduce manual linking between floors and POIs.

  • POI-driven content and destination flows

    Pointr ties POIs, floors, and navigation flows into one configurable wayfinding setup for content reuse across kiosk and mobile deployments. Visioglobe emphasizes POI-centric venue map authoring that drives turn-by-turn guidance across floors and targets kiosk and mobile touchpoints.

  • Indoor positioning backbone for embedded navigation experiences

    Situm is built around an indoor positioning engine so the same location backbone supports custom apps and kiosk-style entry flows. IndoorAtlas supplies an SDK designed for BLE sensor-fusion indoor positioning to improve location fixes for indoor routing.

  • Operational governance for map quality and routing tuning

    MazeMap routing quality depends on how accurately areas and waypoints are authored, which makes ongoing POI and waypoint maintenance part of day-to-day operations. Mappedin navigation accuracy depends on floor plan cleanup and path modeling work, which means venue teams must control input geometry quality.

  • Multi-deployment experience configuration for kiosk and mobile

    Navigine provides configurable wayfinding experiences for both mobile and kiosk-style deployments built from CAD floor plan ingestion. Steerpath configures navigation experiences for kiosk and mobile deployments around configured multi-floor destinations and accessibility-aware guidance.

Select based on routing generation philosophy, then match integration depth

Routing generation method should come first because it dictates what must be authored and what can be automated later. Mappedin derives turn-by-turn directions from indoor connectivity across floors, while Living Map builds an indoor spatial graph from CAD geometry to drive multi-floor guidance.

Integration depth and operational control come next because kiosk and mobile rollouts typically require consistent configuration and governance across venues. Situm and IndoorAtlas center on an indoor positioning engine with SDK embedding, while Mappedin, MazeMap, and Living Map center on venue authoring and routing runtime fed by authored map models.

  • Pick the routing backbone: connectivity graph vs spatial graph vs CAD waypoint routing

    Choose Mappedin when the indoor connectivity model across floors is the source for turn-by-turn directions. Choose Living Map when routing should be driven from CAD floor plan geometry into an indoor spatial graph, and choose MazeMap when floor plans must be linked to navigable waypoints for multi-floor turn-by-turn routing.

  • Decide who authors destinations: POI content team or mapping ops team

    Choose Pointr when POIs, floors, and navigation flows must be configured together for reusable destination routing across kiosk and mobile. Choose Concept3D or Navigine when CAD-driven map authoring workflows are the primary source of routing paths and floor-to-floor connectivity.

  • Match positioning ownership: SDK positioning vs routing-only authoring

    Choose Situm when venue apps and kiosk flows need an indoor positioning backbone exposed through SDK-based indoor positioning with turn-by-turn routing in custom apps. Choose IndoorAtlas when BLE and sensor-fusion positioning via the IndoorAtlas SDK is a requirement for location fixes that feed indoor routing.

  • Validate the authoring-to-accuracy pipeline for the floor plans on hand

    If CAD layers and geometry cleanliness are inconsistent, prioritize workflows that explicitly depend on floor plan cleanup and path modeling quality such as Mappedin. If waypoint and area authorship accuracy is the limiting factor, validate MazeMap with representative floors where areas and waypoints can be curated and maintained.

  • Design for deployment modes: kiosk-first UI requirements vs mobile-first embedding

    Choose Navigine when configurable experiences are needed for both kiosk-style and mobile guidance tied to CAD ingestion and routed paths. Choose Situm or IndoorAtlas when the navigation runtime must be embedded into custom apps and kiosk-style entry flows while relying on a shared location backbone.

Who benefits from these indoor wayfinding approaches

Venue operators usually need predictable multi-floor turn-by-turn routing and a repeatable map authoring pipeline across changing spaces. Developers usually need positioning and navigation behavior that can be embedded into mobile and kiosk deployments with consistent location fixes and routing outputs.

The tools differ most in whether routing is generated from indoor connectivity across floors, from CAD geometry into an indoor spatial graph, or from CAD-to-waypoint authoring tied to navigable path nodes.

  • Large multi-floor venues with standardized CAD workflows

    Mappedin generates turn-by-turn directions from authored indoor connectivity across floors, which fits chains that can enforce floor plan cleanup and path modeling standards.

  • Venues with curated wayfinding teams maintaining curated waypoints

    MazeMap relies on how accurately areas and waypoints are authored, which aligns with teams that can run ongoing POI and waypoint governance.

  • Engineering teams building custom mobile apps and kiosk entry experiences

    Situm and IndoorAtlas provide SDK-based indoor positioning so the same location backbone can support turn-by-turn routing in custom applications and kiosk-style flows.

  • Operators who want destination content reuse across kiosk and mobile

    Pointr provisions POIs, floors, and navigation flows together so the same destination routing content can be reused across different visitor touchpoints.

  • Venues ingesting inconsistent CAD layers across properties

    Navigine can generate multi-floor routing from CAD floor plan ingestion, but map preparation workload can be high when CAD layers are inconsistent.

Common indoor wayfinding implementation pitfalls

Indoor navigation failures often come from treating map publishing as a one-time task instead of a quality pipeline. Routing accuracy in these tools depends on how floor plans are cleaned, how paths are modeled, and how destinations and waypoints are authored.

Another frequent failure is choosing a tool that centers on routing authoring when the project actually requires an SDK positioning backbone shared across custom apps and kiosk entry flows.

  • Publishing floor plans without investing in floor cleanup and path modeling quality

    Mappedin navigation accuracy depends on floor plan cleanup and path modeling work, so test with representative floors before scaling authoring. If geometry cleanliness is weak, expect repeated rework in the indoor connectivity inputs.

  • Assuming waypoint-based routing will stay accurate without ongoing POI and waypoint governance

    MazeMap routing quality depends on how accurately areas and waypoints are authored, so plan for ongoing curation. If destination footprints change, update areas and waypoints in step with venue maintenance.

  • Treating SDK positioning as optional when the kiosk and mobile experiences must share a location backbone

    Situm is built around an indoor positioning engine tuned for venue deployment, so custom apps and kiosk flows share positioning behavior. IndoorAtlas similarly relies on BLE sensor fusion via the IndoorAtlas SDK, so omit it only when location fixes and positioning requirements are already satisfied.

  • Overestimating automation depth when relying on geometry ingestion from CAD assets

    Living Map provides CAD floor plan ingestion into an indoor spatial graph for multi-floor routing, but advanced navigation tuning can require governance discipline across teams. Concept3D automation also depends on input map quality and geometry cleanup effort.

How We Selected and Ranked These Tools

We evaluated Mappedin, MazeMap, Living Map, Pointr, Concept3D, Situm, IndoorAtlas, Navigine, Visioglobe, and Steerpath using feature coverage, ease of getting to turn-by-turn multi-floor results, and long-run value tied to map authoring work. Features accounted for 40% because turn-by-turn generation from indoor connectivity or waypoint authoring determines routing behavior across floors.

Ease and value each accounted for 30% because floor plan cleanup, path modeling workload, and governance effort drive the real time-to-first venue experience. Mappedin set the ranking pace because it generates turn-by-turn directions from authored indoor connectivity across floors and pairs CAD-based venue authoring with multi-floor turn-by-turn routing that maps cleanly to kiosk and mobile deployments.

Frequently Asked Questions About indoor wayfinding software

How do Mappedin and MazeMap generate turn-by-turn routes across multiple floors?
Mappedin generates turn-by-turn indoor directions from an authored indoor connectivity graph linked to venue data, so routing stays consistent as spaces change. MazeMap builds routing from authoring flows that link floor plan inputs to navigable waypoints across curated entrances, corridors, and rooms.
Which platform is better when a CAD-to-routing workflow must be driven by API-controlled publishing?
Living Map fits when CAD floor plan ingestion must feed routing and map publishing through an API surface for map content and navigation configuration. Navigine also connects CAD floor plans to routing paths, but it emphasizes automation-friendly map asset serving for mobile and kiosk clients rather than API publishing control.
How do Situm and IndoorAtlas differ in positioning architecture for indoor navigation?
Situm centers on an indoor positioning engine exposed through SDK support so mobile wayfinding apps and kiosks compute location fixes and then route users. IndoorAtlas focuses on sensor-fusion location fixes through its SDK, then pairs location updates with proximity-triggered guidance patterns tied to POI content.
What breaks if venue data and navigation destinations drift from the authored map graph?
In Mappedin, routing and search rely on the indoor map graph linked to venue data, so mismatched POIs or floor metadata can send users to wrong destinations. In Pointr, navigation destinations and real-time positioning inputs are tied to a single operational setup, so stale venue content can cause incorrect guidance even when route computation still runs.
Which tool supports admin controls that reduce changes to mobile or kiosk apps during venue updates?
Pointr targets configuration-driven provisioning, so venue teams can manage venue content and navigation behavior without custom route computation per location. Steerpath also supports venue-level configuration so map and route updates apply without rebuilding apps, but it adds analytics views for operational behavior tracking.
How do integrations work when maps need to be embedded into kiosks, signage, or existing visitor apps?
Living Map provides an API surface for embedding map content and controlling navigation configuration, which supports app-side rendering and kiosk integration. Mappedin supports embedding and export so teams can integrate maps into existing apps and digital signage surfaces while keeping the authored map graph consistent.
When accessible route routing is required, how do Steerpath and Concept3D handle constraints differently?
Steerpath configures accessible route options so guidance accounts for common accessibility constraints during multi-floor navigation. Concept3D focuses on geometry-to-routing generation from CAD-driven authoring, so accessibility behavior depends on how navigation inputs and POI placement are configured for routing outputs.
How does MazeMap compare with Visioglobe for POI-first authoring and changing layouts?
MazeMap emphasizes curated venue navigation flows that link floor plans to waypoints for consistent turn-by-turn routing as routes are maintained. Visioglobe emphasizes POI-centric venue map authoring and uses positioning to drive guidance updates, which helps when multi-entrance layouts and guidance content shift across floors.
What setup work is required to connect a venue map authoring workflow to an SDK-based mobile wayfinding experience?
Situm’s workflow uses its indoor positioning engine plus SDK so mobile apps and kiosk flows compute location and route users through multi-floor spaces after venue map configuration. Concept3D generates 3D-ready venue navigation content from CAD inputs and then depends on how the authored maps connect to the chosen mobile wayfinding app or embedded SDK flow.

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.