
# Archives & collections management on AWS

Compare documented Archives & collections management deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/archives-collections-management/
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.


## Provider guidance

- Account boundary: AWS account
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

10 listings.


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







## Archivematica

Open-source digital-preservation processing system with an institutional AWS deployment recipe.

- Listing: https://launchinyourcloud.com/directory/archivematica/
- 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: Terraform
- Architecture: Wellcome Collection's Terraform-managed application services, databases and preservation 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/wellcomecollection/archivematica-infrastructure
- 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 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.

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

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.


### Category fit

- archives-collections-management: Open-source digital-preservation processing system with an institutional AWS deployment recipe.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/wellcomecollection/archivematica-infrastructure (checked 2026-11-19). 


### Cloud deployment evidence

- Wellcome Terraform (aws): https://github.com/wellcomecollection/archivematica-infrastructure
  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.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


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

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/artefactual/archivematica/graphs/contributors

- Upstream project: https://github.com/artefactual/archivematica

### Sources

- Wellcome Terraform: https://github.com/wellcomecollection/archivematica-infrastructure

- Bootstrap Docs: https://docs.wellcomecollection.org/archivematica/administering-archivematica/bootstrapping

- AGPL-3.0 LICENSE: https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE

- GitHub Releases: https://github.com/artefactual/archivematica/releases

### Licensing sources

- https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE

### Infrastructure sources

- https://github.com/wellcomecollection/archivematica-infrastructure


### 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 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. Scope: Versioned Dashboard/Storage Service federation; retain the OIDC experimental qualification. Source: https://www.archivematica.org/en/docs/archivematica-1.18/admin-manual/security/security/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Official package/automation installation workflow; not a claim that every historical institutional stack supports the current release. Source: https://www.archivematica.org/en/docs/archivematica-1.18/admin-manual/installation-setup/installation/installation/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. 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. Scope: Production processing guidance; archival retention storage and HA replicas are additional. Source: https://www.archivematica.org/en/docs/archivematica-1.18/admin-manual/installation-setup/installation/installation/ (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: Archivematica; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Archivematica upstream application; verify compatibility with the selected package. Source: https://github.com/artefactual/archivematica/releases/tag/v1.18.0 (reviewed 2026-11-19).







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







## Avalon Media System

Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

- Listing: https://launchinyourcloud.com/directory/avalon-media-system/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: Avalon application and media-processing/storage services provisioned by the project's Terraform scripts.
- 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/avalonmediasystem/avalon-terraform
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

- digital-asset-management: Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/avalonmediasystem/avalon-terraform (checked 2026-11-19). 


### Cloud deployment evidence

- avalon-terraform (aws): https://github.com/avalonmediasystem/avalon-terraform
  Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes cjcolvar, masaball, Dananji, 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/avalonmediasystem/avalon/graphs/contributors

- Upstream project: https://github.com/avalonmediasystem/avalon

### Sources

- avalon-terraform: https://github.com/avalonmediasystem/avalon-terraform

- Apache-2.0 LICENSE: https://github.com/avalonmediasystem/avalon/blob/main/LICENSE

- GitHub Releases: https://github.com/avalonmediasystem/avalon/releases

### Licensing sources

- https://github.com/avalonmediasystem/avalon/blob/main/LICENSE

### Infrastructure sources

- https://github.com/avalonmediasystem/avalon-terraform


