Archivematica vs Omeka S vs DSpace: Best Self-Hosted Digital Archive Platform 2026

Digital archives are the backbone of institutional memory. Whether you run a university repository, a museum collection, or a government records program, you need a reliable system to ingest, preserve, describe, and provide access to digital objects. Proprietary digital asset management (DAM) systems often cost tens of thousands of dollars per year and lock your data into vendor-specific formats. Self-hosted open-source alternatives give you full control, zero licensing fees, and the flexibility to adapt to any workflow.

In this guide, we compare three leading open-source digital archive platforms: Archivematica, Omeka S, and DSpace. Each serves a different primary use case — preservation processing, public exhibition, and institutional repository, respectively — but all can be self-hosted on your own infrastructure.

For related reading, see our web archiving with ArchiveBox guide and document management with Paperless-ngx.

Why Self-Host a Digital Archive Platform?

Digital preservation is fundamentally about maintaining the authenticity, integrity, and accessibility of digital objects over time. When you rely on a cloud-hosted or proprietary system, you face several risks:

• Vendor lock-in: Exporting your entire collection — including metadata, fixity checksums, and derivative files — from a commercial DAM is often difficult or impossible without data loss.
• Long-term cost: SaaS pricing models scale with storage and user count, making large collections prohibitively expensive over decades.
• Format obsolescence: Open-source platforms let you run your own format migration and normalization pipelines without waiting on vendor updates.
• Compliance and sovereignty: Government agencies, libraries, and archives often have legal mandates to keep records on-premises or within specific jurisdictions.
• Customization: Open-source systems can be extended with custom plugins, metadata schemas, and ingestion workflows that proprietary vendors will never build.

Self-hosting gives you direct control over the preservation pipeline, from ingest AIP (Archival Information Package) creation to long-term storage and access dissemination.

Archivematica: Standards-Based Digital Preservation

GitHub: artefactual/archivematica · Stars: 498 · Updated: April 2026 · License: AGPL-3.0 · Language: Python

Archivematica is the gold standard for open-source digital preservation processing. It implements the OAIS (Open Archival Information System) reference model and produces AIPs that conform to international preservation standards. Developed by Artefactual Systems, it is widely used by national archives, university libraries, and cultural heritage institutions worldwide.

Core Capabilities

• Automated normalization: Converts files to preservation-friendly formats (e.g., TIFF for images, WAV for audio, PDF/A for documents) during ingest.
• Virus checking and validation: Scans incoming transfers for malware and validates file formats against PRONOM signatures.
• Metadata extraction: Automatically extracts technical, structural, and descriptive metadata using tools like MediaInfo, ExifTool, and FITS.
• BagIt packaging: Wraps processed content in BagIt bags with manifest checksums for integrity verification.
• Archival Storage: Stores AIPs in configurable storage locations (local disk, NFS, S3-compatible, Archivematica Storage Service).
• Microservice architecture: Each processing step is a configurable microservice that can be enabled, disabled, or reordered.
• Dashboard UI: Web-based interface for monitoring processing queues, reviewing normalization results, and managing transfers.

Docker Deployment

Archivematica ships with a full Docker Compose setup in its hack/ directory. It requires MySQL, Elasticsearch, and multiple service containers (MCP clients, Dashboard, Storage Service):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

name: am

volumes:
  mysql_data:
  elasticsearch_data:
  archivematica_storage_service_staging_data:

services:
  mysql:
    image: mysql:8.0
    environment:
      MYSQL_ROOT_PASSWORD: root_password
      MYSQL_DATABASE: MCP
    volumes:
      - mysql_data:/var/lib/mysql
    command: --default-authentication-plugin=mysql_native_password

  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.17.0
    environment:
      - discovery.type=single-node
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    volumes:
      - elasticsearch_data:/usr/share/elasticsearch/data

  archivematica-mcp-client:
    image: artefactual/archivematica-mcp-client:stable-1.15
    depends_on:
      - mysql
      - elasticsearch
    environment:
      - DB_HOST=mysql
      - DB_USER=root
      - DB_PASSWORD=root_password
      - ELASTICSEARCH_HOST=elasticsearch
      - ELASTICSEARCH_PORT=9200
    volumes:
      - ./sharedDirectory:/var/archivematica/sharedDirectory

  archivematica-dashboard:
    image: artefactual/archivematica-dashboard:stable-1.15
    depends_on:
      - mysql
      - archivematica-mcp-client
    ports:
      - "8000:8000"
    environment:
      - DB_HOST=mysql
      - DB_USER=root
      - DB_PASSWORD=root_password
    volumes:
      - ./sharedDirectory:/var/archivematica/sharedDirectory

  archivematica-storage-service:
    image: artefactual/archivematica-storage-service:stable-1.15
    ports:
      - "8001:8000"
    depends_on:
      - mysql
    environment:
      - DB_HOST=mysql
      - DB_USER=root
      - DB_PASSWORD=root_password
    volumes:
      - archivematica_storage_service_staging_data:/var/archivematica/storage_service/staging

Deploy with:

1
2
3

git clone https://github.com/artefactual/archivematica.git
cd archivematica/hack
docker compose up -d

The Dashboard will be available at http://localhost:8000 and the Storage Service at http://localhost:8001. Default credentials are admin:demo1234.

Omeka S: Web Publishing for Cultural Collections

GitHub: omeka/omeka-s · Stars: 480 · Updated: April 2026 · License: GPL-3.0 · Language: PHP

Omeka S, developed by the Corporation for Digital Scholarship at George Mason University, is designed for exhibiting digital collections online. It powers web galleries, museum exhibitions, and library showcases where public presentation and rich metadata are the primary goals. Unlike Archivematica, Omeka S focuses on access and display rather than preservation processing.

Core Capabilities

• Linked Open Data (LOD): Native support for IIIF, BIBFRAME, and linked data vocabularies. Every resource gets a stable URI.
• Multi-site architecture: Run multiple public-facing sites from a single Omeka S installation, each with its own theme, items, and collections.
• Media handling: Supports images, audio, video, PDFs, 3D models, and embeds. Generates thumbnails and derivatives automatically.
• Metadata flexibility: Uses Dublin Core as the base schema but supports custom metadata templates and RDF vocabularies.
• Module ecosystem: Over 50 community modules add features like bulk import, geolocation, IIIF integration, and advanced search.
• Theme system: Customizable public themes with responsive design for displaying collections on any device.
• API-first: Full REST API for programmatic access to items, media, and collections.

Docker Deployment

Omeka S is a PHP application that runs on Apache/Nginx with MySQL/MariaDB. Here is a production-ready Docker Compose configuration:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

services:
  db:
    image: mariadb:11
    environment:
      MYSQL_ROOT_PASSWORD: omeka_root_pass
      MYSQL_DATABASE: omeka_s
      MYSQL_USER: omeka
      MYSQL_PASSWORD: omeka_db_pass
    volumes:
      - db_data:/var/lib/mariadb
    healthcheck:
      test: ["CMD", "mariadb-admin", "ping", "-h", "localhost"]
      interval: 10s
      timeout: 5s
      retries: 5

  omeka:
    image: omeka/omeka-s:latest
    ports:
      - "8080:80"
    depends_on:
      db:
        condition: service_healthy
    environment:
      OMEKA_DB_HOST: db
      OMEKA_DB_NAME: omeka_s
      OMEKA_DB_USER: omeka
      OMEKA_DB_PASSWORD: omeka_db_pass
      OMEKA_DB_PREFIX: omeka_
    volumes:
      - omeka_files:/var/www/html/files
      - omeka_themes:/var/www/html/themes
      - omeka_modules:/var/www/html/modules
      - ./logs:/var/www/html/logs

volumes:
  db_data:
  omeka_files:
  omeka_themes:
  omeka_modules:

Deploy with:

1
2
3

mkdir -p omeka-s && cd omeka-s
# Create the docker-compose.yml file above
docker compose up -d

Visit http://localhost:8080 to complete the installation wizard. You will need to create an admin account and configure the site’s base URL.

DSpace: Institutional Repository Platform

GitHub: DSpace/DSpace · Stars: 1,059 · Updated: April 2026 · License: BSD-3-Clause · Language: Java

DSpace is the most widely deployed open-source institutional repository software in the world. It powers repositories for over 3,000 institutions including MIT, Harvard, Cornell, and countless universities globally. DSpace is designed for managing and providing open access to scholarly output — research papers, theses, datasets, conference proceedings, and learning objects.

Core Capabilities

• Submission workflow: Configurable multi-step submission process with review and approval stages.
• Access control: Fine-grained permissions at the community, collection, and item level. Embargo support for time-delayed access.
• OAI-PMH harvesting: Full OAI-PMH 2.0 compliance for metadata harvesting by aggregators and search engines.
• Solr-based discovery: Apache Solr powers faceted search, filtering, and full-text search across the repository.
• REST API: Modern REST API (v7+) for programmatic access, integrations, and headless frontend development.
• Statistics: Built-in usage statistics with Google Analytics integration.
• SWORD protocol: Supports SWORD v2 for deposit from external systems (reference managers, journal platforms).
• Angular UI: Modern Angular-based frontend with responsive design and accessibility support.

Docker Deployment

DSpace provides an official Docker Compose configuration that includes the backend, Angular frontend, PostgreSQL database, and Solr search engine:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

networks:
  dspacenet:
    ipam:
      config:
        - subnet: 172.23.0.0/16

services:
  dspacedb:
    image: postgres:17
    environment:
      POSTGRES_USER: dspace
      POSTGRES_PASSWORD: dspace
      POSTGRES_DB: dspace
    networks:
      - dspacenet
    volumes:
      - db_data:/var/lib/postgresql/data

  dspacesolr:
    image: solr:9
    networks:
      - dspacenet
    volumes:
      - solr_data:/var/solr

  dspace:
    image: dspace/dspace:latest
    environment:
      db__P__url: jdbc:postgresql://dspacedb:5432/dspace
      solr__P__server: http://dspacesolr:8983/solr
      dspace__P__server__P__url: http://localhost:8080/server
      dspace__P__ui__P__url: http://localhost:4000
    ports:
      - "8080:8080"
      - "8000:8000"
    depends_on:
      - dspacedb
      - dspacesolr
    networks:
      - dspacenet
    volumes:
      - dspace_data:/dspace/assetstore

  dspace-angular:
    image: dspace/dspace-angular:latest
    environment:
      DSPACE_UI_URL: http://localhost:4000
      DSPACE_REST_URL: http://localhost:8080/server
    ports:
      - "4000:4000"
    depends_on:
      - dspace
    networks:
      - dspacenet

volumes:
  db_data:
  solr_data:
  dspace_data:

Deploy with:

1
2
3

git clone https://github.com/DSpace/DSpace.git
cd DSpace
docker compose up -d

The REST API will be at http://localhost:8080/server and the Angular frontend at http://localhost:4000. Initial admin credentials need to be created via the DSpace command-line tools.

Comparison Table

Choosing the Right Platform

The choice between these three depends entirely on your primary use case:

Choose Archivematica if: You need a preservation processing system that implements OAIS standards, performs automated format normalization, generates fixity checksums, and produces standards-compliant AIPs. It is the right tool for archivists who process incoming digital transfers and need to ensure long-term accessibility.

Choose Omeka S if: Your priority is presenting digital collections to the public through rich, themed web exhibits. It excels at cultural heritage institutions that need to showcase items with compelling narratives, geographic mapping, and linked data connections.

Choose DSpace if: You operate an institutional repository that needs to accept, manage, and provide open access to scholarly output. Its submission workflows, access controls, OAI-PMH harvesting, and integration with academic systems make it the standard choice for universities.

Many institutions actually run multiple systems: Archivematica for preservation processing, Omeka S for public exhibitions of selected collections, and DSpace for the institutional repository. The Storage Service API in Archivematica can even push AIPs to external repositories.

Self-Hosting Architecture Best Practices

Regardless of which platform you choose, follow these infrastructure recommendations:

Reverse Proxy with TLS

Place a reverse proxy in front of your archive platform:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

services:
  nginx-proxy:
    image: nginx:alpine
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
      - ./certs:/etc/nginx/certs:ro
    depends_on:
      - archivematica-dashboard  # or omeka / dspace

  # Add your chosen platform below...

Configure automatic TLS certificate renewal with Certbot or use the docker-letsencrypt-nginx-proxy-companion container.

Storage Architecture

Digital archives require reliable, redundant storage:

• Use ZFS or Btrfs for the underlying filesystem — both provide checksumming and snapshot capabilities critical for data integrity.
• Implement the 3-2-1 backup rule: 3 copies of data, on 2 different media, with 1 offsite copy.
• Monitor disk health with SMART monitoring and automated alerts for failing drives.
• Use separate volumes for application data, database files, and asset storage to simplify backup and migration.

Monitoring

Set up health checks for critical services:

1
2
3
4
5
6
7
8

# Monitor PostgreSQL/MySQL
docker exec dspacedb pg_isready -U dspace

# Monitor Solr
curl -s http://localhost:8983/solr/admin/cores?action=STATUS

# Monitor Elasticsearch
curl -s http://localhost:9200/_cluster/health

For related infrastructure monitoring, check our guide to self-hosted monitoring tools.

FAQ

Which digital archive platform is best for a small museum?

Omeka S is the strongest choice for museums and galleries. Its multi-site architecture lets you run separate exhibitions from one installation, the theme system provides professional public presentation, and the IIIF support enables deep zoom viewing of high-resolution images. The lower resource requirements (2 GB RAM minimum) also make it feasible to run on modest hardware.

Can Archivematica and DSpace work together?

Yes. A common workflow is to use Archivematica for the preservation processing pipeline — ingesting raw transfers, normalizing files, generating AIPs — and then deposit the Dissemination Information Packages (DIPs) into DSpace for public access and discovery. The Archivematica Storage Service can be configured to push DIPs to DSpace via its REST API.

How much storage do I need for a digital archive?

Storage requirements depend on your collection size and preservation strategy. Archivematica typically triples storage needs: one copy of the original transfer, one normalized preservation copy, and one access copy. For a 1 TB incoming transfer, budget 3 TB of usable storage. Use deduplication where possible and compress access derivatives.

Does DSpace support research data management?

DSpace 7.x includes enhanced support for research datasets with schema.org metadata, DOI integration via DataCite or EZID, and configurable item types for datasets. It can integrate with external data repositories and supports large file uploads via the REST API. For specialized data repository needs, consider InvenioRDM as an alternative.

Is there a way to migrate content between these platforms?

Migration paths exist but require planning. Omeka S and DSpace both support CSV bulk import, so you can export metadata from one system and re-import it into the other. Binary files can be transferred via filesystem copy. Archivematica AIPs can be unpacked and their contents re-ingested into any platform. Always test migration with a representative sample before committing to a full transfer.

What is the minimum server specification for running these platforms?

• Archivematica: 4 GB RAM, 2 CPU cores, 50 GB disk (minimum). Elasticsearch alone requires 2 GB.
• Omeka S: 2 GB RAM, 1 CPU core, 20 GB disk. Scales well with more RAM for image processing.
• DSpace: 8 GB RAM, 2 CPU cores, 50 GB disk. Java and Solr are resource-intensive. For production repositories, 16 GB RAM is recommended.