
# ArchivesSpace

Self-hosted archival description and collections management with searchable finding aids.

Canonical page: https://launchinyourcloud.com/directory/archivesspace/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## ArchivesSpace

Self-hosted archival description and collections management with searchable finding aids.

- Listing: https://launchinyourcloud.com/directory/archivesspace/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open source; optional membership/support services
- Licensing model: open-source
- Installation: Docker or ZIP distribution with production MySQL and required search/runtime services
- Architecture: Customer-operated archival application, MySQL and search
- Operations: Customer operates the application, production database, search services and backups.
- Product website: https://archivesspace.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/dts-hosting/terraform-aws-archivesspace (checked 2026-11-12). Source: https://github.com/dts-hosting/terraform-aws-archivesspace/blob/main/examples/complete/main.tf (checked 2026-11-12). 


### Cloud deployment evidence

- ArchivesSpace community Terraform deployment on AWS ECS (aws): https://github.com/dts-hosting/terraform-aws-archivesspace
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Complete AWS infrastructure example for the ArchivesSpace module (aws): https://github.com/dts-hosting/terraform-aws-archivesspace/blob/main/examples/complete/main.tf
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official installation methods and production requirements: https://docs.archivesspace.org/administration/getting_started/

- Hosting, licensing and digital-object scope: https://archivesspace.org/about/faqs

- Licensing and edition terms: https://github.com/archivesspace/archivesspace/blob/master/README.md

### Licensing sources

- https://github.com/archivesspace/archivesspace/blob/master/README.md

- https://archivesspace.org/about/faqs

### Infrastructure sources

- https://docs.archivesspace.org/administration/getting_started/

- https://archivesspace.org/about/faqs


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Optional plugin user federation; maintainer version compatibility must be checked, not assumed from core LDAP support. Source: https://github.com/lyrasis/aspace-oauth (reviewed 2026-11-21). Supporting source: Project authentication extension guide — https://docs.archivesspace.org/customization/authentication/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.archivesspace.org/administration/getting_started/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. 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. Scope: ArchivesSpace application allocation; not total stack RAM. Source: https://docs.archivesspace.org/administration/getting_started/ (reviewed 2026-11-14).

- License pricing: Documented. 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. Scope: Versioned ArchivesSpace core; third-party components and optional services retain separate terms. Source: https://github.com/archivesspace/archivesspace/blob/v4.2.1/COPYING (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream archivesspace/archivesspace release record; commercial editions and deployment packages may differ. Source: https://github.com/archivesspace/archivesspace/releases/tag/v4.2.1 (reviewed 2026-11-14).






