Omeka S
Digital collections publishing for libraries, archives, museums and research institutions.
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
24 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation.
Runs in
Documented customer environment
Persistent PHP application with MySQL, collection files, configuration, themes and extension modules
- AWS: Customer cloud account
- DigitalOcean: Customer cloud account
- Linode: Customer cloud account
- Vultr: Customer cloud account
- Hostinger: Customer VPS account
- LumaDock: Customer VPS account
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
Servers / containers
Operated by
Your team
Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron EC2 AMI and application installation ↗ · Source checked 2026-11-13
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron customer Droplet deployment ↗ · Source checked 2026-11-13
- Linode: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron customer Linode deployment ↗ · Source checked 2026-11-13
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron named-provider installation and Marketplace availability ↗ · Source checked 2026-11-13
- Hostinger: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Hostinger customer VPS Cloudron template ↗ · Source checked 2026-11-13
- LumaDock: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
LumaDock customer VPS Cloudron template ↗ · Source checked 2026-11-13
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation. |
|---|---|
| Infrastructure | Servers / containers Persistent PHP application with MySQL, collection files, configuration, themes and extension modules. Cloudron provides a persistent server application, not event-driven application functions. |
| Licensing model | Open Source / Open Core 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. |
| License | GPLv3 application; the packaged OIDC module is GPL-3.0-or-later. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 5 documented · 1 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate.
Cloudron platform plus separate application package · Source ↗ · Cloudron application package ↗ · Offer prodview-aep3gt5elubci ↗ — Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Third-party module-maintainer evidence for Omeka S user OIDC, distinct from the upstream core and packaged defaults · Source ↗ · Versioned module compatibility declaration ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
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.
Omeka S upstream requirements; no verified whole-host or Cloudron application memory minimum · Source ↗ · Cloudron package documentation ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Versioned upstream Omeka S core; no packaged-platform or optional-module entitlement inferred · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream omeka/omeka-s release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (6 not researched)
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & 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.
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.
Compare within Archives & collections management
- ArchesOpen-source cultural-heritage inventory and resource-information platform.
- AWS
- ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
- AWS
- ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
- AWS
- Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- AWS
- BrowsertrixOpen-source browser-based web archiving and collection-management application.
- DigitalOcean
- Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
- AWS
- DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
- AWS
- Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
- AWS
Showing 8 of 11 other listings in Archives & collections management. These products address related workflows; read their category-fit notes before comparing scope. See all of Archives & collections management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official application scope and stewardship ↗omeka.org
- Installation, requirements and upgrades ↗omeka.org
- Extension compatibility ↗omeka.org
- Application user roles ↗omeka.org
- Cloudron package operations; identity manual lags current manifest ↗docs.cloudron.io
- Reviewed upstream release ↗github.com
- Core GPL license ↗github.com
- Packaged OIDC module ↗github.com
- OIDC 1.2.0 compatibility ↗github.com
- OIDC module license ↗github.com
- Institutional collection deployments ↗omeka.org
- Cloudron application packages and persistent data ↗docs.cloudron.io
- Cloudron application updates ↗docs.cloudron.io
- Cloudron database and application-data backups ↗docs.cloudron.io
- Cloudron platform plans ↗www.cloudron.io
- Cloudron account and platform terms ↗www.cloudron.io
- Cloudron account and installation metadata ↗www.cloudron.io
- Exact Cloudron application package versions ↗www.cloudron.io
- Cloudron EC2 AMI and application installation ↗aws.amazon.com
- Cloudron customer Droplet deployment ↗marketplace.digitalocean.com
- Cloudron customer Linode deployment ↗www.linode.com
- Cloudron named-provider installation and Marketplace availability ↗docs.cloudron.io
- Hostinger customer VPS Cloudron template ↗www.hostinger.com
- LumaDock customer VPS Cloudron template ↗lumadock.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Cloudron EC2 AMI and application installation ↗ · AWS
Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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 customer Droplet deployment ↗ · DigitalOcean
Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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 customer Linode deployment ↗ · Linode
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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 named-provider installation and Marketplace availability ↗ · Vultr
Package platform documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Hostinger customer VPS Cloudron template ↗ · Hostinger
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- LumaDock customer VPS Cloudron template ↗ · LumaDock
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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 EC2 AMI and application installation ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Institutional deployments ↗omeka.org
- Project stewardship ↗omeka.org
- Maintained release ↗github.com