
# Archives & collections management on DigitalOcean

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

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/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: DigitalOcean team/account and project
- Provider group: cloud-infrastructure
- Provider classification: Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Source: https://docs.digitalocean.com/products/droplets/how-to/create/ (checked 2026-11-20).
- Network: VPC and Cloud Firewalls; review public endpoints
- Identity and access: Team roles, scoped API tokens and SSH keys
- Installation guidance: Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
- Guidance source: https://docs.digitalocean.com/products/droplets/how-to/create/
- Guidance reviewed: 2026-11-12


### Private networking

DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls.
Source: https://docs.digitalocean.com/products/networking/vpc/ (reviewed 2026-11-14).

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

3 listings.


## Browsertrix

Open-source browser-based web archiving and collection-management application.

- Listing: https://launchinyourcloud.com/directory/browsertrix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- 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: Kubernetes manifests
- Architecture: Browsertrix Kubernetes services, crawl workers and object storage deployed through the DigitalOcean Ansible playbook.
- 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://webrecorder.net/browsertrix
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

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

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.


### Category fit

- legacy-system-archive-access: Open-source browser-based web archiving and collection-management application.

- archives-collections-management: Open-source browser-based web archiving and collection-management application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.browsertrix.com/deploy/ansible/digitalocean/ (checked 2026-11-19). 


### Cloud deployment evidence

- Browsertrix DigitalOcean Docs (digitalocean): https://docs.browsertrix.com/deploy/ansible/digitalocean/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

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.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/webrecorder/browsertrix/graphs/contributors

- Upstream project: https://github.com/webrecorder/browsertrix

### Sources

- Browsertrix DigitalOcean Docs: https://docs.browsertrix.com/deploy/ansible/digitalocean/

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE

- GitHub Releases: https://github.com/webrecorder/browsertrix/releases

### Licensing sources

- https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE

### Infrastructure sources

- https://docs.browsertrix.com/deploy/ansible/digitalocean/


### 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. 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. 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 (reviewed 2026-11-21). Supporting source: Deployment customization — https://docs.browsertrix.com/deploy/customization/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Self-hosted Browsertrix v1.26.6 Helm artifact; production configuration and experimental Ansible scope. Source: https://docs.browsertrix.com/deploy/remote/ (reviewed 2026-11-21). Deployment artifact: https://github.com/webrecorder/browsertrix/tree/v1.26.6/chart. Artifact reference: v1.26.6. Supporting source: Chart configuration — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/README.md.

- Minimum footprint / sizing: Documented. 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. 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 (reviewed 2026-11-21). Supporting source: Backend resource template — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/backend.yaml. Supporting source: MongoDB resource template — https://github.com/webrecorder/browsertrix/blob/v1.26.6/chart/templates/mongo.yaml.

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Browsertrix; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/webrecorder/browsertrix/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Islandora (ISLE)

Open-source digital repository and collections platform with a community DigitalOcean deployment.

- Listing: https://launchinyourcloud.com/directory/islandora/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: ISLE application containers on a Terraform-provisioned DigitalOcean host with Spaces-backed infrastructure state.
- 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://sandbox.islandora.ca
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

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

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.


### Category fit

- archives-collections-management: Open-source digital repository and collections platform with a community DigitalOcean deployment.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Islandora-Devops/sandbox (checked 2026-11-19). 


### Cloud deployment evidence

- Islandora-Devops/sandbox (digitalocean): https://github.com/Islandora-Devops/sandbox
  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.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

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.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/Islandora-Devops/islandora-starter-site/graphs/contributors

- Upstream project: https://github.com/Islandora-Devops/islandora-starter-site

### Sources

- Islandora-Devops/sandbox: https://github.com/Islandora-Devops/sandbox

- main.tf: https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf

- GPL-2.0 LICENSE: https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE

- GitHub Releases: https://github.com/Islandora/islandora-starter-site/releases

### Licensing sources

- https://github.com/Islandora/islandora-starter-site/blob/main/LICENSE

### Infrastructure sources

- https://github.com/Islandora-Devops/sandbox


### 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. 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. 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/ (reviewed 2026-11-21). Supporting source: Starter-site dependencies — https://github.com/Islandora-Devops/islandora-starter-site/blob/1.11.0/composer.json.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Islandora (ISLE) deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/Islandora-Devops/sandbox/main/main.tf. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. 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. Scope: ISLE Compose host prerequisite, not a complete production/HA capacity estimate. Source: https://islandora.github.io/documentation/installation/docker/docker-prereq/ (reviewed 2026-11-21).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. 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 (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. 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 (reviewed 2026-11-19).







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






