Archivematica
Open-source digital-preservation processing system with an institutional AWS deployment recipe.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Terraform
Runs in
Documented customer environment
Wellcome Collection's Terraform-managed application services, databases and preservation storage.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Wellcome Terraform ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Terraform |
|---|---|
| Infrastructure | Servers / containers Wellcome Collection's Terraform-managed application services, databases and preservation storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The 1.18 security guide documents Shibboleth and CAS user authentication for both Dashboard and Storage Service, with separately configured backends. OIDC is also described but explicitly experimental. These login paths are distinct from pipeline/API service credentials.
Versioned Dashboard/Storage Service federation; retain the OIDC experimental qualification · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The 1.18 installation guide documents supported dependency/package installation and links advanced Ansible deployment options. Choose matching Dashboard, Storage Service and dependency versions and configure processing/storage locations, secrets and backups. Institutional AWS Terraform examples have their own maintenance and version scope.
Official package/automation installation workflow; not a claim that every historical institutional stack supports the current release · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The 1.18 guide recommends a viable production minimum of 2 CPU cores, 4 GB RAM and 200 GB processing disk, with 8 cores/16 GB more commonly deployed. It separately recommends 20 GB plus four times the largest transfer for processing space; source and archival storage, media type and concurrency change requirements.
Production processing guidance; archival retention storage and HA replicas are additional · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Archivematica; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream v1.18.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Archivematica upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The 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.
Community & maintenance
The reviewed upstream contributor history includes mcantelon, Hwesta, sevein, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Archives & collections management
- Open-source digital-preservation processing system with an institutional AWS deployment recipe.
Compare within Archives & collections management
- ArchesOpen-source cultural-heritage inventory and resource-information platform.
- AWS
- ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
- AWS
- Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- AWS
- BrowsertrixOpen-source browser-based web archiving and collection-management application.
- DigitalOcean
- Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
- AWS
- DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
- AWS
- Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
- AWS
- FormKiQ Archives and Collections Management Directory PublisherConnect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.
- AWS
Showing 8 of 11 other listings in Archives & collections management. These products address related workflows; read their category-fit notes before comparing scope. See all of Archives & collections management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Wellcome Terraform ↗github.com
- Bootstrap Docs ↗docs.wellcomecollection.org
- AGPL-3.0 LICENSE ↗github.com
- GitHub Releases ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Wellcome Terraform ↗ · AWS
Institution deployment · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Wellcome Collection's Terraform-managed application services, databases and preservation storage. The 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.
- Wellcome Terraform ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com