Digital wayfinding software in four parts, built on one map
DigiMaps is a digital wayfinding system in four parts. Your team builds and publishes the venue in Studio. Wayfinder shows it on kiosks, phones, signage and your website. The live layer pushes closures and emergencies to every screen within seconds, and the API connects your own systems.
1Studio
Your team draws, names and publishes the venue.
- Editor
- Directory
- Live
- Releases
- Kiosk fleet
- Statistics
2Wayfinder
What visitors see and touch.
- Kiosk
- Phone, by QR
- Signage page
- Directory board
- Website embed
3Live layer
Today’s changes, without a new release.
- Closures
- Moved services
- Notices
- Emergency
- Events
- Signage playlists
4API
How your own systems connect.
- REST · 340+ operations
- Webhooks · 13 events
- Live channel · SSE
- RSS · JSON Feed · iCal
- SSO · SAML 2.0, OIDC
What each part does, and who uses it.
Facilities teams work in Studio. Visitors only ever see Wayfinder. IT looks after the API and the server it runs on. Each part links to the page that covers it in detail.
-
Studio: the venue CMS
Map editors draw or import floors. Content editors keep names, opening hours and languages right. Every map change waits in draft until someone publishes it, and one Studio runs a whole portfolio of venues.
-
Wayfinder: what visitors use
A 3D map with search, place cards and step-by-step directions. The same app runs on a touchscreen kiosk, in a phone’s browser after a QR scan, on signage players and inside your website. The QR code carries the destination, language and step-free choice from the kiosk to the phone.
3D maps on phones and websites Kiosk software and fleet control Maps on your signage players Step-free routes and reach mode
-
Live layer: today’s changes
A closed restroom, a clinic moved for the week, a notice for one wing. Operators post it in Studio and it reaches the chosen screens within seconds, without a new map release. Emergency mode takes over every screen in every venue language, and supplements, never replaces, your approved signage and procedures.
-
API: how your systems connect
A REST API, signed webhooks, a live event channel and feeds for signage players. If you already run beacons or a positioning SDK, DigiMaps accepts its position feed through a documented API.
The kiosk and the directory board beside it read the same release.
When you publish, kiosks, phones, signage pages, your website and the API all load the same frozen release. There is no second copy of the directory for someone to forget to update.
Studio
Edit, review, publish.
Wayvale General Hospital
Release v15 · published
- Preflight passed
- Visitors see only published releases
- Touchscreen kiosk Fixed “You are here”, step-by-step routes, QR to phone.
- Visitor’s phone Opens in the browser from a QR or link. No app.
- Signage display and directory board Any player that opens a URL, plus RSS, JSON Feed and iCal feeds.
- Your website Embed with an iframe and a JavaScript API.
- API and webhooks REST API, live Server-Sent Events channel, signed webhooks.
Closures, notices and emergencies reach screens within seconds, no republish.
Studio → every screen, skipping the release step
Signage pages need a Chromium 111 or newer browser engine on the player. Test each player model on site before go-live.
Two ways a change reaches the screens.
Some changes alter the map and deserve a second pair of eyes. Others cannot wait: if a lift breaks at 09:40, the kiosks need to know at 09:40. DigiMaps keeps the two apart.
Release line
Changes to the map itself: a new shop unit, a moved wall, a renamed department, new opening hours.
- Studio Edit in draft. Visitors see nothing yet.
- Review A colleague approves, or rejects with a comment.
- Preflight Critical map errors block the publish.
- Publish Now, or scheduled for tonight.
- Every screen Kiosks switch over when idle.
Live line
Things that change today: restrooms closed for cleaning, a lift out of service, a clinic moved for the week, an evacuation.
- Studio Post it in Live, pick screens or zones, set an end time.
- Live channel Server-Sent Events carry it out.
- Every screen Within seconds. Routes avoid the closed place.
Both lines end at the same screens. A visitor already following a route is re-routed when a closure lands, and told why.
For tender documents
Platform data sheet
If you are writing a specification for a “digital way finding system”, start from these rows. Each one describes the product as it is today. Our wayfinding tender specification template turns them into requirements you can copy.
Studio
- Venues
- Many venues per workspace, many buildings per venue, up to 50 floors per building
- Editor
- 21 drawing and routing tools. Draw in 2D, check in 3D
- Coordinates
- Local metres from CAD, or WGS84 for georeferenced campuses
- Industry packs
- 14, including hospital, mall, airport, campus, office and government
- Roles
- Six, with per-venue overrides. SSO via SAML 2.0 and OpenID Connect
- Releases
- Review and approval, scheduled publish, version diff, rollback
- Export
- IMDF, GeoJSON and KML
Wayfinder
- Surfaces
- Touchscreen kiosk, phone and desktop browser, signage page, directory board, website embed
- Phones
- QR hand-off from a kiosk, no app. Keeps working offline after the first visit
- Routing
- Six profiles. Step-free is a hard rule, never a preference
- Languages
- Venue content in up to 24 of 54 catalogue languages. Arabic right to left
- Kiosk hardware
- Android 9 boards with 2 GB, Windows kiosk PCs, ChromeOS. Chromium or WebView 111+, WebGL 2
- Screen layouts
- Full HD and 4K, portrait and landscape
Live layer
- Kinds
- Closures, moved services, notices, emergencies, events, information pages, signage playlists
- Delivery
- Server-Sent Events with replay. Within seconds, no republish
- Targeting
- Every screen, or chosen zones and kiosks. Start, end and repeating windows
- Emergency
- Full-screen takeover in every venue language. Nearest-exit guidance where approved exit data exists
API and integrations
- REST API
- OpenAPI-documented, 340+ operations
- API keys
- Scoped, hashed, shown once. Rotation and expiry
- Webhooks
- HMAC-SHA256 signed, 13 event types, retries and a redrive log
- Feeds
- RSS 2.0 with Media RSS, JSON Feed 1.1, iCalendar
- Embeds
- iframe and JavaScript API. Web SDK on request
Where it runs
- Cloud
- Hosted by us, in a region agreed in your contract
- On-premises
- DigiMaps Server on one machine: Ubuntu 22.04 or 24.04, or Windows 11 22H2+ and Server 2025 through WSL2
- Air-gapped
- No internet needed: no outbound calls by default, offline updates
- AI features
- Optional. Off by default on-premises
Running DigiMaps on your own server Wayfinding solutions by industry
What DigiMaps does not do today.
Buyers ask about these early on, so here is the plain answer. Each row says what works instead. If one of them is a must-have for your venue, we would rather you knew now.
| Not available | Status | What works today |
|---|---|---|
| A live blue dot on iPhone | On the roadmap | Kiosk “You are here” and QR hand-off of the route to the visitor’s phone. iPhone positioning would need a native app. |
| A blue dot on Android phones | Pilot only | A commissioned pilot: we survey your venue and report the accuracy measured on site. |
| Native iOS and Android SDKs | On the roadmap | Embed the wayfinder with an iframe and a JavaScript API. The web SDK is available on request. |
| Augmented-reality directions | Not offered | Step-by-step directions with landmarks, a route preview and a heading-up “Your view”. |
| Precision positioning (UWB or visual positioning) | On the roadmap | Positions from your own beacons or positioning SDK can be fed in through a documented API. |
| Photoreal 3D capture of your building | On the roadmap | A 3D map built from your floor plans, in your colours, fonts and logo. |
| Crowd-aware routing out of the box | Needs your feed | Connect your occupancy or Wi-Fi-count feed, or post closures live from Studio. |
| Ready-made CRM, chat or point-of-sale connectors | Not offered | Signed webhooks and the REST API, wired to the tools you use. |
| Studio in languages other than English | Not yet | Visitor content in up to 24 languages per venue, including Arabic right to left. |
| Security certifications and independent audits | Not yet | Security questionnaire, threat model and penetration-test scope under NDA. |
| An uptime SLA | Not offered | Health monitoring, kiosk offline alerts and monthly kiosk uptime reports built in. |
| Self-service accounts and online checkout | Not offered | Book a demo. We quote per venue, in writing. |
What we can show you as evidence, and what we cannot yet: trust and evidence Where another vendor may fit better: wayfinding software comparisons
Questions about the platform
What is a digital wayfinding system?
A digital wayfinding system shows visitors an interactive map of a building and gives them directions on screens: touchscreen kiosks, their own phones, signage and websites. Staff keep it up to date from a content management system instead of reprinting signs. In DigiMaps, that system is Studio and the visitor side is Wayfinder.
Which parts of DigiMaps does a venue need?
Every deployment has Studio and Wayfinder: one is where your team maintains the map, the other is what visitors use. The live layer is part of Studio, so closures, notices and emergency mode come with it. The API matters when you want to connect your website, building systems or a signage CMS.
Does DigiMaps work with the kiosks and signage players we already have?
Usually, yes. Kiosks run on Android signage boards (Android 9 with 2 GB of memory is enough), Windows kiosk PCs and ChromeOS, with a Chromium or WebView 111+ browser and WebGL 2. Signage players that can open a web page or read an RSS feed can show the signage page or directory board. We have setup notes for Xibo, BrightSign, Yodeck and ScreenCloud, and we test each player model on site before go-live.
Can the whole platform run on our own server?
Yes. DigiMaps Server runs Studio, Wayfinder, the API and the database on one machine on your network, on Ubuntu or Windows. It runs with no internet connection: no outbound calls by default, and updates arrive as an offline bundle.
How does DigiMaps connect to our other systems?
Through a REST API with more than 340 documented operations, HMAC-signed webhooks for 13 event types such as a kiosk going offline or an emergency broadcast, and a live Server-Sent Events channel. Signage systems can read RSS, JSON Feed and iCal feeds. There are no ready-made connectors for specific CRM or chat tools.
What does DigiMaps not do yet?
There is no blue dot on iPhone, no native mobile SDK and no augmented-reality guidance today, and DigiMaps holds no security certifications yet. Kiosk wayfinding, QR hand-off to phones, Arabic, accessibility, live operations and on-premises hosting are where it is strongest.
See all four parts on a sample hospital
In a 30-minute call we post a closure in Studio, watch the kiosk re-route around it, and show the QR hand-off to a phone. Bring a floor plan and a list of your screens, and we will tell you plainly what a pilot on your site would involve.