
# InvenioRDM



Canonical page: https://launchinyourcloud.com/directory/inveniordm/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## InvenioRDM

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

- Listing: https://launchinyourcloud.com/directory/inveniordm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT application code; framework modules, institutional customizations and dependencies retain their own terms.
- Licensing model: open-source
- Installation: Official Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration.
- Architecture: Persistent Python web/worker services with PostgreSQL, search, queue/cache and local or object storage
- Operations: Institution operates application and workers, identity, search, data services, configuration, backups and upgrades. Cloud resources are separate from the public Zenodo hosted service.
- Product website: https://inveniosoftware.org/products/rdm/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

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.

The invenio-app-rdm application is MIT licensed. Its framework/modules, optional services and institution-specific customizations must be reviewed under their own licenses.

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.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/caltechlibrary/caltechauthors (checked 2026-11-13). 


### Cloud deployment evidence

- CaltechAUTHORS institutional AWS EC2 deployment (aws): https://github.com/caltechlibrary/caltechauthors
  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.
  Source type: institution-deployment; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-13.

- Institutional governance: https://inveniosoftware.org/governance/

- Current release and community: https://inveniosoftware.org/products/rdm/

- Named Caltech institutional repository: https://github.com/caltechlibrary/caltechauthors

### Sources

- Current product and release: https://inveniosoftware.org/products/rdm/

- Production runtime, persistence and operations: https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md

- Institutional cloud-init prerequisites: https://github.com/caltechlibrary/cloud-init-examples/blob/main/invenio-rdm-13-init.yaml

- CaltechAUTHORS institutional AWS EC2 deployment: https://github.com/caltechlibrary/caltechauthors

- Application license: https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE

- Institutional governance: https://inveniosoftware.org/governance/

### Licensing sources

- https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE

### Infrastructure sources

- https://inveniosoftware.org/products/rdm/

- https://github.com/caltechlibrary/caltechauthors


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The project explicitly describes integration with an institution’s SSO. Confirm the chosen authentication integration, user mapping and local customization for the deployed release. Scope: Institution-operated InvenioRDM; not a guarantee for an unmodified third-party package. Source: https://inveniosoftware.org/products/rdm/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream production strategy with explicit reference-template limits. Source: https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md (reviewed 2026-11-21). Deployment artifact: https://github.com/inveniosoftware/helm-invenio. Artifact reference: repository default branch (moving); select charts compatible with the chosen InvenioRDM release.

- Minimum footprint / sizing: Documented. 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. Scope: Published small production reference, not a 100-user/1-TB HA guarantee. Source: https://github.com/inveniosoftware/docs-invenio-rdm/blob/master/docs/operate/ops/deploy.md (reviewed 2026-11-21).

- License pricing: Documented. 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. Scope: Reviewed upstream application source on the moving master branch; assess dependency and service terms separately. Source: https://github.com/inveniosoftware/invenio-app-rdm/blob/master/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






