A visit route in a museum
Every work becomes an information point: visitors use the kiosk or their phone and receive in-depth content in several languages and a map of the room.
Proximity also means speaking to the right people when they need it: a museum that guides the visitor, a kiosk that answers, a screen that knows what to say. Without profiling anyone.
Proximity also means speaking to the right people when they need it: a museum that guides the visitor, a kiosk that answers, a screen that knows what to say.
Collections, visit routes and events in a single management system: every artwork becomes an information point.
A kiosk welcomes, guides and answers the questions of whoever approaches.
Screens show the right message based on context and on how many people pass by, without profiling anyone.
Treasure hunts and checkpoint routes turn the visit into a guided game.
Museums, fairs and venues open to the public welcome many visitors every day, but often do not know what they liked, where they stopped or when they need help. A kiosk that answers and a screen that changes its message turn passing through into a dialogue.
The challenge is to do it without profiling anyone: context, meaning where you are, how many people are there and what time it is, is enough to choose the right content, and data stays aggregated and anonymous.
From the touchpoint to aggregated data, in five layers.
The functions for interacting with people are reusable Nebula microservices: each activates on its own and integrates with the ones you already use.
Every work becomes an information point: visitors use the kiosk or their phone and receive in-depth content in several languages and a map of the room.
A kiosk at the entrance guides visitors, answers frequent questions and alerts staff when a person is needed.
A stage-based route with checkpoints turns the visit into a game: each stage unlocks on the spot and a summary appears at the end.
Collections arrive from existing archives and systems through import; screens update over the network; ticketing and bookings connect through APIs. Interfaces are native or web and use the same data model.
We define objectives, audience and touchpoints with you, and choose the first service to activate.
We activate a service in a room, a stand or an event and measure what works.
We add services and venues reusing the same data and interfaces, without redoing the architecture.
Updates, monitoring and staff training are planned from the start.
No. The services work from kiosks and screens, or from a web page opened with a QR code, with no installation or registration.
Yes, when it exposes an API or allows data export. We import collections, calendars and events and keep them aligned with the rest of the platform.
With aggregated indicators: visits per room, dwell times, most frequent questions and route completion. No data identifies a person.
Indoor and outdoor localization, augmented reality search and contextual digital signage.
Open the pageMulti-tenant GIS for public bodies: maps, open data and aggregated flows of people.
Open the pagePredictive maintenance and statistical process control on machines and lines.
Open the pageIoT and Edge AI: models on the device and nodes that coordinate.
Open the pageCustom software and cloud platforms, one sheet at a time.
Open the pageTell us about the place and the audience: we'll choose together the first service to activate.
Let's talk