{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Archival description, accessions, digital collections and researcher access.","formkiqSolution":"archives-collections-management","id":"archives-collections-management","name":"Archives \u0026 collections management"},"kind":"category","listings":[{"architecture":"Arches application on EC2, PostgreSQL/PostGIS and separately configured media storage.","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"archives-collections-management":"Open-source cultural-heritage inventory and resource-information platform."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Arches AWS EC2 Guide","url":"https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/archesproject/arches/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/archesproject/arches"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source cultural-heritage inventory and resource-information platform.","diligence":{"footprint":{"reviewed":"2026-11-21","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/","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-21","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/","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-19","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","status":"documented","summary":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-11-06T16:08:32Z","releaseTag":"7.6.28","reviewed":"2026-11-19","scope":"Arches upstream application; verify compatibility with the selected package","source":"https://github.com/archesproject/arches/releases/tag/7.6.28","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","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","status":"documented","summary":"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.","supportingSources":[{"title":"Token validation and account mapping backend","url":"https://github.com/archesproject/arches/blob/7.6.28/arches/app/utils/external_oauth_backend.py"}]}},"id":"arches","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/"],"install":"Source / language package","installMethods":["source"],"kind":"product","license":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/archesproject/arches/blob/dev/8.1.x/LICENSE.txt"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Arches","notes":"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.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Arches AWS EC2 Guide","url":"https://arches.readthedocs.io/en/stable/deployment/migrating-a-local-app-to-aws-ec2/"},{"title":"AWS S3 Guide","url":"https://arches.readthedocs.io/en/stable/deployment/using-aws-s3/"},{"title":"AGPL-3.0 LICENSE","url":"https://github.com/archesproject/arches/blob/dev/8.1.x/LICENSE.txt"},{"title":"GitHub Releases","url":"https://github.com/archesproject/arches/releases"}],"url":"https://launchinyourcloud.com/directory/arches/","website":"https://github.com/archesproject/arches"},{"architecture":"Wellcome Collection's Terraform-managed application services, databases and preservation storage.","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"archives-collections-management":"Open-source digital-preservation processing system with an institutional AWS deployment recipe."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-19","sourceType":"institution-deployment","title":"Wellcome Terraform","url":"https://github.com/wellcomecollection/archivematica-infrastructure","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/artefactual/archivematica/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/artefactual/archivematica"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source digital-preservation processing system with an institutional AWS deployment recipe.","diligence":{"footprint":{"reviewed":"2026-11-21","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/","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-21","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/","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-19","scope":"Archivematica; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE","status":"documented","summary":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2025-09-26T16:01:39Z","releaseTag":"v1.18.0","reviewed":"2026-11-19","scope":"Archivematica upstream application; verify compatibility with the selected package","source":"https://github.com/artefactual/archivematica/releases/tag/v1.18.0","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","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/","status":"documented","summary":"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."}},"id":"archivematica","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://github.com/wellcomecollection/archivematica-infrastructure"],"install":"Terraform","installMethods":["terraform"],"kind":"product","license":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Archivematica","notes":"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.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Wellcome Terraform","url":"https://github.com/wellcomecollection/archivematica-infrastructure"},{"title":"Bootstrap Docs","url":"https://docs.wellcomecollection.org/archivematica/administering-archivematica/bootstrapping"},{"title":"AGPL-3.0 LICENSE","url":"https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/artefactual/archivematica/releases"}],"url":"https://launchinyourcloud.com/directory/archivematica/","website":"https://github.com/wellcomecollection/archivematica-infrastructure"},{"architecture":"Customer-operated archival application, MySQL and search","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"community-template","title":"ArchivesSpace community Terraform deployment on AWS ECS","url":"https://github.com/dts-hosting/terraform-aws-archivesspace","vendorSupport":"not-assessed"},{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"community-template","title":"Complete AWS infrastructure example for the ArchivesSpace module","url":"https://github.com/dts-hosting/terraform-aws-archivesspace/blob/main/examples/complete/main.tf","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"}],"description":"Self-hosted archival description and collections management with searchable finding aids.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"ArchivesSpace application allocation; not total stack RAM","source":"https://docs.archivesspace.org/administration/getting_started/","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.archivesspace.org/administration/getting_started/","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-21","scope":"Versioned ArchivesSpace core; third-party components and optional services retain separate terms","source":"https://github.com/archivesspace/archivesspace/blob/v4.2.1/COPYING","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-07-10T12:50:44Z","releaseTag":"v4.2.1","reviewed":"2026-11-14","scope":"Upstream archivesspace/archivesspace release record; commercial editions and deployment packages may differ","source":"https://github.com/archivesspace/archivesspace/releases/tag/v4.2.1","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Optional plugin user federation; maintainer version compatibility must be checked, not assumed from core LDAP support","source":"https://github.com/lyrasis/aspace-oauth","status":"documented","summary":"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.","supportingSources":[{"title":"Project authentication extension guide","url":"https://docs.archivesspace.org/customization/authentication/"}]}},"id":"archivesspace","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.archivesspace.org/administration/getting_started/","https://archivesspace.org/about/faqs"],"install":"Docker or ZIP distribution with production MySQL and required search/runtime services","installMethods":["docker","package"],"kind":"product","license":"Open source; optional membership/support services","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://github.com/archivesspace/archivesspace/blob/master/README.md","https://archivesspace.org/about/faqs"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"ArchivesSpace","notes":"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.","operations":"Customer operates the application, production database, search services and backups.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official installation methods and production requirements","url":"https://docs.archivesspace.org/administration/getting_started/"},{"title":"Hosting, licensing and digital-object scope","url":"https://archivesspace.org/about/faqs"},{"title":"Licensing and edition terms","url":"https://github.com/archivesspace/archivesspace/blob/master/README.md"}],"url":"https://launchinyourcloud.com/directory/archivesspace/","website":"https://archivesspace.org/"},{"architecture":"Avalon application and media-processing/storage services provisioned by the project's Terraform scripts.","categories":["archives-collections-management","digital-asset-management"],"category":"Archives \u0026 collections management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"avalon-terraform","url":"https://github.com/avalonmediasystem/avalon-terraform","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/avalonmediasystem/avalon/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/avalonmediasystem/avalon"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.","diligence":{"footprint":{"reviewed":"2026-11-20","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","status":"documented","summary":"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.","supportingSources":[{"title":"Recipe goals and architecture","url":"https://github.com/avalonmediasystem/avalon-terraform/blob/main/README.md"}]},"iac":{"artifactRef":"main (moving branch); select compatible Avalon/container and Terraform/provider versions","artifactUrl":"https://github.com/avalonmediasystem/avalon-terraform/tree/main","reviewed":"2026-11-20","scope":"Avalon AWS Terraform deployment; provisioner and application releases must be version-matched","source":"https://github.com/avalonmediasystem/avalon-terraform/blob/main/README.md","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-19","scope":"Avalon Media System; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/avalonmediasystem/avalon/blob/main/LICENSE","status":"documented","summary":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-11-02T15:41:28Z","releaseTag":"v8.2.2","reviewed":"2026-11-19","scope":"Avalon Media System upstream application; verify compatibility with the selected package","source":"https://github.com/avalonmediasystem/avalon/releases/tag/v8.2.2","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-20","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","status":"documented","summary":"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.","supportingSources":[{"title":"Published SAML strategy dependency","url":"https://github.com/avalonmediasystem/avalon/blob/v8.2.2/Gemfile"},{"title":"Application sign-in callback","url":"https://github.com/avalonmediasystem/avalon/blob/v8.2.2/app/controllers/users/omniauth_callbacks_controller.rb"},{"title":"Provider identity mapping","url":"https://github.com/avalonmediasystem/avalon/blob/v8.2.2/app/models/user.rb"}]}},"id":"avalon-media-system","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://github.com/avalonmediasystem/avalon-terraform"],"install":"Terraform","installMethods":["terraform"],"kind":"product","license":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/avalonmediasystem/avalon/blob/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Avalon Media System","notes":"Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"avalon-terraform","url":"https://github.com/avalonmediasystem/avalon-terraform"},{"title":"Apache-2.0 LICENSE","url":"https://github.com/avalonmediasystem/avalon/blob/main/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/avalonmediasystem/avalon/releases"}],"url":"https://launchinyourcloud.com/directory/avalon-media-system/","website":"https://github.com/avalonmediasystem/avalon-terraform"},{"architecture":"Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook.","categories":["legacy-system-archive-access","archives-collections-management"],"category":"Legacy system archive \u0026 access","categoryFit":{"archives-collections-management":"Open-source browser-based web archiving and collection-management application.","legacy-system-archive-access":"Open-source browser-based web archiving and collection-management application."},"cloudEvidence":[{"clouds":["digitalocean"],"notes":"Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Browsertrix DigitalOcean Docs","url":"https://docs.browsertrix.com/deploy/ansible/digitalocean/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["digitalocean"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/webrecorder/browsertrix/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/webrecorder/browsertrix"}],"summary":"The reviewed upstream contributor history includes SuaYoo, ikreymer, tw4l, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source browser-based web archiving and collection-management application.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Browsertrix v1.26.6 chart component resource requests; not complete workload/HA sizing","source":"https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/values.yaml","status":"documented","summary":"The v1.26.6 chart defaults request 100 millicores/350 MiB for an API container and 12 millicores/512 MiB with a 2 GiB volume for bundled MongoDB; the deployment templates apply those values. These are per-component scheduling defaults, not a total host minimum or archive capacity. Include Redis, frontend, crawler/browser workers, replicas, captured data and backups when sizing production.","supportingSources":[{"title":"Backend resource template","url":"https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/backend.yaml"},{"title":"MongoDB resource template","url":"https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/mongo.yaml"}]},"iac":{"artifactRef":"v1.26.6","artifactUrl":"https://github.com/webrecorder/browsertrix/tree/v1.26.6/chart","reviewed":"2026-11-21","scope":"Self-hosted Browsertrix v1.26.6 Helm artifact; production configuration and experimental Ansible scope","source":"https://docs.browsertrix.com/deploy/remote/","status":"documented","summary":"Browsertrix provides an upstream Helm chart and remote-deployment instructions for Kubernetes, including single-machine MicroK8s/k3s configuration, domains/TLS and optional external MongoDB/S3-compatible storage. Ansible cloud playbooks are described as experimental. Pin the chart/application release and configure secrets, persistent storage, backups and exposure; these recipes do not establish HA.","supportingSources":[{"title":"Chart configuration","url":"https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/README.md"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"Browsertrix; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE","status":"documented","summary":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-11-05T00:38:26Z","releaseTag":"v1.26.6","reviewed":"2026-11-19","scope":"Browsertrix upstream application; verify compatibility with the selected package","source":"https://github.com/webrecorder/browsertrix/releases/tag/v1.26.6","status":"documented","summary":"Reviewed upstream v1.26.6 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"reviewed":"2026-11-21","scope":"Self-hosted Browsertrix v1.26.6 platform-user identity; captured-site credentials are excluded","source":"https://github.com/webrecorder/browsertrix/blob/v1.26.6/backend/btrixcloud/auth.py","status":"inconclusive","summary":"Browsertrix v1.26.6 implements application-issued JWTs and password-based login. The reviewed deployment/authentication material does not establish an external SAML/OIDC login path for platform users. Browser profiles used to authenticate to websites being crawled are a separate feature and do not prove Browsertrix account SSO.","supportingSources":[{"title":"Deployment customization","url":"https://docs.browsertrix.com/deploy/customization/"}]}},"id":"browsertrix","infrastructure":["servers"],"infrastructureNotes":"Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.browsertrix.com/deploy/ansible/digitalocean/"],"install":"Kubernetes manifests","installMethods":["kubernetes"],"kind":"product","license":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Browsertrix","notes":"The documented playbook provisions the application rather than only a crawler SDK. Customer operators manage crawl capacity, storage, credentials, retention and upgrades; the hosted Browsertrix service is a separate option.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Browsertrix DigitalOcean Docs","url":"https://docs.browsertrix.com/deploy/ansible/digitalocean/"},{"title":"AGPL-3.0 LICENSE","url":"https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/webrecorder/browsertrix/releases"}],"url":"https://launchinyourcloud.com/directory/browsertrix/","website":"https://webrecorder.net/browsertrix"},{"architecture":"Java/Payara application with PostgreSQL, Solr and local or object data storage","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Upstream AWS EC2 deployment script and instructions","url":"https://guides.dataverse.org/en/6.12.1/developers/deployment.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-13","sources":[{"title":"Reviewed release and corrected Docker-image notice","url":"https://github.com/IQSS/dataverse/releases/tag/v6.12.1"},{"title":"Institutional project and community","url":"https://dataverse.org/about/"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Institutional research-data repository for dataset preservation, metadata, access and citation.","diligence":{"footprint":{"reviewed":"2026-11-21","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","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-14","scope":"Dataverse 6.12.1 installation paths; not every community cloud package","source":"https://guides.dataverse.org/en/6.12.1/installation/prep.html","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-21","scope":"Versioned Dataverse software licence; optional components and services have separate terms","source":"https://github.com/IQSS/dataverse/blob/v6.12.1/LICENSE.md","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-10-08T23:17:53Z","releaseTag":"v6.12.1","reviewed":"2026-11-14","scope":"Upstream IQSS/dataverse release record; commercial editions and deployment packages may differ","source":"https://github.com/IQSS/dataverse/releases/tag/v6.12.1","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Versioned self-hosted repository-user federation","source":"https://guides.dataverse.org/en/6.12.1/installation/oidc.html","status":"documented","summary":"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.","supportingSources":[{"title":"Shibboleth integration","url":"https://guides.dataverse.org/en/6.12.1/installation/shibboleth.html"}]}},"id":"dataverse","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://guides.dataverse.org/en/6.12.1/installation/index.html","https://guides.dataverse.org/en/6.12.1/developers/deployment.html"],"install":"Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release.","installMethods":["package"],"kind":"product","license":"Apache-2.0 application; dependencies and dataset reuse licenses are separate.","licenseModel":"open-source","licenseModelNotes":"The Dataverse application is Apache-2.0. Stored research datasets can use different rights and licenses; component licenses and optional services remain separate.","licenseModelSources":["https://github.com/IQSS/dataverse/blob/develop/LICENSE.md"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Dataverse Self-Hosted","notes":"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.","operations":"Institution operates application and infrastructure, permissions, persistent identifiers, database/files, backups, monitoring and upgrades. External identity, citation and analysis services require configuration.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"Production installation guide for 6.12.1","url":"https://guides.dataverse.org/en/6.12.1/installation/index.html"},{"title":"Production security, identifiers and storage configuration","url":"https://guides.dataverse.org/en/6.12.1/installation/config.html"},{"title":"Repository and collection scope","url":"https://dataverse.org/about/"},{"title":"Upstream AWS EC2 deployment script and instructions","url":"https://guides.dataverse.org/en/6.12.1/developers/deployment.html"},{"title":"Upstream software license","url":"https://github.com/IQSS/dataverse/blob/develop/LICENSE.md"},{"title":"Reviewed release and corrected Docker-image notice","url":"https://github.com/IQSS/dataverse/releases/tag/v6.12.1"}],"url":"https://launchinyourcloud.com/directory/dataverse/","website":"https://dataverse.org/"},{"architecture":"Persistent Java backend and Node frontend services with PostgreSQL, Solr and repository storage","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Johns Hopkins institutional DSpace deployment on AWS","url":"https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-13","sources":[{"title":"Project, governance and institutional community","url":"https://dspace.org/"},{"title":"Current 10.1 releases","url":"https://dspace.org/download/"},{"title":"Johns Hopkins repository deployment","url":"https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Institutional digital repository for scholarly works, datasets and cultural collections.","diligence":{"footprint":{"reviewed":"2026-11-21","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","status":"inconclusive","summary":"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."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/DSpace/DSpace","reviewed":"2026-11-14","scope":"Upstream backend development/test artifacts; not the AWS/JHU production reference","source":"https://github.com/DSpace/DSpace","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-21","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","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-09-14T22:44:38Z","releaseTag":"dspace-10.1","reviewed":"2026-11-14","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","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","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","status":"documented","summary":"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."}},"id":"dspace","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://dspace.org/download/","https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/"],"install":"Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate.","installMethods":["other"],"kind":"product","license":"BSD-3-Clause core; dependencies and optional commercial hosting/support have separate terms.","licenseModel":"open-source","licenseModelNotes":"The DSpace core is BSD-3-Clause. Review backend/frontend dependencies and any paid service-provider agreement separately.","licenseModelSources":["https://github.com/DSpace/DSpace/blob/main/LICENSE"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"DSpace Self-Hosted","notes":"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.","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.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"Current backend/frontend downloads and upgrades","url":"https://dspace.org/download/"},{"title":"DSpace 10 production installation","url":"https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944708/Installing%2BDSpace"},{"title":"Johns Hopkins institutional DSpace deployment on AWS","url":"https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/"},{"title":"Upstream core license","url":"https://github.com/DSpace/DSpace/blob/main/LICENSE"},{"title":"Project, governance and institutional community","url":"https://dspace.org/"}],"url":"https://launchinyourcloud.com/directory/dspace/","website":"https://dspace.org/"},{"architecture":"Fedora Repository application on EC2 with PostgreSQL in RDS.","categories":["archives-collections-management","document-management"],"category":"Archives \u0026 collections management","categoryFit":{"archives-collections-management":"Open-source preservation repository with an AWS Terraform deployment.","document-management":"Open-source preservation repository with an AWS Terraform deployment."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-19","sourceType":"community-template","title":"fcrepo-aws-deployer","url":"https://github.com/fcrepo-exts/fcrepo-aws-deployer","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/fcrepo/fcrepo/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/fcrepo/fcrepo"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source preservation repository with an AWS Terraform deployment.","diligence":{"footprint":{"reviewed":"2026-11-20","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","status":"documented","summary":"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.","supportingSources":[{"title":"Configurable recipe inputs","url":"https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/variables.tf"}]},"iac":{"artifactRef":"master (moving branch); select compatible Fedora, servlet-container and database versions","artifactUrl":"https://github.com/fcrepo-exts/fcrepo-aws-deployer/tree/master","reviewed":"2026-11-20","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","status":"documented","summary":"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.","supportingSources":[{"title":"Upstream runtime packaging","url":"https://github.com/fcrepo/fcrepo/blob/main/README.md"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"Fedora Repository; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/fcrepo/fcrepo/blob/main/LICENSE","status":"documented","summary":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-07-16T08:56:55Z","releaseTag":"fcrepo-6.5.2","reviewed":"2026-11-19","scope":"Fedora Repository upstream application; verify compatibility with the selected package","source":"https://github.com/fcrepo/fcrepo/releases/tag/fcrepo-6.5.2","status":"documented","summary":"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."},"sso":{"reviewed":"2026-11-20","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","status":"inconclusive","summary":"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."}},"id":"fedora-repository","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://github.com/fcrepo-exts/fcrepo-aws-deployer"],"install":"Terraform; Package / binary installer","installMethods":["terraform","package"],"kind":"product","license":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/fcrepo/fcrepo/blob/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Fedora Repository","notes":"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.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"fcrepo-aws-deployer","url":"https://github.com/fcrepo-exts/fcrepo-aws-deployer"},{"title":"Apache-2.0 LICENSE","url":"https://github.com/fcrepo/fcrepo/blob/main/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/fcrepo/fcrepo/releases"}],"url":"https://launchinyourcloud.com/directory/fedora-repository/","website":"https://wiki.lyrasis.org/display/FF/Fedora+Repository+Home"},{"architecture":"Application on the FormKiQ document and workflow platform","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"archives-collections-management":"Archival description, accessions, digital collections and researcher access."},"cloudEvidence":[{"applicableEdition":"FormKiQ platform; solution configuration and entitlement must be agreed separately","clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"FormKiQ commercial AWS installation","url":"https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Connect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.","diligence":{"footprint":{"reviewed":"2026-11-21","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/","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Platform architecture and optional components","url":"https://docs.formkiq.com/docs/platform/overview"},{"title":"Commercial deployment templates","url":"https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq"}]},"iac":{"reviewed":"2026-11-16","scope":"FormKiQ Archives and Collections Management; customer-managed AWS deployment; configured commercial solution, not Core","source":"https://formkiq.com/solutions/archives-collections-management/","status":"documented","summary":"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.","supportingSources":[{"title":"Commercial deployment and customer-specific templates","url":"https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"FormKiQ Archives and Collections Management; customer-managed AWS deployment; configured commercial solution, not Core","source":"https://formkiq.com/solutions/archives-collections-management/","status":"documented","summary":"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.","supportingSources":[{"title":"Edition pricing and separately quoted modules/services","url":"https://formkiq.com/pricing/"}]},"securityControls":{"reviewed":"2026-11-16","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/","status":"documented","summary":"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."},"sso":{"reviewed":"2026-11-21","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/","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Underlying platform architecture","url":"https://docs.formkiq.com/docs/platform/overview"}]}},"id":"formkiq-archives-collections-management","infrastructure":["serverless"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://formkiq.com/solutions/archives-collections-management/","https://docs.formkiq.com/docs/platform/overview"],"install":"Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.","installMethods":["cloudformation"],"kind":"solution","license":"Commercial FormKiQ Advanced or Enterprise; confirm required extensions","licenseModel":"commercial-only","licenseModelNotes":"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.","licenseModelSources":["https://formkiq.com/solutions/","https://formkiq.com/pricing/"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"FormKiQ Archives and Collections Management","notes":"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.","operations":"Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.","parent":"formkiq","publisher":true,"requiresOpenSearch":false,"reviewed":"2026-11-12","sources":[{"title":"Archives and Collections Management solution","url":"https://formkiq.com/solutions/archives-collections-management/"},{"title":"Business solution editions and platform relationship","url":"https://formkiq.com/solutions/"},{"title":"Commercial deployment notes","url":"https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq"},{"title":"Platform infrastructure and optional components","url":"https://docs.formkiq.com/docs/platform/overview"},{"title":"Licensing and edition terms","url":"https://formkiq.com/pricing/"}],"url":"https://launchinyourcloud.com/directory/formkiq-archives-collections-management/","website":"https://formkiq.com/solutions/archives-collections-management/"},{"architecture":"Persistent Python web/worker services with PostgreSQL, search, queue/cache and local or object storage","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-13","sourceType":"institution-deployment","title":"CaltechAUTHORS institutional AWS EC2 deployment","url":"https://github.com/caltechlibrary/caltechauthors","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws"],"communityAcceptance":{"reviewed":"2026-11-13","sources":[{"title":"Institutional governance","url":"https://inveniosoftware.org/governance/"},{"title":"Current release and community","url":"https://inveniosoftware.org/products/rdm/"},{"title":"Named Caltech institutional repository","url":"https://github.com/caltechlibrary/caltechauthors"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Research and institutional repository platform for digital-resource deposit, curation and discovery.","diligence":{"footprint":{"reviewed":"2026-11-21","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","status":"documented","summary":"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."},"iac":{"artifactRef":"repository default branch (moving); select charts compatible with the chosen InvenioRDM release","artifactUrl":"https://github.com/inveniosoftware/helm-invenio","reviewed":"2026-11-21","scope":"Upstream production strategy with explicit reference-template limits","source":"https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-21","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","status":"documented","summary":"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."},"sso":{"reviewed":"2026-11-14","scope":"Institution-operated InvenioRDM; not a guarantee for an unmodified third-party package","source":"https://inveniosoftware.org/products/rdm/","status":"documented","summary":"The project explicitly describes integration with an institution’s SSO. Confirm the chosen authentication integration, user mapping and local customization for the deployed release."}},"id":"inveniordm","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://inveniosoftware.org/products/rdm/","https://github.com/caltechlibrary/caltechauthors"],"install":"Official Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration.","installMethods":["other"],"kind":"product","license":"MIT application code; framework modules, institutional customizations and dependencies retain their own terms.","licenseModel":"open-source","licenseModelNotes":"The invenio-app-rdm application is MIT licensed. Its framework/modules, optional services and institution-specific customizations must be reviewed under their own licenses.","licenseModelSources":["https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"InvenioRDM","notes":"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.","operations":"Institution operates application and workers, identity, search, data services, configuration, backups and upgrades. Cloud resources are separate from the public Zenodo hosted service.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"Current product and release","url":"https://inveniosoftware.org/products/rdm/"},{"title":"Production runtime, persistence and operations","url":"https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md"},{"title":"Institutional cloud-init prerequisites","url":"https://github.com/caltechlibrary/cloud-init-examples/blob/main/invenio-rdm-13-init.yaml"},{"title":"CaltechAUTHORS institutional AWS EC2 deployment","url":"https://github.com/caltechlibrary/caltechauthors"},{"title":"Application license","url":"https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE"},{"title":"Institutional governance","url":"https://inveniosoftware.org/governance/"}],"url":"https://launchinyourcloud.com/directory/inveniordm/","website":"https://inveniosoftware.org/products/rdm/"},{"architecture":"ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state.","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"archives-collections-management":"Open-source digital repository and collections platform with a community DigitalOcean deployment."},"cloudEvidence":[{"clouds":["digitalocean"],"notes":"ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. The named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.","reviewed":"2026-11-19","sourceType":"community-template","title":"Islandora-Devops/sandbox","url":"https://github.com/Islandora-Devops/sandbox","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["digitalocean"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/Islandora-Devops/islandora-starter-site/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/Islandora-Devops/islandora-starter-site"}],"summary":"The reviewed upstream contributor history includes rosiel, adam-vessey, aOelschlager, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source digital repository and collections platform with a community DigitalOcean deployment.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"ISLE Compose host prerequisite, not a complete production/HA capacity estimate","source":"https://islandora.github.io/documentation/installation/docker/docker-prereq/","status":"documented","summary":"The ISLE Docker prerequisites call for at least 8 GB RAM, ideally 16 GB, plus Docker/Compose, Make and Git. This is a host setup prerequisite; database, Fedora, search, media processing, files and production replicas require additional workload and storage planning."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf","reviewed":"2026-11-19","scope":"Islandora (ISLE) deployment example; review the full linked installation instructions","source":"https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf","status":"documented","summary":"The reviewed source supplies deployment configuration for ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. Set organization-specific secrets, networking, storage and compatible image versions before use."},"licensePricing":{"reviewed":"2026-11-19","scope":"Islandora (ISLE); software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE","status":"documented","summary":"GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-06-19T12:26:19Z","releaseTag":"1.11.0","reviewed":"2026-11-19","scope":"Islandora starter-site distribution 1.11.0; Drupal, ISLE and other components have separate versions","source":"https://github.com/Islandora-Devops/islandora-starter-site/releases/tag/1.11.0","status":"documented","summary":"Reviewed upstream 1.11.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"reviewed":"2026-11-21","scope":"Islandora starter-site 1.11.0/Drupal 11 user authentication; internal JWTs and generic Drupal module availability are insufficient","source":"https://islandora.github.io/documentation/user-documentation/jwt-authentication/","status":"inconclusive","summary":"Islandora documents JWTs for communication among Drupal and repository microservices. This is service authentication, not a staff browser-login integration. The reviewed starter-site 1.11.0 dependencies do not establish a configured, compatible Drupal 11 SAML/OIDC module and identity mapping; that user-federation path remains unconfirmed.","supportingSources":[{"title":"Starter-site dependencies","url":"https://github.com/Islandora-Devops/islandora-starter-site/blob/1.11.0/composer.json"}]}},"id":"islandora","infrastructure":["servers"],"infrastructureNotes":"ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://github.com/Islandora-Devops/sandbox"],"install":"Terraform","installMethods":["terraform"],"kind":"product","license":"GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Islandora (ISLE)","notes":"The named-cloud recipe is a community sandbox implementation. Validate persistence, domain configuration, secrets and production recovery separately; its Terraform release is not an Islandora application release.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Islandora-Devops/sandbox","url":"https://github.com/Islandora-Devops/sandbox"},{"title":"main.tf","url":"https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf"},{"title":"GPL-2.0 LICENSE","url":"https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/Islandora/islandora-starter-site/releases"}],"url":"https://launchinyourcloud.com/directory/islandora/","website":"https://sandbox.islandora.ca"},{"architecture":"Persistent PHP application with MySQL, collection files, configuration, themes and extension modules","categories":["archives-collections-management"],"category":"Archives \u0026 collections management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-13","sourceType":"marketplace-offer","title":"Cloudron EC2 AMI and application installation","url":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"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.","reviewed":"2026-11-13","sourceType":"marketplace-offer","title":"Cloudron customer Droplet deployment","url":"https://marketplace.digitalocean.com/apps/cloudron","vendorSupport":"not-assessed"},{"clouds":["linode"],"notes":"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.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Cloudron customer Linode deployment","url":"https://www.linode.com/docs/marketplace-docs/guides/cloudron/","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"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.","reviewed":"2026-11-13","sourceType":"package-platform-documentation","title":"Cloudron named-provider installation and Marketplace availability","url":"https://docs.cloudron.io/installation/","vendorSupport":"not-assessed"},{"clouds":["hostinger"],"notes":"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.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Hostinger customer VPS Cloudron template","url":"https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/","vendorSupport":"not-assessed"},{"clouds":["lumadock"],"notes":"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.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"LumaDock customer VPS Cloudron template","url":"https://lumadock.com/vps-hosting/cloudron","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock"],"communityAcceptance":{"reviewed":"2026-11-13","sources":[{"title":"Institutional deployments","url":"https://omeka.org/s/showcase/"},{"title":"Project stewardship","url":"https://omeka.org/s/"},{"title":"Maintained release","url":"https://github.com/omeka/omeka-s/releases/tag/v4.2.1"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"vps-account","cloud":"hostinger","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"vps-account","cloud":"lumadock","controlPlane":"not-assessed","evidence":[5],"operator":"customer"}],"description":"Digital collections publishing for libraries, archives, museums and research institutions.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Omeka S upstream requirements; no verified whole-host or Cloudron application memory minimum","source":"https://omeka.org/s/docs/user-manual/install/","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Cloudron package documentation","url":"https://docs.cloudron.io/packages/omekas/"}]},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://omeka.org/s/docs/user-manual/install/","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-21","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","status":"documented","summary":"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."},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"Platform AMI; external Cloudron license","id":"prodview-aep3gt5elubci","publisher":"Cloudron UG","url":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci","version":"Cloudron 10.0.5 (platform, not application)"}],"reviewed":"2026-11-14","scope":"Cloudron platform plus separate application package","source":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci","status":"documented","summary":"AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate.","supportingSources":[{"title":"Cloudron application package","url":"https://docs.cloudron.io/packages/omekas/"}]},"release":{"releasePublishedAt":"2026-06-18T17:25:14Z","releaseTag":"v4.2.1","reviewed":"2026-11-14","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","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","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","status":"documented","summary":"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.","supportingSources":[{"title":"Versioned module compatibility declaration","url":"https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/config/module.ini"}]}},"id":"omeka-s","infrastructure":["servers"],"infrastructureNotes":"Persistent PHP application with MySQL, collection files, configuration, themes and extension modules. Cloudron provides a persistent server application, not event-driven application functions.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://docs.cloudron.io/packages/omekas/","https://docs.cloudron.io/installation/"],"install":"Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation.","installMethods":["package","cloudron"],"kind":"product","license":"GPLv3 application; the packaged OIDC module is GPL-3.0-or-later.","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["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"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Omeka S","notes":"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.","operations":"Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"Official application scope and stewardship","url":"https://omeka.org/s/"},{"title":"Installation, requirements and upgrades","url":"https://omeka.org/s/docs/user-manual/install/"},{"title":"Extension compatibility","url":"https://omeka.org/s/docs/user-manual/modules/"},{"title":"Application user roles","url":"https://omeka.org/s/docs/user-manual/admin/users/"},{"title":"Cloudron package operations; identity manual lags current manifest","url":"https://docs.cloudron.io/packages/omekas/"},{"title":"Reviewed upstream release","url":"https://github.com/omeka/omeka-s/releases/tag/v4.2.1"},{"title":"Core GPL license","url":"https://github.com/omeka/omeka-s/blob/v4.2.1/LICENSE"},{"title":"Packaged OIDC module","url":"https://github.com/cloudron-io/OmekaS-OIDC"},{"title":"OIDC 1.2.0 compatibility","url":"https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/config/module.ini"},{"title":"OIDC module license","url":"https://github.com/cloudron-io/OmekaS-OIDC/blob/v1.2.0/composer.json"},{"title":"Institutional collection deployments","url":"https://omeka.org/s/showcase/"},{"title":"Cloudron application packages and persistent data","url":"https://docs.cloudron.io/apps/"},{"title":"Cloudron application updates","url":"https://docs.cloudron.io/updates/"},{"title":"Cloudron database and application-data backups","url":"https://docs.cloudron.io/backups/"},{"title":"Cloudron platform plans","url":"https://www.cloudron.io/pricing.html"},{"title":"Cloudron account and platform terms","url":"https://www.cloudron.io/legal/terms.html"},{"title":"Cloudron account and installation metadata","url":"https://www.cloudron.io/legal/privacy.html"},{"title":"Exact Cloudron application package versions","url":"https://www.cloudron.io/store/index.html"},{"title":"Cloudron EC2 AMI and application installation","url":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci"},{"title":"Cloudron customer Droplet deployment","url":"https://marketplace.digitalocean.com/apps/cloudron"},{"title":"Cloudron customer Linode deployment","url":"https://www.linode.com/docs/marketplace-docs/guides/cloudron/"},{"title":"Cloudron named-provider installation and Marketplace availability","url":"https://docs.cloudron.io/installation/"},{"title":"Hostinger customer VPS Cloudron template","url":"https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/"},{"title":"LumaDock customer VPS Cloudron template","url":"https://lumadock.com/vps-hosting/cloudron"}],"url":"https://launchinyourcloud.com/directory/omeka-s/","website":"https://omeka.org/s/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/categories/archives-collections-management/"}