Vendor Landscape
Comparison
Understanding the Archival Ecosystem: A Standards-Based Approach
| Feature / Model | Managed Open Source (USA Archives Hosting) |
Proprietary Platform (SaaS Vendors) |
Consortium / Association (Large Non-Profits) |
|---|---|---|---|
| Core Technology | Open Source (Community Owned) ArchivesSpace, AtoM, Koha |
Closed Source (Vendor Owned) Proprietary Codebase |
Open Source (Managed) ArchivesSpace, etc. |
| Data Portability | 100% Full SQL Access You own the database dump. |
Restricted / API Only Structure locked to vendor. |
Limited Often shared/multi-tenant DBs. |
| Standards Support | Native Integration IIIF, OAI-PMH, EAD3 |
Proprietary Interpretation May diverge from specs. |
Strict / Rigid Updates can be slow. |
| Customization | Flexible Plugins, Themes, Custom Fields. |
None / Low "One size fits all" |
None Strictly standardized. |
| Cost Model | Flat Fee (All Inclusive) Storage + Support + License. |
Volume Based Costs scale aggressively with TBs. |
Membership Tier Based on institution revenue. |
| IIIF Capability | Enterprise Server Cantaloupe with Deep Zoom. |
Basic / Outsource Often relies on 3rd parties. |
Varies Often an "Add-on". |
Choosing the Right Model
Managed Open Source (Us): Best for institutions that want the power and standards-compliance of open source (AtoM, ArchivesSpace) but lack the internal IT team to manage servers. You get the software you know, optimized for performance, with full control over your data.
Proprietary Platforms: Often provide a slicker "out of the box" initial experience but suffer from "Vendor Lock-in." If you leave, exporting your data in a usable format can be difficult, and you cannot host the software yourself.
Consortiums: Excellent for community networking, but often technologically rigid. You are on a shared timeline for updates and can rarely implement custom plugins or branding that deviates from the group norm.