Why Madrona
A platform built specifically for cultural heritage - not adapted from generic software or constrained by decades-old architecture.
How Madrona compares
| Feature | Legacy CMS | Madrona |
|---|---|---|
| Deployment | On-premises servers you maintain | Your call - self-host free, or we host it |
| Source code | Closed, vendor-controlled | Apache-2.0, public repository, fork it if you want |
| Updates | Annual upgrade projects, downtime required | Continuous updates designed to avoid scheduled downtime |
| Getty Vocabularies | Manual import, periodic refresh | Native integration, real-time suggestions |
| IIIF Support | Add-on or third-party tool | Built-in image serving and manifests |
| Audit Trails | Limited or module-specific | Complete field-level history for everything |
| Integrations | Custom development or expensive add-ons | Data integration included during implementation |
| User Interface | Desktop-era design | Responsive web application |
| Mobile Access | Limited or none | Full functionality on any device |
| Pricing Model | Per-seat + maintenance + modules | Software is free; pay only for hosting and services |
| Exit path | Data extraction project, vendor cooperation required | Take the source and your data and run it yourself |
The cost of staying put
Legacy systems aren't just outdated - they carry hidden costs that add up every year.
Less time on administration
Replace manual data reconciliation across multiple systems with one shared data layer.
Faster cataloging
Getty vocabulary autocomplete and bulk operations are designed to accelerate cataloging workflows.
Infrastructure on your terms
Run it yourself with docker compose, or let us host it and skip the server maintenance, backups, and upgrade cycles entirely.
Full data portability
Export capabilities in standard formats mean you're never locked in. Your data remains yours.
No software to buy
The platform is Apache-2.0. Licensing is not a line item, and a budget freeze can never switch it off.
Legacy system costs you might not see
Madrona
No license fee at all - the software is Apache-2.0
Madrona
Self-host on your own hardware, or pay us to run it
Madrona
Managed updates on hosting; docker compose pull if you self-host
Madrona
Data integration handled during implementation
Madrona
Intuitive web UI, minimal training needed
Madrona
Automation built in
What makes Madrona different
Built for cultural heritage, not adapted
Madrona was designed from day one for cultural heritage workflows. We didn't retrofit enterprise software or bolt on cultural heritage features - we started with what institutions actually need.
Open source, all of it
Madrona is Apache-2.0 — every application, the API, and the deployment tooling. Not a limited community edition next to a paid one: the public repository is the same code we run for hosted customers. Install it yourself and pay us nothing, or hire us to run it.
Modern architecture
No legacy code from the 1990s. Madrona is built on current technology that enables real-time collaboration, mobile access, and data integration across systems.
Standards-native
Getty vocabularies, IIIF, and linked data are built into the foundation - not checkboxes, not add-ons. JSON-LD export is suitable for CIDOC-CRM mapping.
Transparent pricing
The software costs nothing. Hosting includes the full platform, unlimited users, and data integration during implementation. No per-seat fees, no module upsells, no maintenance surcharges.
Lock-in is structurally impossible
Most vendors promise no lock-in and mean data export. We mean the software as well: it is Apache-2.0, so the worst case if you fire us is that you run the same platform yourself.
Continuous improvement
Regular updates with new features, performance improvements, and security patches. Applied for you on hosting, and available to every self-hosted install the moment they land. No annual upgrade projects.
Ready to see the difference?
Schedule a demo to see how Madrona compares to your current system.
Request a demo