### 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. Avalon v8.2.2 publishes an OmniAuth integration that loads configured providers, includes the SAML strategy and maps the returned identity through its user callbacks. The published source confirms this integration path; the default local-account setup does not enable SSO. Supply and test the institutional IdP, attributes and account mapping. Scope: Avalon v8.2.2 configurable OmniAuth/SAML application login; institution-specific provider configuration required. Source: https://github.com/avalonmediasystem/avalon/blob/v8.2.2/config/initializers/devise.rb (reviewed 2026-11-20). Supporting source: Published SAML strategy dependency — https://github.com/avalonmediasystem/avalon/blob/v8.2.2/Gemfile. Supporting source: Application sign-in callback — https://github.com/avalonmediasystem/avalon/blob/v8.2.2/app/controllers/users/omniauth_callbacks_controller.rb. Supporting source: Provider identity mapping — https://github.com/avalonmediasystem/avalon/blob/v8.2.2/app/models/user.rb.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official project publishes a Terraform AWS deployment with application containers, networking, persistent services and initial-admin instructions. It targets low-to-medium traffic. Configure DNS/state, credentials, compatible application/dependency images, storage and email; this is not certification of an arbitrary HA workload. Scope: Avalon AWS Terraform deployment; provisioner and application releases must be version-matched. Source: https://github.com/avalonmediasystem/avalon-terraform/blob/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/avalonmediasystem/avalon-terraform/tree/main. Artifact reference: main (moving branch); select compatible Avalon/container and Terraform/provider versions.

- Minimum footprint / sizing: Documented. The AWS Terraform recipe defaults to a t3.large application/Compose host with a 75 GB root volume, plus separate supporting database/storage resources. These are adjustable recipe defaults for low-to-medium traffic, not a minimum for every media library or a validated 100-user, 1 TB HA design. Scope: Avalon project AWS example allocation; transcoding, derivatives, database, object storage, backups and replicas must be sized together. Source: https://github.com/avalonmediasystem/avalon-terraform/blob/main/variables.tf (reviewed 2026-11-20). Supporting source: Recipe goals and architecture — https://github.com/avalonmediasystem/avalon-terraform/blob/main/README.md.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Avalon Media System; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/avalonmediasystem/avalon/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Dataverse Self-Hosted

Institutional research-data repository for dataset preservation, metadata, access and citation.

- Listing: https://launchinyourcloud.com/directory/dataverse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache-2.0 application; dependencies and dataset reuse licenses are separate.
- Licensing model: open-source
- Installation: Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release.
- Architecture: Java/Payara application with PostgreSQL, Solr and local or object data storage
- Operations: Institution operates application and infrastructure, permissions, persistent identifiers, database/files, backups, monitoring and upgrades. External identity, citation and analysis services require configuration.
- Product website: https://dataverse.org/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used 6.12.1; Docker users need the corrected 6.12.1-noble-r3 image or newer described by upstream. The AWS developer script creates the full application but is not a production hardening shortcut. Configure HTTPS, restricted APIs, database/file recovery and appropriate sensitive-data controls before opening access. This is unrelated to Microsoft Dataverse.

The Dataverse application is Apache-2.0. Stored research datasets can use different rights and licenses; component licenses and optional services remain separate.

Java/Payara application with PostgreSQL, Solr and local or object data storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- archives-collections-management: Preserves and publishes research datasets in metadata-rich collections with persistent identifiers and access controls. It is a research-data repository, not grant-application or sponsored-award administration software.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://guides.dataverse.org/en/6.12.1/developers/deployment.html (checked 2026-11-13). 


### Cloud deployment evidence

- Upstream AWS EC2 deployment script and instructions (aws): https://guides.dataverse.org/en/6.12.1/developers/deployment.html
  The project documents AWS credential/role setup and a script that creates an EC2 instance with the Dataverse application, browser access and cleanup steps in the operator account. It is developer-oriented and warns about branch/dependency compatibility. Pair it with the supported-release production installer, hardening and backup guidance.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

Harvard IQSS develops the project with sustained multi-institution community participation. The maintained 6.12.1 release includes security fixes and detailed upgrade instructions, and the project documents its institutional research repository purpose.

Reviewed 2026-11-13.

- Reviewed release and corrected Docker-image notice: https://github.com/IQSS/dataverse/releases/tag/v6.12.1

- Institutional project and community: https://dataverse.org/about/

### Sources

- Production installation guide for 6.12.1: https://guides.dataverse.org/en/6.12.1/installation/index.html

- Production security, identifiers and storage configuration: https://guides.dataverse.org/en/6.12.1/installation/config.html

- Repository and collection scope: https://dataverse.org/about/

- Upstream AWS EC2 deployment script and instructions: https://guides.dataverse.org/en/6.12.1/developers/deployment.html

- Upstream software license: https://github.com/IQSS/dataverse/blob/develop/LICENSE.md

- Reviewed release and corrected Docker-image notice: https://github.com/IQSS/dataverse/releases/tag/v6.12.1

### Licensing sources

- https://github.com/IQSS/dataverse/blob/develop/LICENSE.md

### Infrastructure sources

- https://guides.dataverse.org/en/6.12.1/installation/index.html

- https://guides.dataverse.org/en/6.12.1/developers/deployment.html


### 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 6.12.1 installation guides document OIDC login with configurable providers and a separate Shibboleth integration. Provider registration, client/redirect settings and stable account identifiers require configuration; login is distinct from API-token access and repository permissions. Scope: Versioned self-hosted repository-user federation. Source: https://guides.dataverse.org/en/6.12.1/installation/oidc.html (reviewed 2026-11-21). Supporting source: Shibboleth integration — https://guides.dataverse.org/en/6.12.1/installation/shibboleth.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned 6.12.1 installation guide separates standard and container installation paths. Prepare the database, search/application services and configuration before following the selected deployment workflow. Scope: Dataverse 6.12.1 installation paths; not every community cloud package. Source: https://guides.dataverse.org/en/6.12.1/installation/prep.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The 6.12.1 guide gives an 8-GB RAM/50-GB disk test-VM example and a much larger Harvard reference with separate application, Solr and R servers plus RDS and S3. Those examples illustrate workload variation rather than a universal production minimum; data services, ingest and retention need separate capacity planning. Scope: Published test and institutional reference examples, not validated 100-user/1-TB HA sizing or a current cost estimate. Source: https://guides.dataverse.org/en/6.12.1/installation/prep.html (reviewed 2026-11-21).

- License pricing: Documented. The v6.12.1 software is Apache-2.0 licensed. Hosting, persistent storage, identifiers, external services and professional support require separate arrangements; a repository installation is distinct from using Harvard Dataverse as a hosted service. Scope: Versioned Dataverse software licence; optional components and services have separate terms. Source: https://github.com/IQSS/dataverse/blob/v6.12.1/LICENSE.md (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v6.12.1, published 2026-10-08. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream IQSS/dataverse release record; commercial editions and deployment packages may differ. Source: https://github.com/IQSS/dataverse/releases/tag/v6.12.1 (reviewed 2026-11-14).







## DSpace Self-Hosted

Institutional digital repository for scholarly works, datasets and cultural collections.

- Listing: https://launchinyourcloud.com/directory/dspace/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause core; dependencies and optional commercial hosting/support have separate terms.
- Licensing model: open-source
- Installation: Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate.
- Architecture: Persistent Java backend and Node frontend services with PostgreSQL, Solr and repository storage
- Operations: Institution manages the application releases, collection permissions, metadata, storage, backups and upgrades. AWS can operate container compute through Fargate; the institution still operates its repository services.
- Product website: https://dspace.org/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used backend/frontend 10.1. Follow the current installation guide for runtime and database/search compatibility; protect Solr from public access and enable HTTPS. The Johns Hopkins AWS case study demonstrates an institutional deployment, not a turnkey installer or a blanket upstream cloud-support commitment. External identity, analytics and scholarly integrations are operator choices.

The DSpace core is BSD-3-Clause. Review backend/frontend dependencies and any paid service-provider agreement separately.

Persistent Java backend and Node frontend services with PostgreSQL, Solr and repository storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- archives-collections-management: Manages institutional and digital collections with deposit, metadata, access and discovery for scholarly and cultural material. Repository preservation is distinct from grant administration or a general enterprise records policy engine.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/ (checked 2026-11-13). 


### Cloud deployment evidence

- Johns Hopkins institutional DSpace deployment on AWS (aws): https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/
  AWS and the Johns Hopkins authors describe the library team migrating and operating JScholarship on ECS/Fargate with cloud backing services. This establishes application hosting by an adopting institution, not a vendor-hosted subscription or upstream support certification. Adapt the architecture to the selected release and operational requirements.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

DSpace has established Lyrasis/community governance and named institutional use. Johns Hopkins describes its operating repository, while the project publishes matched 10.1 releases and ongoing maintenance guidance.

Reviewed 2026-11-13.

- Project, governance and institutional community: https://dspace.org/

- Current 10.1 releases: https://dspace.org/download/

- Johns Hopkins repository deployment: https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/

### Sources

- Current backend/frontend downloads and upgrades: https://dspace.org/download/

- DSpace 10 production installation: https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944708/Installing%2BDSpace

- Johns Hopkins institutional DSpace deployment on AWS: https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/

- Upstream core license: https://github.com/DSpace/DSpace/blob/main/LICENSE

- Project, governance and institutional community: https://dspace.org/

### Licensing sources

- https://github.com/DSpace/DSpace/blob/main/LICENSE

### Infrastructure sources

- https://dspace.org/download/

- https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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 dspace-10.1 backend supplies OIDC authentication configuration with provider endpoints, client credentials, redirect, identity-claim mapping, self-registration policy and an optional login group. Enable the appropriate authentication method and configure the matching frontend; the settings do not establish compatibility with every IdP or packaged image. Scope: Versioned DSpace repository-user OIDC plugin configuration, not machine API tokens. Source: https://github.com/DSpace/DSpace/blob/dspace-10.1/dspace/config/modules/authentication-oidc.cfg (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README explicitly says its Docker images/Compose quickstarts are not production-ready and are intended for development/testing. Match backend/frontend versions and follow the separate production architecture. Scope: Upstream backend development/test artifacts; not the AWS/JHU production reference. Source: https://github.com/DSpace/DSpace (reviewed 2026-11-14). Deployment artifact: https://github.com/DSpace/DSpace. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The 10.x installation guide separates the Java backend, Node/Angular frontend, PostgreSQL and Solr. Its example Tomcat heap setting is process-level configuration, not a complete host minimum; a quantitative production CPU/RAM/storage baseline for the full reference workload was not established. Scope: Production software/component prerequisites confirmed; whole-system hardware and HA sizing remain unconfirmed. Source: https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944708/Installing%2BDSpace (reviewed 2026-11-21).

- License pricing: Documented. The dspace-10.1 backend core is BSD-3-Clause licensed. Frontend packages, dependencies, hosting and any commercial support must be assessed separately; the source licence is not a managed repository subscription. Scope: Versioned DSpace backend core; not an entitlement to every third-party package or service. Source: https://github.com/DSpace/DSpace/blob/dspace-10.1/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was dspace-10.1, published 2026-09-14. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: DSpace/DSpace backend repository only; the separately released Angular frontend and commercial/provider packages may differ. Source: https://github.com/DSpace/DSpace/releases/tag/dspace-10.1 (reviewed 2026-11-14).







## Fedora Repository

Open-source preservation repository with an AWS Terraform deployment.

- Listing: https://launchinyourcloud.com/directory/fedora-repository/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Package / binary installer
- Architecture: Fedora Repository application on EC2 with PostgreSQL in RDS.
- 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://wiki.lyrasis.org/display/FF/Fedora+Repository+Home
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Fedora Repository application on EC2 with PostgreSQL in RDS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source preservation repository with an AWS Terraform deployment.

- document-management: Open-source preservation repository with an AWS Terraform deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer (checked 2026-11-19). 


### Cloud deployment evidence

- fcrepo-aws-deployer (aws): https://github.com/fcrepo-exts/fcrepo-aws-deployer
  Fedora Repository application on EC2 with PostgreSQL in RDS. The repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes cbeer, ajs6f, whikloj, 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/fcrepo/fcrepo/graphs/contributors

- Upstream project: https://github.com/fcrepo/fcrepo

### Sources

- fcrepo-aws-deployer: https://github.com/fcrepo-exts/fcrepo-aws-deployer

- Apache-2.0 LICENSE: https://github.com/fcrepo/fcrepo/blob/main/LICENSE

- GitHub Releases: https://github.com/fcrepo/fcrepo/releases

### Licensing sources

- https://github.com/fcrepo/fcrepo/blob/main/LICENSE

### Infrastructure sources

- https://github.com/fcrepo-exts/fcrepo-aws-deployer


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Sources checked — unresolved. The reviewed Fedora deployment material identifies servlet-container/application security, but does not establish a version-matched external SAML/OIDC login configuration for the repository. A Java authentication library or cloud account IAM alone is not sufficient evidence of a supported user-federation path. Scope: Fedora Repository application authentication; institutional front ends and external reverse-proxy integrations need their own configuration evidence. Source: https://github.com/fcrepo/fcrepo/blob/main/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Fedora community publishes a Terraform AWS deployer for the application and RDS, while upstream publishes WAR artifacts for a servlet container. The Terraform inputs and application/server versions must be matched; review its example database/instance defaults rather than treating the recipe as a current production or HA certification. Scope: Community-maintained Fedora AWS deployment recipe; provider path and upstream application artifacts have separate versions. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/fcrepo-exts/fcrepo-aws-deployer/tree/master. Artifact reference: master (moving branch); select compatible Fedora, servlet-container and database versions. Supporting source: Upstream runtime packaging — https://github.com/fcrepo/fcrepo/blob/main/README.md.

- Minimum footprint / sizing: Documented. The community AWS recipe defaults to a t3.small application instance and a small RDS database with a 10 GB allocation. These configurable example values do not establish a production minimum; verify currently supported database classes/engine versions, repository-object storage, index/load growth, backups and redundancy separately. Scope: Fedora community AWS recipe defaults, not a validated 1 TB repository or HA design. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/README.md (reviewed 2026-11-20). Supporting source: Configurable recipe inputs — https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/variables.tf.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Fedora Repository; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/fcrepo/fcrepo/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## FormKiQ Archives and Collections Management

Connect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.

- Listing: https://launchinyourcloud.com/directory/formkiq-archives-collections-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/archives-collections-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- archives-collections-management: Archival description, accessions, digital collections and researcher access.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Archives and Collections Management solution: https://formkiq.com/solutions/archives-collections-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/archives-collections-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Archives and Collections Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/archives-collections-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The overview distinguishes rights metadata from document permissions that enforce access; publication and restricted materials need an agreed review workflow. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Archives and Collections Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/archives-collections-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Archives and Collections Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/archives-collections-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Archives and Collections Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/archives-collections-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Archives and Collections Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/archives-collections-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## InvenioRDM

Research and institutional repository platform for digital-resource deposit, curation and discovery.

- Listing: https://launchinyourcloud.com/directory/inveniordm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT application code; framework modules, institutional customizations and dependencies retain their own terms.
- Licensing model: open-source
- Installation: Official Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration.
- Architecture: Persistent Python web/worker services with PostgreSQL, search, queue/cache and local or object storage
- Operations: Institution operates application and workers, identity, search, data services, configuration, backups and upgrades. Cloud resources are separate from the public Zenodo hosted service.
- Product website: https://inveniosoftware.org/products/rdm/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

The upstream project identifies v14. Caltech documents its own EC2 deployment and earlier release-specific setup, not universal v14 compatibility. Follow current upstream production requirements and review the institution-specific files before reuse. Docker Compose reference defaults require production adaptation. External DOI, identity, mail and analytics services have separate data boundaries.

The invenio-app-rdm application is MIT licensed. Its framework/modules, optional services and institution-specific customizations must be reviewed under their own licenses.

Persistent Python web/worker services with PostgreSQL, search, queue/cache and local or object storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- archives-collections-management: Provides institutional and research-data repositories with deposit, curation, metadata, access and dissemination. Research-data repository functions do not establish grant administration or clinical regulatory-document control.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/caltechlibrary/caltechauthors (checked 2026-11-13). 


### Cloud deployment evidence

- CaltechAUTHORS institutional AWS EC2 deployment (aws): https://github.com/caltechlibrary/caltechauthors
  Caltech Library documents running its customized InvenioRDM repository on AWS EC2 with Ubuntu, application installation and S3 configuration. This is an institution-maintained deployment example, not a stock v14 installer or CERN support commitment. Replace institutional values and reconcile runtime, dependencies, secrets and upgrades with the chosen current release.
  Source type: institution-deployment; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

CERN publishes a participating-institution governance model and ongoing InvenioRDM releases. Caltech Library maintains a named institutional deployment and source customization, establishing use beyond a demo or star count.

Reviewed 2026-11-13.

- Institutional governance: https://inveniosoftware.org/governance/

- Current release and community: https://inveniosoftware.org/products/rdm/

- Named Caltech institutional repository: https://github.com/caltechlibrary/caltechauthors

### Sources

- Current product and release: https://inveniosoftware.org/products/rdm/

- Production runtime, persistence and operations: https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md

- Institutional cloud-init prerequisites: https://github.com/caltechlibrary/cloud-init-examples/blob/main/invenio-rdm-13-init.yaml

- CaltechAUTHORS institutional AWS EC2 deployment: https://github.com/caltechlibrary/caltechauthors

- Application license: https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE

- Institutional governance: https://inveniosoftware.org/governance/

### Licensing sources

- https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE

### Infrastructure sources

- https://inveniosoftware.org/products/rdm/

- https://github.com/caltechlibrary/caltechauthors


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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 project explicitly describes integration with an institution’s SSO. Confirm the chosen authentication integration, user mapping and local customization for the deployed release. Scope: Institution-operated InvenioRDM; not a guarantee for an unmodified third-party package. Source: https://inveniosoftware.org/products/rdm/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production guide documents deployment strategies and points to the project-generated Compose reference and Invenio Helm charts used on Kubernetes/OpenShift. The Compose file is explicitly a development/reference configuration requiring production customization, persistence, backups and network configuration. Scope: Upstream production strategy with explicit reference-template limits. Source: https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md (reviewed 2026-11-21). Deployment artifact: https://github.com/inveniosoftware/helm-invenio. Artifact reference: repository default branch (moving); select charts compatible with the chosen InvenioRDM release.

- Minimum footprint / sizing: Documented. The production guide gives 4 vCPU/16 GB RAM as a typical co-located small-instance starting point for thousands of records and tens of concurrent users. It separately sizes web/worker processes, PostgreSQL, OpenSearch and lightweight services, with file storage driven by upload volume. Larger instances and HA require a different plan. Scope: Published small production reference, not a 100-user/1-TB HA guarantee. Source: https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md (reviewed 2026-11-21).

- License pricing: Documented. The reviewed invenio-app-rdm source uses the MIT License. This application licence is separate from the licences of its infrastructure dependencies and any institutional hosting, implementation or support agreement. Scope: Reviewed upstream application source on the moving master branch; assess dependency and service terms separately. Source: https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Omeka S

Digital collections publishing for libraries, archives, museums and research institutions.

- Listing: https://launchinyourcloud.com/directory/omeka-s/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 application; the packaged OIDC module is GPL-3.0-or-later.
- Licensing model: open-source
- Installation: Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation.
- Architecture: Persistent PHP application with MySQL, collection files, configuration, themes and extension modules
- Operations: Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.
- Product website: https://omeka.org/s/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed Cloudron 1.6.1 contains Omeka S 4.2.1 and OIDC module 1.2.0, whose declared compatibility covers Omeka S 4.x. The current package uses OIDC although its package manual still describes LDAP. Change initial administrator credentials, review identity/account linking and researcher defaults, and check extension compatibility before upgrades. Preserve the database, configuration, collection files, modules and themes. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.

GPLv3 application; the packaged OIDC module is GPL-3.0-or-later. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Persistent PHP application with MySQL, collection files, configuration, themes and extension modules. Cloudron provides a persistent server application, not event-driven application functions.


### Category fit

- archives-collections-management: Describes digital collection items and media with shared metadata, item sets, linked data and independently curated public exhibits. This does not establish formal retention or legal-hold controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (checked 2026-11-13). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudron.io/installation/ (checked 2026-11-13). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The Corporation for Digital Scholarship maintains Omeka S with an institutional community. Its showcase documents library and university collections, including Yale and the University of Utah, alongside continuing upstream releases. These establish real collection use, not provider certification.

Reviewed 2026-11-13.

- Institutional deployments: https://omeka.org/s/showcase/

- Project stewardship: https://omeka.org/s/

- Maintained release: https://github.com/omeka/omeka-s/releases/tag/v4.2.1

### Sources

- Official application scope and stewardship: https://omeka.org/s/

- Installation, requirements and upgrades: https://omeka.org/s/docs/user-manual/install/

- Extension compatibility: https://omeka.org/s/docs/user-manual/modules/

- Application user roles: https://omeka.org/s/docs/user-manual/admin/users/

- Cloudron package operations; identity manual lags current manifest: https://docs.cloudron.io/packages/omekas/

- Reviewed upstream release: https://github.com/omeka/omeka-s/releases/tag/v4.2.1

- Core GPL license: https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE

- Packaged OIDC module: https://github.com/cloudron-io/OmekaS-OIDC

- OIDC 1.2.0 compatibility: https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/config/module.ini

- OIDC module license: https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/composer.json

- Institutional collection deployments: https://omeka.org/s/showcase/

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

### Licensing sources

- https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE

- https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/composer.json

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/omekas/

- https://docs.cloudron.io/installation/


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 documented, 1 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: Documented. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/omekas/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The optional OIDC 1.2.0 module documents institutional user login, PKCE, claim/group-based roles and just-in-time provisioning, with PHP 8.1+ and Omeka S ^4.0 compatibility. Install and configure the module and IdP deliberately; this does not establish that every Cloudron or VPS image includes it. Scope: Third-party module-maintainer evidence for Omeka S user OIDC, distinct from the upstream core and packaged defaults. Source: https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/README.md (reviewed 2026-11-21). Supporting source: Versioned module compatibility declaration — https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/config/module.ini.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream manual documents a PHP application distribution with MySQL/MariaDB, writable files and configuration. These requirements describe upstream Omeka S, not the separately maintained Cloudron package. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://omeka.org/s/docs/user-manual/install/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The upstream installation manual identifies PHP extensions, database, web-server and filesystem requirements, while Cloudron documents its separate package configuration. Neither reviewed page establishes a quantitative production CPU/RAM/storage baseline for the repository, media derivatives, indexing and HA. Scope: Omeka S upstream requirements; no verified whole-host or Cloudron application memory minimum. Source: https://omeka.org/s/docs/user-manual/install/ (reviewed 2026-11-21). Supporting source: Cloudron package documentation — https://docs.cloudron.io/packages/omekas/.

- License pricing: Documented. The v4.2.1 core is GPLv3 licensed. Modules, themes, hosting and Cloudron or other packaged-platform subscriptions have separate terms; their charges are not an Omeka S core software licence fee. Scope: Versioned upstream Omeka S core; no packaged-platform or optional-module entitlement inferred. Source: https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE (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-06-18. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream omeka/omeka-s release record; commercial editions and deployment packages may differ. Source: https://github.com/omeka/omeka-s/releases/tag/v4.2.1 (reviewed 2026-11-14).






