Archives & collections management
Archival description, accessions, digital collections and researcher access.
12 listings, including 11 from other publishers. Entries cover the deployment options documented on their individual pages.
Read this page as JSON or Markdown.
Watch this category with RSS · Build a requirements shortlist
Deployment comparison
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Arches | AWS | Customer-operated Servers / containers | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Source / language package | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe AWS deployment guide covers the application, while the S3 guide covers media storage. Mentions of storage on other providers do not establish corresponding application installs. Heritage-resource inventories are distinct from complete archival accession and records-disposition workflows.
Cloud evidence reviewed 2026-11-19 |
| Archivematica | AWS | Customer-operated Servers / containers | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe AWS implementation is maintained by Wellcome Collection. It is an institutional deployment pattern rather than an upstream support commitment. Preservation outputs, access interfaces and storage/recovery policies require separate configuration.
Cloud evidence reviewed 2026-11-19 |
| ArchivesSpace | AWS | Customer-operated Servers / containers | Open Source / Open Core Open source; optional membership/support services | Docker or ZIP distribution with production MySQL and required search/runtime services | Customer operates the application, production database, search services and backups.Scope and evidenceThe project documents Docker and ZIP installations. Its FAQ explicitly distinguishes archival description from managing digital files or digitization workflows. Provider-specific deployment support was not verified.
Cloud evidence reviewed 2026-11-12 |
| Avalon Media System | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceAvalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.
Cloud evidence reviewed 2026-11-19 |
| Browsertrix | DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Kubernetes manifests | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.
Cloud evidence reviewed 2026-11-19 |
| Dataverse Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache-2.0 application; dependencies and dataset reuse licenses are separate. | Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release. | Institution operates application and infrastructure, permissions, persistent identifiers, database/files, backups, monitoring and upgrades. External identity, citation and analysis services require configuration.Scope and evidenceReview used 6.12.1; Docker users need the corrected 6.12.1-noble-r3 image or newer described by upstream. The AWS developer script creates the full application but is not a production hardening shortcut. Configure HTTPS, restricted APIs, database/file recovery and appropriate sensitive-data controls before opening access. This is unrelated to Microsoft Dataverse.
Cloud evidence reviewed 2026-11-13 |
| DSpace Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core BSD-3-Clause core; dependencies and optional commercial hosting/support have separate terms. | Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate. | Institution manages the application releases, collection permissions, metadata, storage, backups and upgrades. AWS can operate container compute through Fargate; the institution still operates its repository services.Scope and evidenceReview used backend/frontend 10.1. Follow the current installation guide for runtime and database/search compatibility; protect Solr from public access and enable HTTPS. The Johns Hopkins AWS case study demonstrates an institutional deployment, not a turnkey installer or a blanket upstream cloud-support commitment. External identity, analytics and scholarly integrations are operator choices.
Cloud evidence reviewed 2026-11-13 |
| Fedora Repository | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform; Package / binary installer | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.
Cloud evidence reviewed 2026-11-19 |
| FormKiQ Archives and Collections ManagementDirectory Publisher | AWS | Customer-operated Serverless | Commercial Only Commercial FormKiQ Advanced or Enterprise; confirm required extensions | Configure the solution in a FormKiQ deployment; CloudFormation installs the platform. | Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.Scope and evidenceThis is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.
Cloud evidence reviewed 2026-11-12 |
| InvenioRDM | AWS | Customer-operated Servers / containers | Open Source / Open Core MIT application code; framework modules, institutional customizations and dependencies retain their own terms. | Official Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration. | Institution operates application and workers, identity, search, data services, configuration, backups and upgrades. Cloud resources are separate from the public Zenodo hosted service.Scope and evidenceThe upstream project identifies v14. Caltech documents its own EC2 deployment and earlier release-specific setup, not universal v14 compatibility. Follow current upstream production requirements and review the institution-specific files before reuse. Docker Compose reference defaults require production adaptation. External DOI, identity, mail and analytics services have separate data boundaries.
Cloud evidence reviewed 2026-11-13 |
| Islandora (ISLE) | DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.
Cloud evidence reviewed 2026-11-19 |
| Omeka S | AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock | Customer-operated Servers / containers | Open Source / Open Core GPLv3 application; the packaged OIDC module is GPL-3.0-or-later. | Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation. | Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.Scope and evidenceReviewed Cloudron 1.6.1 contains Omeka S 4.2.1 and OIDC module 1.2.0, whose declared compatibility covers Omeka S 4.x. The current package uses OIDC although its package manual still describes LDAP. Change initial administrator credentials, review identity/account linking and researcher defaults, and check extension compatibility before upgrades. Preserve the database, configuration, collection files, modules and themes. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.
Cloud evidence reviewed 2026-11-13 |
Choose 2–4 listings to compare
Browse listing cards
Archives & collections management
Arches
Open-source cultural-heritage inventory and resource-information platform.
- AWS
Buyer facts and open questions →
4 sources checked
Archives & collections management
Archivematica
Open-source digital-preservation processing system with an institutional AWS deployment recipe.
- AWS
Buyer facts and open questions →
4 sources checked
Archives & collections management
ArchivesSpace
Self-hosted archival description and collections management with searchable finding aids.
- AWS
Buyer facts and open questions →
3 sources checked
Archives & collections management +1 more
Avalon Media System
Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- AWS
Buyer facts and open questions →
3 sources checked
Legacy system archive & access +1 more
Browsertrix
Open-source browser-based web archiving and collection-management application.
- DigitalOcean
Buyer facts and open questions →
3 sources checked
Archives & collections management
Dataverse Self-Hosted
Institutional research-data repository for dataset preservation, metadata, access and citation.
- AWS
Buyer facts and open questions →
6 sources checked
Archives & collections management
DSpace Self-Hosted
Institutional digital repository for scholarly works, datasets and cultural collections.
- AWS
Buyer facts and open questions →
5 sources checked
Archives & collections management +1 more
Fedora Repository
Open-source preservation repository with an AWS Terraform deployment.
- AWS
Buyer facts and open questions →
3 sources checked
Archives & collections management
FormKiQ Archives and Collections Management
Directory PublisherBusiness solution
Connect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.
- AWS
Buyer facts and open questions →
5 sources checked
Archives & collections management
InvenioRDM
Research and institutional repository platform for digital-resource deposit, curation and discovery.
- AWS
Buyer facts and open questions →
6 sources checked
Archives & collections management
Islandora (ISLE)
Open-source digital repository and collections platform with a community DigitalOcean deployment.
- DigitalOcean
Buyer facts and open questions →
4 sources checked
Archives & collections management
Omeka S
Digital collections publishing for libraries, archives, museums and research institutions.
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
Buyer facts and open questions →
24 sources checked
How these listings fit
- Arches
- Open-source cultural-heritage inventory and resource-information platform.
- Archivematica
- Open-source digital-preservation processing system with an institutional AWS deployment recipe.
- ArchivesSpace
- Dedicated archival description and collections management with finding aids and digital-object metadata. ArchivesSpace describes and links digital objects; it is not a DAM, file repository or digitization workflow system.
- Avalon Media System
- Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- Browsertrix
- Open-source browser-based web archiving and collection-management application.
- Dataverse Self-Hosted
- Preserves and publishes research datasets in metadata-rich collections with persistent identifiers and access controls. It is a research-data repository, not grant-application or sponsored-award administration software.
- DSpace Self-Hosted
- Manages institutional and digital collections with deposit, metadata, access and discovery for scholarly and cultural material. Repository preservation is distinct from grant administration or a general enterprise records policy engine.
- Fedora Repository
- Open-source preservation repository with an AWS Terraform deployment.
- FormKiQ Archives and Collections Management Directory Publisher
- Archival description, accessions, digital collections and researcher access.
- InvenioRDM
- Provides institutional and research-data repositories with deposit, curation, metadata, access and dissemination. Research-data repository functions do not establish grant administration or clinical regulatory-document control.
- Islandora (ISLE)
- Open-source digital repository and collections platform with a community DigitalOcean deployment.
- Omeka S
- Describes digital collection items and media with shared metadata, item sets, linked data and independently curated public exhibits. This does not establish formal retention or legal-hold controls.
Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →