InvenioRDM

Research and institutional repository platform for digital-resource deposit, curation and discovery.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Official Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration.

  2. Operated by

    Your team

    Institution operates application and workers, identity, search, data services, configuration, backups and upgrades. Cloud resources are separate from the public Zenodo hosted service.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration.
InfrastructureServers / containers
Persistent Python web/worker services with PostgreSQL, search, queue/cache and local or object storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.
Licensing modelOpen Source / Open Core
The invenio-app-rdm application is MIT licensed. Its framework/modules, optional services and institution-specific customizations must be reviewed under their own licenses.
LicenseMIT application code; framework modules, institutional customizations and dependencies retain their own terms.

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.

4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
DocumentedEvidence and scope for Single sign-on

The project explicitly describes integration with an institution’s SSO. Confirm the chosen authentication integration, user mapping and local customization for the deployed release.

Institution-operated InvenioRDM; not a guarantee for an unmodified third-party package · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The production guide documents deployment strategies and points to the project-generated Compose reference and Invenio Helm charts used on Kubernetes/OpenShift. The Compose file is explicitly a development/reference configuration requiring production customization, persistence, backups and network configuration.

Upstream production strategy with explicit reference-template limits · Source ↗ · Deployment artifact ↗ (repository default branch (moving); select charts compatible with the chosen InvenioRDM release) · Reviewed 2026-11-21

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The production guide gives 4 vCPU/16 GB RAM as a typical co-located small-instance starting point for thousands of records and tens of concurrent users. It separately sizes web/worker processes, PostgreSQL, OpenSearch and lightweight services, with file storage driven by upload volume. Larger instances and HA require a different plan.

Published small production reference, not a 100-user/1-TB HA guarantee · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The reviewed invenio-app-rdm source uses the MIT License. This application licence is separate from the licences of its infrastructure dependencies and any institutional hosting, implementation or support agreement.

Reviewed upstream application source on the moving master branch; assess dependency and service terms separately · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
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.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The upstream project identifies v14. Caltech documents its own EC2 deployment and earlier release-specific setup, not universal v14 compatibility. Follow current upstream production requirements and review the institution-specific files before reuse. Docker Compose reference defaults require production adaptation. External DOI, identity, mail and analytics services have separate data boundaries.

Community & maintenance

CERN publishes a participating-institution governance model and ongoing InvenioRDM releases. Caltech Library maintains a named institutional deployment and source customization, establishing use beyond a demo or star count.

Category fit

Archives & collections management
Provides institutional and research-data repositories with deposit, curation, metadata, access and dissemination. Research-data repository functions do not establish grant administration or clinical regulatory-document control.

Compare within Archives & collections management

  • ArchesOpen-source cultural-heritage inventory and resource-information platform.
    • AWS
    Customer-operated · Open Source / Open Core
  • ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
    • AWS
    Customer-operated · Open Source / Open Core
  • ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
    • AWS
    Customer-operated · Open Source / Open Core
  • Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
    • AWS
    Customer-operated · Open Source / Open Core
  • BrowsertrixOpen-source browser-based web archiving and collection-management application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
    • AWS
    Customer-operated · Open Source / Open Core
  • DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
    • AWS
    Customer-operated · Open Source / Open Core
  • Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
    • AWS
    Customer-operated · Open Source / Open Core

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • CaltechAUTHORS institutional AWS EC2 deployment ↗ · AWS

      Institution deployment · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Caltech Library documents running its customized InvenioRDM repository on AWS EC2 with Ubuntu, application installation and S3 configuration. This is an institution-maintained deployment example, not a stock v14 installer or CERN support commitment. Replace institutional values and reconcile runtime, dependencies, secrets and upgrades with the chosen current release.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory