
# Arches

Open-source cultural-heritage inventory and resource-information platform.

Canonical page: https://launchinyourcloud.com/directory/arches/
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.


## Arches

Open-source cultural-heritage inventory and resource-information platform.

- Listing: https://launchinyourcloud.com/directory/arches/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Source / language package
- Architecture: Arches application on EC2, PostgreSQL/PostGIS and separately configured media storage.
- Operations: 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.
- Product website: https://github.com/archesproject/arches
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Arches application on EC2, PostgreSQL/PostGIS and separately configured media storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source cultural-heritage inventory and resource-information platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/ (checked 2026-11-19). 


### Cloud deployment evidence

- Arches AWS EC2 Guide (aws): https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/
  Arches application on EC2, PostgreSQL/PostGIS and separately configured media storage. The 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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes chiatt, apeters, chrabyrd, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/archesproject/arches/graphs/contributors

- Upstream project: https://github.com/archesproject/arches

### Sources

- Arches AWS EC2 Guide: https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/

- AWS S3 Guide: https://arches.readthedocs.io/en/stable/deployment/using-aws-s3/

- AGPL-3.0 LICENSE: https://github.com/archesproject/arches/blob/dev/8.1.x/LICENSE.txt

- GitHub Releases: https://github.com/archesproject/arches/releases

### Licensing sources

- https://github.com/archesproject/arches/blob/dev/8.1.x/LICENSE.txt

### Infrastructure sources

- https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/


### 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 7.6.28 application implements an external OAuth browser redirect/callback and a configured authentication backend that exchanges tokens, validates identity and logs the mapped user into Arches. Configure the provider, claims, domain/registration policy and backend deliberately; this is user login code rather than only an OAuth library dependency. Scope: Versioned Arches external user OAuth/OIDC flow; provider compatibility and local authorization require configuration. Source: https://github.com/archesproject/arches/blob/7.6.28/arches/app/views/auth.py (reviewed 2026-11-21). Supporting source: Token validation and account mapping backend — https://github.com/archesproject/arches/blob/7.6.28/arches/app/utils/external_oauth_backend.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official AWS EC2 guide documents dependency setup, installation of Arches and deployment of an application project. Select compatible application, search/database, Python and frontend-toolchain releases; the manual EC2 workflow is not a complete hardened or HA infrastructure template. Scope: Project-documented manual EC2 installation; runtime and source-deployment versions must be aligned. Source: https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The current requirements guide gives development/test resources of 4 GB RAM, 2 GB for dependencies/application and 8 GB for uploaded files/backups, with more storage expected for real collections. Building frontend assets requires at least 8 GB RAM, and production search/application capacity is larger and workload-dependent. Scope: Current development/test and build prerequisites, not a version-specific 100-user/1-TB HA production minimum. Source: https://arches.readthedocs.io/en/stable/installing/requirements-and-dependencies/ (reviewed 2026-11-21).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Arches; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/archesproject/arches/blob/dev/8.1.x/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 7.6.28 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Arches upstream application; verify compatibility with the selected package. Source: https://github.com/archesproject/arches/releases/tag/7.6.28 (reviewed 2026-11-19).






