Curator's Atlas
A SaaS tool for museum registrars and curators that consolidates object location data, loan schedules, and condition reports into one searchable map across their own collection and partner museums.
Small and mid-sized museum registrars juggling loans, exhibitions, and storage moves
- Single map view of every object with location, condition status, and current custodian
- Loan timeline planning that flags conflicts before scheduling
- Automated shipping and customs paperwork drafts
- Public-friendly view for marketing 'where to find this piece' pages
Ex Situ shows the underlying data model is buildable; most museums still run object location through spreadsheets and emails
Confirmed Ex Situ HN post (38 pts, 22 comments) shows real interest in this problem, but software review sites already host dedicated museum-software categories with many buyers, indicating a real but modest niche.Show HN: Ex Situ – Open-source spatial index of displaced cultural artifacts (Hacker News) ↗List of Top Museum Software – SoftwareWorld ↗
Market is crowded with incumbents (CollectiveAccess, Adlib, Axiell/TMS, VitrineCMS, Museum Archive) that already advertise cataloging, loan tracking and location tracking — the cross-institution map view is a narrower niche but still adjacent to existing scope.Best Museum Collections Software 2026 – worldmetrics.org ↗Museum Collection Management Software – VitrineCMS ↗
Real SaaS spend exists (SoftwareAdvice, Capterra, SourceForge all monetize listings) and VitrineCMS openly publishes 'free to institutional' tiers, but museum budgets are famously thin, capping per-seat pricing potential.Best Museum Software – 2026 Reviews & Pricing | SoftwareAdvice ↗Museum Collection Management Software – VitrineCMS ↗
Cultural-heritage sector is structurally stable and mission-driven; once adopted, registrar tools persist for decades — but the market is slow-growing and resistant to disruption.
Ex Situ's GitHub repo (github.com/hburakyel/ex-situ) demonstrates the spatial/cross-institution data model is buildable, but a production SaaS still requires integrations with many legacy CMS APIs, mapping UI, and auth — non-trivial but clearly doable.