ArchivesSpace
Self-hosted archival description and collections management with searchable finding aids.
3 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
Docker or ZIP distribution with production MySQL and required search/runtime services
Runs in
Documented customer environment
Customer-operated archival application, MySQL and search
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer operates the application, production database, search services and backups.
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.
ArchivesSpace community Terraform deployment on AWS ECS ↗ · Source checked 2026-11-12
Complete AWS infrastructure example for the ArchivesSpace module ↗ · Source checked 2026-11-12
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 | Docker or ZIP distribution with production MySQL and required search/runtime services |
|---|---|
| Infrastructure | Servers / containers The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless. |
| Licensing model | Open Source / Open Core ArchivesSpace is released under the OSI-approved Educational Community License 2.0. Optional membership, documentation and support benefits do not make its code open-core. |
| License | Open source; optional membership/support services |
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 official custom-authentication guide links the Lyrasis-maintained plugin, whose README documents tested SAML and CAS strategies, IdP redirects/callbacks and creation of ArchivesSpace user records. Group membership and permissions remain local; select the plugin revision matching the ArchivesSpace release.
Optional plugin user federation; maintainer version compatibility must be checked, not assumed from core LDAP support · Source ↗ · Project authentication extension guide ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The administration guide documents a ZIP distribution and Docker installation. ZIP deployments require a compatible Java runtime and Solr; production database/search configuration and backups remain separate.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The getting-started guide requires at least 1,024 MB allocated to the application and recommends 2 GB. Java/Solr/database resources and workload growth are additional capacity considerations.
ArchivesSpace application allocation; not total stack RAM · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The v4.2.1 core is licensed under Educational Community License 2.0. This software grant is distinct from paid hosting, support or institutional service arrangements; no cloud-service price is implied by the source licence.
Versioned ArchivesSpace core; third-party components and optional services retain separate terms · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was v4.2.1, published 2026-07-10. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream archivesspace/archivesspace release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
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 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.
Category fit
- Archives & collections management
- 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.
Compare within Archives & collections management
- ArchesOpen-source cultural-heritage inventory and resource-information platform.
- AWS
- ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
- 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
- Official installation methods and production requirements ↗docs.archivesspace.org
- Hosting, licensing and digital-object scope ↗archivesspace.org
- Licensing and edition terms ↗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.
- ArchivesSpace community Terraform deployment on AWS ECS ↗ · AWS
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
This maintained community Terraform module deploys ArchivesSpace as an ECS service on Fargate or EC2, with an Nginx proxy, database setup and EFS persistence. The inspected complete example uses upstream ArchivesSpace and Solr images plus RDS and load balancing. This is a community-maintained deployment recipe, not an upstream support commitment; pin compatible application/Solr/database versions and review secrets, storage, networking and upgrades.
- Complete AWS infrastructure example for the ArchivesSpace module ↗ · AWS
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected example provisions the supporting VPC, ECS, EFS, RDS, load-balancer and service-discovery resources in the Terraform caller's AWS account. It references official archivesspace/archivesspace and archivesspace/solr images. Adapt example domain names, image tags, sizing and access controls to the actual deployment.
- ArchivesSpace community Terraform deployment on AWS ECS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked