Skip to main content

Memory

Heritage

Digitization · Digital archives · Sustainable systems

  • OAIS
  • IIIF
  • Dublin Core

What makes it hard

You build for decades, not release cycles. The archive has to outlive the technology it was built on — including ours.

Digital innovation for cultural heritage

Heritage venues communicate through print: labels, panels, leaflets, wayfinding — reprinted for every language, and reprinted again for every new exhibition. The result is expensive, slow to change, rarely multilingual enough, and structurally unable to respond to the visitor standing in front of it.

We work with museums, heritage sites and visitor centres to change that, without asking curators to give up editorial control.

What we bring

  1. Open display ecosystems

    Displays that host several applications at once instead of cycling a playlist: multilingual storytelling alongside exhibition information, wayfinding, accessibility features and event communication, updated centrally. This capability comes straight out of our own research.

  2. Grounded AI access

    Retrieval-augmented generation over the venue's own catalogues and interpretive material, so a visitor can ask a question in their own language and get an answer built from the institution's own words. The model retrieves; it does not invent. Curators define the sources and the boundaries.

  3. Multilingual by pipeline, not by project

    Language adaptation built into the content flow rather than commissioned per exhibition. A new language should be an afternoon, not a budget cycle.

  4. Metadata and graph-ready architecture

    Collection data structured so it can be queried, linked and reused: interoperable APIs, open standards, content models designed for aggregation into wider European heritage infrastructure rather than locked inside one vendor's CMS.

  5. Progressive web applications

    Visitor experiences that run on the phone already in the visitor's pocket. No app store, no install, and nobody excluded because their device is three years old.

  6. Curator-in-the-loop workflows

    Editorial control by design. Heritage professionals keep full authority over interpretation and storytelling. Technology automates scheduling, translation, accessibility adjustment and analytics. It does not automate interpretation.

Curated collectionsprovenance retainedGraph-ready metadataOpen APIsWeb & PWASmart displaysGrounded AI assistant

Standards and interoperability

Heritage systems outlive the technology they were built on — including ours. We design against OAIS for preservation-aware workflows, IIIF for image interoperability, and Dublin Core and related schemas for metadata, so that what a project produces can be handed to the next system rather than migrated out of ours under duress.

  • OAIS
  • IIIF
  • Dublin Core

Sovereignty

All intellectual property — source code, application catalogue, brand and strategic decision-making — is owned by an EU-established company. Services run on EU cloud regions; AI capabilities use EU-region services. Aligned with the GDPR and the EU Data Act.

Why us

A heritage organisation does not need another signage vendor. It needs a partner who already understands that a display in a public room is a communications medium with its own rules — who has studied it, published on it, and now runs it in production.

That is what a decade of European research on open display networks was for. We are one of very few EU SMEs holding it in operational, commercial form rather than as historical output. We work on this from Iași, a city dense with archives, churches and museums, where the heritage work started at home.

How we work

Handover
We hand over systems your own team can run — documentation, observability and operational ownership are part of the delivery, not a phase we quote separately. If you need us in year three, it should be because you want us there.
Candour
We say what a system cannot do before we say what it can. An estimate that survives contact with procurement is worth more than one that wins the meeting.
Horizon
We design for the state of the system in year five, not the demo in week six. That is the difference between architecture and assembly.
Proof
Claims are demonstrable or they are not made. Where something is in preparation, we say so — including on this site.
Provenance
Everything we recommend has a source we can name — a project, a paper, or a system we ran ourselves.