Use cases

Any institution that holds a collection and has to answer for it.

The object model adapts to the medium, so the same platform serves a games museum, a university department and a private archive without pretending they are the same.

Museums

From volunteer-run local museums to institutions with several buildings, mixed media and a public programme.

What it solves
One catalogue instead of scattered lists
Location and condition history for audits
Front desk, rotas and maintenance in the same system

Universities

Teaching collections, departmental holdings and research material that move between staff, students and stores.

What it solves
Loans to seminars and labs, tracked
Roles for staff, students and researchers
Reporting for departmental review

Archives

Documents, ephemera and series with their own description rules and access conditions.

What it solves
Hierarchical description down to item level
Digitisation files stored against records
Access and permission control

Libraries

Special collections and non-book holdings the library catalogue was never designed to describe.

What it solves
Custom fields per medium
Condition and conservation notes
Search across the whole special collection

Private collections

Serious collectors who need to know what they hold, where it is, and what it is worth.

What it solves
Provenance and acquisition history
Valuation and insurance records
Export for loans and estate planning

Cultural foundations

Foundations managing holdings across sites, projects and funded programmes.

What it solves
Multi-site locations and movement
Programme and event management
Funder-ready reporting

Researchers

Scholars who need to query a collection properly instead of asking staff for exports.

What it solves
Structured search across fields
Stable object records to cite
Controlled access to sensitive data

Tell us what you hold - we'll show you the shape it takes in museumOS.

Request a demo