PastPerfect Online

Best Self-hosted Alternatives to PastPerfect Online

A curated collection of the 4 best self hosted alternatives to PastPerfect Online.

Cloud collections-management and online catalog service for museums and archives. Manages object records, accessioning, catalog metadata, images, loans and provenance, and publishes searchable public collection websites and online catalogs.

Alternatives List

#1
Omeka

Omeka

Omeka is a PHP-based open-source web publishing platform for managing, preserving and presenting metadata-rich digital collections and media-rich online exhibits.

Omeka screenshot

Omeka is an open-source, PHP-based web publishing platform for managing, publishing, and exhibiting metadata-rich digital collections. It ships in two primary distributions — Omeka Classic for individual projects and educators, and Omeka S for multi-site and institutional deployments — and is extensible via themes, plugins (Classic) and modules (S).

Key Features

  • Core support for structured metadata (Dublin Core and custom mappings) and item/collection (Classic) or item/item set/resource templates (S).
  • Extensible architecture: installable plugins (Classic) and modules (S) plus custom themes to change site presentation and behavior.
  • RESTful API endpoints for programmatic access and integrations; support for JSON-based services and interoperability features.
  • File storage adapters including local filesystem and S3-compatible storage, plus support for image derivatives and thumbnailing via GD or ImageMagick.
  • User roles and permissions for administrators, contributors, and public access; site-building tools in Omeka S for multi-site resource sharing.
  • Wide third-party ecosystem: modules for IIIF/Universal Viewer, CSV import/export, SPARQL and cloud storage adapters.

Use Cases

  • Museums, libraries, and archives publishing curated digital exhibits and searchable collections.
  • Academic and digital humanities projects for teaching, student projects, and research-focused collections.
  • Institutions running multiple branded sites that share centralized resources and vocabularies (Omeka S).

Limitations and Considerations

  • Feature sets and plugin/module ecosystems differ between Omeka Classic and Omeka S; migrating or mixing distributions requires planning and testing for compatibility.
  • Some advanced modules and background jobs require additional server tools (PHP-CLI, ImageMagick, poppler-utils) and specific PHP/database versions; administrators must meet system requirements and manage updates accordingly.

Omeka is well-suited for organizations that need a metadata-first, extensible platform for digital collections and exhibits. It emphasizes interoperability and an active community ecosystem while requiring standard web hosting administration to deploy and maintain.

526stars
210forks
View Details
#2
Omeka S

Omeka S

Omeka S is a modular PHP CMS for cultural heritage institutions to publish exhibits, manage digital collections, and share metadata across sites.

Omeka S screenshot

Omeka S is a modular PHP-based web publication system designed for museums, galleries, libraries, archives, and other cultural heritage institutions. It lets organizations create independently curated exhibits that draw from a shared pool of items, media, and metadata across a local network of sites.

Key Features

  • Modular architecture with cores, modules, and themes to extend functionality and presentation
  • Centralized item and media repository usable by multiple exhibits/sites with shared metadata management
  • RDF/linked-data support and metadata modeling for controlled vocabularies and semantic interoperability
  • Built-in exhibit and resource management features tailored for collections and archives
  • Support for common PHP libraries and tooling (Doctrine ORM, Laminas components) and front-end build tooling via npm
  • Thumbnail/image generation and media handling (ImageMagick recommended)

Use Cases

  • Publish curated online exhibits that aggregate items from a shared institutional collection
  • Manage and present digital collections with descriptive metadata and controlled vocabularies
  • Provide a lightweight institutional repository for galleries, university archives, and special collections

Limitations and Considerations

  • Requires a PHP/Apache/MySQL or MariaDB stack and server configuration (PHP 8.1+ recommended)
  • Performance and scalability for very large collections may require tuning and more robust infrastructure
  • Feature availability often depends on community modules; some integrations may need custom development
  • Thumbnailing and advanced media processing rely on external tools and correct server setup

Omeka S is focused on cultural heritage publishing and metadata-driven collection management rather than general-purpose CMS features. It is well suited for institutions needing exhibit-centric workflows and semantic metadata support.

470stars
158forks
View Details
#3
ArchivesSpace

ArchivesSpace

Open-source archives information management application for accessioning, describing, preserving, and providing access to archival collections and digital objects.

ArchivesSpace screenshot

ArchivesSpace is an open-source archives information management application designed for archivists and cultural heritage institutions. It provides tools to manage archival descriptions, digital objects, and discovery interfaces for researchers and staff.

Key Features

  • Structured archival description supporting accessioning, arrangement, and descriptive metadata workflows
  • Management of digital objects and file uploads tied to descriptive records
  • RESTful API for integration, batch import/export, and programmatic access
  • Full-text and indexed search backed by a search engine for discovery and finding aids
  • Role-based access controls and user management for staff workflows and permissions
  • Deployments supported via packaged releases and containerized setups for production environments

Use Cases

  • Managing institutional archival collections, finding aids, and descriptive metadata
  • Publishing searchable discovery interfaces and providing researcher access to digital objects
  • Integrating archival metadata with institutional systems via the provided API

Limitations and Considerations

  • Typical deployments require a relational database and a search index; initial installation and configuration can be complex for smaller teams
  • Community membership provides access to some support channels and member-only documentation resources; non-members rely on community forums and public docs

ArchivesSpace is focused on archival standards and workflows, prioritizing structured metadata, preservation-aware object management, and interoperability. It is widely used by libraries, museums, and archives to centralize collection control and provide researcher access.

401stars
245forks
View Details
#4
CollectiveAccess Providence

CollectiveAccess Providence

Providence is the backend of CollectiveAccess: a PHP-based collections management system for cataloging complex metadata and media with search, GraphQL API, import/export and reporting.

CollectiveAccess Providence screenshot

CollectiveAccess Providence is the backend/cataloguing component of the CollectiveAccess collections management suite. It provides a configurable framework for describing, managing and indexing complex digital and physical collections, supporting diverse metadata schemas and many media types.

Key Features

  • Flexible data model and configurable metadata profiles to support multiple standards and custom fields
  • Multi-format media support (images, audio, video, documents, 3D) with media metadata extraction and processing
  • Built-in indexing and full-text search with support for hierarchical indexing and non-roman characters
  • GraphQL-based API for search, browsing, introspection and editing
  • Background processing for media handling, indexing and large exports
  • Importers and exporters for many formats and systems, including batch export workflows and BagIt packaging for preservation
  • Reporting and export capabilities with background processing for large datasets
  • Support for automated translation of interface/profile text and automated transcription for audio/video via integrated services

Use Cases

  • Museums, archives and libraries cataloguing and managing complex collections and associated media
  • Research institutions or projects needing structured metadata, advanced search and bulk import/export workflows
  • Institutions requiring preservation-ready exports and integration with external digital preservation systems

Limitations and Considerations

  • Installation and configuration are non-trivial and typically require familiarity with PHP, a supported RDBMS, web server configuration and Composer dependency management
  • Large collections can require careful tuning of background job/work queue settings and server resources for indexing and media processing
  • Providence provides the backend/cataloguing layer; public-facing presentation typically requires the companion front-end or custom development

CollectiveAccess Providence is a mature, feature-rich backend for institutions that need a highly configurable collections management system with advanced indexing, APIs and preservation-oriented export features.

360stars
189forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running