Arches

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

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Source / language package

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

    Arches AWS EC2 Guide ↗ · 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 methodSource / language package
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU 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 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.

Versioned Arches external user OAuth/OIDC flow; provider compatibility and local authorization require configuration · Source ↗ · Token validation and account mapping backend ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Project-documented manual EC2 installation; runtime and source-deployment versions must be aligned · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Current development/test and build prerequisites, not a version-specific 100-user/1-TB HA production minimum · 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.

Arches; 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 7.6.28 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

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

Community & 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.

Category fit

Archives & collections management
Open-source cultural-heritage inventory and resource-information platform.

Compare within Archives & collections management

  • ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
    • AWS
    Customer-operated · Open Source / Open Core
  • ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
    • AWS
    Customer-operated · Open Source / Open Core
  • Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
    • AWS
    Customer-operated · Open Source / Open Core
  • BrowsertrixOpen-source browser-based web archiving and collection-management application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
    • AWS
    Customer-operated · Open Source / Open Core
  • DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
    • AWS
    Customer-operated · Open Source / Open Core
  • Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
    • AWS
    Customer-operated · Open Source / Open Core
  • FormKiQ Archives and Collections Management Directory PublisherConnect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.
    • AWS
    Customer-operated · Commercial Only

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Arches AWS EC2 Guide ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory