NG-Key
NG-Key
Maps & Indoor

Indoor editor, navigator, and guest wayfinding

Turn floor plans into operational routing truths – managed by your administrators and used wherever credentials touch doors.

NG-Key binds indoor topology to your tenant hierarchy: buildings, floors, connections, and destinations remain coherent as your campus evolves.

Operators design and develop routing graphs with validation-oriented workflows; published bundles serve as the sole reference for navigation experiences and downstream analytics.

Guest-facing navigation links inherit the same authorized structure — so reception teams stop sending screenshots, and guests don’t have to guess which stair corresponds to the policy.

Spotlight

What 'one indoor model' unlocks

  • Single routing bundle per tenant and location — no competing geometry silos between visitor apps and operator consoles.
  • Structured transitions between floors and wings — escalators, elevators, and corridors remain aligned with physical circulation.
  • Destination-Aware Guidance – POIs and Checkpoints Reflect How Teams Actually Describe Spaces During Incidents and Audits.
  • Scoped guest journeys — public navigation surfaces inherit restrictions without disclosing internal topology details.
  • Analytics-ready references — indoor events refer to stable identifiers instead of fragile free-text labels.
Abstract indoor routing graph on glass — NG-Key facility marketing item

Depth

Capabilities teams rely on

Authorization & Lifecycle

Draft, Review, and Publish Indoor Revisions with Clear Separation Between Operator Changes and Production Packages.

Navigator runtime

Serve coherent directions from the published graph — aligned to access paths, not generic map tiles.

Guest navigate

Issue tenant-specific experiences that remain calm under load – minimal friction for invited visitors only.

Operational Signals

Attach analytics semantics to floors and connections to improve indoor positioning over time — not just after incidents.

Spatial Governance

Keep circulation constraints explicit – emergency overlays and restricted corridors remain enforceable across all surfaces.

Check coupling

Trace issuance alongside access decisions – procurement and security checks see a coherent story.

Motion

How rollout teams operate it

01

Model

Import or refine geometry with connectors that reflect real traffic – no decorative polygons.

02

Validate

Walk critical journeys digitally — from reception to the boardroom, from the lobby to the lab — before they are published.

03

Publish

Promote bundles so navigator and guest surfaces consume identical routing truths.

04

Observe

Tune POIs and transitions using analytics and operator feedback – without branched maps.

Recognized outcomes from procurement

Fewer navigation escalations during peak visitor times.

Security posture improves when guest journeys inherit institutional constraints.

Operations retire duplicate indoor datasets maintained as 'map only.'

Audit narratives reference stable indoor identifiers instead of screenshots.

Product Preview

Chapter Walkthrough

Short Cinematic Clip for This Chapter About the Facility – Silent, Repeated in the Page, Players Follow Your Motion Settings Elsewhere on the Page.

Continue Exploring

Switch to Workspace Governance or Edge Operations – or Back to Platform Core.