Libraries · Schools · Venues

The AI layer for public culture and knowledge

We don't replace your systems. We make sure the public never has to care which ones you chose.

Live across public libraries · launching in France, Germany, Switzerland, Sweden, Finland and Norway

01 / The staff console

The conversation flow editor, with a live preview of the visitor surface

Flows

Staff design what the agent does

The routing and qualification logic behind a surface, edited as a node diagram by the people who own the service — not scripted by us.

Everything here is the institution's own staff console. No developer in the loop, no ticket to us.

02 / The gap

People's expectations changed. Institutions' interfaces didn't.

Everyone now searches the way Google and ChatGPT taught them — conversationally, in their own words, expecting an answer rather than a list. Then they walk into a library, a museum or a classroom and meet software designed for a different decade.

Institutions are being judged against a standard they did not choose and cannot meet with their current front ends. One municipality. Three doors: the library, the school, the museum. One supplier behind all of them.

03 / Three surfaces

Libraries

Search the way people already search

Conversational, multilingual, voice or text — running on the catalogue the library already has.

For libraries →

Schools

A study layer inside the tools students use

Built on the institution's own material rather than the open web, and visible to the teacher.

For schools →

Venues

Guides and routes the institution maintains

Media guides, routes and interpretation curators create and edit themselves, with no separate content system.

For venues →

The library AI chat on a phone: a book recommendation opened to show its cover, author, branch and availability, with a link to reserve it — A recommendation, with availability and a reservation link

A recommendation, with availability and a reservation link

The study layer on a phone: the next session, a reflection marked done, and the week at a glance — Studieguiden — the next session, the open deadline, the week

Studieguiden — the next session, the open deadline, the week

The museum media guide on a phone: the ironworks guide with explore, listen, quiz and map, and sixteen languages — Järnverket — explore, listen, quiz and map, in sixteen languages

Järnverket — explore, listen, quiz and map, in sixteen languages

04 / The architecture

Systems change. The experience shouldn't.

Digital Venue is a layer, not a replacement. It sits on top of the systems you already own and is built to survive those systems being swapped underneath it.

The public

A reader looking for a book, a student revising for an exam, a visitor standing in a gallery

They arrive with a question in their own words, in whichever language they think in.

Web · kiosk · phone

The layer

One deployment per institution, portable across whatever sits beneath it

It holds no authoritative copy of your catalogue — it reads what you already own. So the systems underneath can be replaced without the visitor noticing.

Digital Venue

Underneath

The library catalogue, the learning platform, the collections database, municipal web and identity

Stay where they are. Replace one and the surface above it does not change.

Your systems

The full architecture, the console and how a deployment goes live →