Skip to main content

Fully Managed
Omeka S
as a Service

Deploy Omeka S as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Omeka S is a Linked Open Data publishing platform for libraries, archives, museums, and digital humanities teams — multi-site, IIIF-ready, RDF-native. It is the natural home for collections that need to publish as discoverable open data, not pile up behind a paywalled SaaS. We run the infrastructure underneath so curators and metadata staff can focus on the items.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Omeka S

Omeka S

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Omeka S Preview Image

ABOUT THE SOFTWARE

What is Omeka S

Omeka S is a Linked Open Data publishing platform built for the institutions that put collections online — universities, libraries, archives, and museums. A single install hosts many independently curated sites that share one pool of items, media, and metadata, all expressed as RDF with dereferenceable URIs.

Omeka S is developed by Digital Scholar — a 501(c)(3) nonprofit with four full-time core developers — and originated at George Mason University's Roy Rosenzweig Center for History and New Media. Combined with the older Omeka Classic, the project has been downloaded more than five hundred thousand times.

Production sites run on PHP with MySQL or MariaDB. The architecture is modular: a small core handles items, item sets, media, multi-site, vocabularies, and the JSON-LD API. IIIF tile serving, EAD finding aids, RDF datatypes, mapping, OAI-PMH harvest, and bulk import each ship as separately maintained modules. Notable deployments include the University of Utah's J. Willard Marriott Library, the Ghent Centre for Digital Humanities, the Saltaire Collection, and the National Library of Wales' crowdsourced transcription portal.

FEATURES

What Omeka S does

Omeka S is built around the things that actually matter to GLAM publishing: rich descriptive metadata, dereferenceable URIs for every resource, IIIF-compatible image delivery, multi-site reuse of one shared item pool, and an open REST API that serializes to JSON-LD, RDF/XML, Turtle, and N-Triples.

Multi-site architecture

One install, many public sites sharing one pool of items, media, and metadata. Items can live in zero, one, or many sites; site-level filters control visibility and theming.

IIIF Presentation and Image API

With Cantaloupe behind it, Omeka S serves IIIF Image API v3 with deep zoom, region cropping, and rotation. Mirador 3 and Universal Viewer drop in directly.

TEXT TEXT TEXT TEXT

The OAI-PMH Repository module exposes your items for harvest by DPLA, Europeana, or other aggregators. Dublin Core is the baseline; MODS and qualified Dublin Core are optional output formats.

Bulk import and editing

CSV Import covers the simple path. BulkImport adds multi-value separators, file sideloading, update-by-identifier, and resumable jobs for ingests of tens of thousands of records.

Linked Open Data and RDF

Every resource has a dereferenceable URI. Dublin Core Terms, FOAF, and the Bibliographic Ontology in core. Custom Vocab and Custom Ontology import Getty AAT, Schema.org, CIDOC-CRM, or any RDF vocabulary.

EAD finding aids

The EAD module imports Encoded Archival Description 2002 finding aids and renders the collection / series / sub-series tree, mapped through Ead2DCterms to all fifty-five DCMI Metadata Terms.

Faceted search at scale

Bundled MySQL fulltext for small collections. AdvancedSearch and SearchSolr add Apache Solr 9.x with faceting, relevance ranking, and sub-second response on indexes of a million items and more.

ArchivesSpace integration

The official ArchivesSpace Connector module, released April 2026, imports Archival Objects from your ArchivesSpace API as nested item sets, preserving collection / series / sub-series structure.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Omeka S

Three things converged in 2025 and 2026 to push institutions toward managed Omeka S. A March 2025 executive order destabilized the IMLS grant funding that paid for proprietary digital-collections subscriptions. The 2023 ransomware attack on a major proprietary museum-platform vendor made boards skittish about closed-source lock-in. And the long-awaited ArchivesSpace Connector module finally landed in April 2026.

Running Omeka S in production is a discipline, not an install step. The core is well-engineered, but a working stack also wants Cantaloupe configured for IIIF, Solr indexed for fast item search, OAI-PMH exposed for DPLA or Europeana harvesting, OPcache tuned for module-heavy request patterns, PHP memory raised to 1024M for derivative jobs and CSV imports, and a cron worker running application/data/scripts/perform-jobs.php for background tasks. None of that ships in the upstream zip.

The hardest part is upgrades. The Omeka S installer only touches core code — it does not touch modules or themes. Most production-grade modules (IIIF Server, EAD, AdvancedSearch, Mapping, Timeline, BulkImport) are maintained by an independent developer whose release cadence does not align with core releases. The result is a recurring window after every major Omeka S release where institutional installs cannot upgrade without breaking something critical. Public forum threads and managed-host knowledge bases converge on this as the single most common cause of failed Omeka S upgrades.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Omeka S on DANIAN

Three patterns we see most often: the university library running multiple curated exhibits on one shared item pool, the digital humanities project publishing Linked Open Data with maps and timelines, and the volunteer-run community archive on a small budget. The configuration choices below come from production installs.

UNIVERSITY LIBRARY · DIGITAL SCHOLARSHIP

Eleven curated exhibits on one shared item pool

A mountain-west research library runs eleven public Omeka S sites — including a digital pandemic archive, a Japanese-American memorial collection, and a regional religious history project — from a single install in a US region. Universal Viewer for IIIF, custom institutional theme, Dublin Core plus MODS metadata. Editor team of six. Solr-backed search across the full pool.

DIGITAL HUMANITIES RESEARCH · MADRID

Twenty historical maps, four thousand places, ten thousand cultural objects

A Spanish university digital humanities centre publishes a multilingual interactive atlas combining twenty historical maps of one city, four thousand places with timestamped history, and ten thousand cultural heritage objects pulled via IIIF from partner GLAM institutions. Runs in a Europe-Spain region. Modules: Custom Ontology, Geometry datatype, IIIF Server, Value Suggest. Four-researcher team.

Community archive · UNESCO heritage site 

Six thousand items, volunteer-run, OAI-PMH-harvested

A UK community archive for a UNESCO World Heritage industrial site runs six thousand documents, photographs, maps, and objects on a volunteer cataloguing model. Modules: CSV Import, Faceted Browse, OAI-PMH Repository, Octopus Viewer for IIIF, Restricted Sites for in-progress collections. Two part-time paid staff, volunteer editors. Runs in a UK region.

COMPARISON

Four ways to run Omeka S

Most institutions evaluate three or four paths before settling on managed Omeka S. The proprietary library and archives platforms — ContentDM (OCLC) and Preservica — are the closest commercial peers. The self-host path is real but undercounts operator time. The fourth path is us. The math is below.

 PATHSTARTING (1 SITE, ≤5K ITEMS)GROWING (5 SITES, ≤25K ITEMS)AT SCALE (10 SITES, ≤100K ITEMS, IIIF)
ContentDM (OCLC) — proprietary SaaS
~$3,372/yr ongoing+ $10,000 one-time tier upgrade+ $30,000 one-time tier upgrade
$24/mo production-class VPS, self-managed
~€100–280/mo effective (infra + ops time at sysadmin rates)~€150–400/mo (more time + DB tuning)~€300–600+/mo (Solr, Cantaloupe, IIIF traffic, on-call)
Synology DS923+ NAS at home
~€210–450/mo (hardware amortised + electricity + business internet + off-site backup)Not viable at this scale (no redundancy)Not viable at this scale (no redundancy)
DANIAN Managed Omeka S€9/month flat€9/month flat€9/month flat

Year-1 ContentDM total at this tier is materially higher (~$11,782 in a published Miami University training example based on OCLC's price list); current 2026 quotes are typically 1.5–2× the legacy figure. For archives-focused workloads the equivalent comparable proprietary spend is Preservica Starter Plus at ~$2,388/yr (25 GB tier); multi-site and IIIF require Preservica Professional, which is quote-only.

Two notes on the table. First, the time costs on the self-host row are real — public forum threads document that almost all upgrade failures come from un-tested module compatibility, which is on you when you self-host. Second, Omeka.net — the official Digital Scholar SaaS — does not host Omeka S. It runs Omeka Classic only. Institutions wanting multi-site, IIIF, RDF/LOD, or the ArchivesSpace Connector have no first-party SaaS option, which is why a managed Omeka S layer is genuinely useful rather than just price-competitive.

BY INDUSTRY

Omeka S for specific industries

Different institutional types put different demands on Omeka S. Academic libraries care about ArchivesSpace integration and OAI-PMH harvest. Archives need EAD finding aids and PREMIS preservation metadata. Museums prioritise IIIF tile serving and CIDOC-CRM. Digital humanities projects want clean Linked Open Data publication. Here is what we tune for each.

Standard: Dublin Core Terms (DCMI) and MODS for descriptive metadata, with OAI-PMH 2.0 for harvest by DPLA and Europeana.

DANIAN configuration: pre-installed AdvancedSearch and SearchSolr modules with Apache Solr 9.x indexing; the ArchivesSpace Connector module (released by Digital Scholar on 28 April 2026) pre-installed and configured to your institutional ArchivesSpace API endpoint.

Workflow: a librarian publishes a finding aid in ArchivesSpace, the Connector imports collection / series / sub-series hierarchy into Omeka S as nested item sets, digital objects attach via CSV Import or IIIF manifest, Solr indexes for sub-second public search, and the OAI-PMH endpoint exposes records for DPLA harvest nightly.

Quantifiable detail: the ArchivesSpace Connector was developed in partnership with the University of Missouri–Kansas City; harvest latency from ArchivesSpace edits to Omeka S is cron-configurable, typically nightly.

Standard: Encoded Archival Description (EAD 2002) for finding aids, ISAD(G) for hierarchical description, PREMIS for preservation metadata.

DANIAN configuration: pre-installed Daniel-KM EAD, Generic, and BulkImport modules with the Ead2DCterms XSLT2 processor; OAI-PMH Repository configured for DPLA harvest; nightly mysqldump plus rsync of the files directory to off-site cold storage.

Workflow: the archivist exports EAD 2002 XML from a local description tool, uploads through the EAD module, the finding aid tree renders via the ead view helper, items link via Dublin Core isPartOf and hasPart, public discovery happens through Faceted Browse and OAI-PMH.

Quantifiable detail: Ead2DCterms maps the EAD 2002 schema to all fifty-five DCMI Metadata Terms — substantially more descriptive granularity than legacy EAD-to-DC crosswalks that mapped only the basic fifteen Dublin Core elements.

Standard: CIDOC-CRM for object documentation, VRA Core 4 for visual resources, IIIF Presentation 3.0 for image delivery.

DANIAN configuration: Cantaloupe 5.x pre-installed (Java 17, 2 GB heap, reverse-proxied on /iiif), IiifServer and ImageServer modules pre-configured, PHP memory_limit raised to 1024M for derivative generation.

Workflow: a registrar uploads a TIFF master, ImageServer auto-tiles to pyramid TIFF or JP2, the IIIF Presentation manifest is auto-generated, and the object renders in Mirador 3 or Universal Viewer with deep zoom, rotation, and region cropping; multilingual values per locale.

Quantifiable detail: Cantaloupe supports IIIF Image API v3 from version 5 onward; a typical install with Java 17 and 2 GB heap serves more than ten thousand tile requests per hour on a four-core production VPS. The December 2023 ransomware on a major proprietary museum-platform vendor — affecting more than two hundred and sixty institutions — has made self-controllable IIIF stacks a board-level priority.

Standard: RDF and Linked Open Data with custom vocabularies, the W3C Web Annotation Data Model, Schema.org for SEO and discovery.

DANIAN configuration: pre-installed Custom Ontology, Custom Vocab, Data Type RDF, Data Type Geometry, and Value Suggest modules; SPARQL-friendly URI patterns via the Clean URL module; Mapping, Timeline, and CSV Import modules pre-installed for typical project mode.

Workflow: the principal investigator imports a controlled vocabulary (FOAF, Getty AAT, Schema.org), researchers describe items with Resource Templates mixing Dublin Core and custom ontology, data exports as JSON-LD, RDF/XML, Turtle, or N-Triples via the REST API, and external SPARQL endpoints or visualization tools consume it.

Quantifiable detail: the Omeka S REST API has serialized to RDF/XML, N3, Turtle, and N-Triples since v4.1.0 (April 2024) — every resource has a dereferenceable URI for genuine Linked Open Data publication.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

CSV Import (Digital Scholar) handles the simple cases. For multi-value separators, file sideloading, update-by-identifier, or resumable jobs of tens of thousands of records, we install BulkImport. Both run as background jobs against a cron worker we set up with max_execution_time = 0 on the CLI.
Natively. JSON-LD is the default API format. Every item, item set, and media has a dereferenceable URI. Dublin Core Terms, FOAF, and the Bibliographic Ontology ship in core; Custom Vocab and Custom Ontology let you import Getty AAT, Schema.org, CIDOC-CRM, or any RDF vocabulary. As of v4.1.0 the REST API also serializes to RDF/XML, Turtle, and N-Triples.
Up to about fifty thousand items, the bundled MySQL fulltext search is fine. Beyond that we install AdvancedSearch and SearchSolr with Apache Solr 9.x. We reindex via the background worker after each import. Solr handles a million-item index with faceting, relevance ranking, and sub-second response.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Omeka S for 7 days

No card. Cancel from the dashboard.