The problems it was built to fix.
Many events, one login
The Fourth of July, the fall festival and the tree lighting each get their own map and brand, managed from one place.
Road closures people actually see
Closures and reroutes are on the map attendees already have open, not on a channel nobody checks.
Accessibility you can point to
ADA parking, accessible entrances and viewing areas and quiet zones are first-class map content.
Emergency communication
A weather hold or a shelter-in-place reaches every open guide in seconds, scoped to the area that needs it.
Tourism attribution
Which campaign brought visitors, from the hotel key card to the billboard, with QR and UTM tracking built in.
Reports for council and sponsors
Engagement by zone, content demand and sponsor recaps, with the data kept by the city year over year.
No app for them to install.
City events draw people who will never download a municipal app. A QR code on the banner, the parking sign and the bus shelter opens the guide in their browser, in the event's brand.
- Works from any QR code or link
- Branded per event, not as the city's software
- Installable for people who want it
Closures, holds and shelters, where people are looking.
Publish a road closure and the map reroutes. Publish a weather hold and every open guide shows it. Keep the audit log for the after-action report.
- Zone-scoped emergency banners
- Closures reflected in routing
- Audit trail for the debrief
Questions we hear from cities.
Who owns the data?
The city. It is isolated per organization and stays available after the event. Nothing is sold or shared.
Is attendee tracking involved?
No passive location tracking. The guide records what people tap and search, with consent-aware collection and aggregation by default.
Can multiple departments share it?
Yes. Roles separate map managers, content editors and analysts, and one login can cover several organizations.
What about events the city co-hosts?
Each event has its own brand and its own public URL, whichever organization runs it.