
# Dataverse Self-Hosted



Canonical page: https://launchinyourcloud.com/directory/dataverse/
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.


## Dataverse Self-Hosted

Institutional research-data repository for dataset preservation, metadata, access and citation.

- Listing: https://launchinyourcloud.com/directory/dataverse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache-2.0 application; dependencies and dataset reuse licenses are separate.
- Licensing model: open-source
- Installation: Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release.
- Architecture: Java/Payara application with PostgreSQL, Solr and local or object data storage
- Operations: Institution operates application and infrastructure, permissions, persistent identifiers, database/files, backups, monitoring and upgrades. External identity, citation and analysis services require configuration.
- Product website: https://dataverse.org/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used 6.12.1; Docker users need the corrected 6.12.1-noble-r3 image or newer described by upstream. The AWS developer script creates the full application but is not a production hardening shortcut. Configure HTTPS, restricted APIs, database/file recovery and appropriate sensitive-data controls before opening access. This is unrelated to Microsoft Dataverse.

The Dataverse application is Apache-2.0. Stored research datasets can use different rights and licenses; component licenses and optional services remain separate.

Java/Payara application with PostgreSQL, Solr and local or object data storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- archives-collections-management: Preserves and publishes research datasets in metadata-rich collections with persistent identifiers and access controls. It is a research-data repository, not grant-application or sponsored-award administration software.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://guides.dataverse.org/en/6.12.1/developers/deployment.html (checked 2026-11-13). 


### Cloud deployment evidence

- Upstream AWS EC2 deployment script and instructions (aws): https://guides.dataverse.org/en/6.12.1/developers/deployment.html
  The project documents AWS credential/role setup and a script that creates an EC2 instance with the Dataverse application, browser access and cleanup steps in the operator account. It is developer-oriented and warns about branch/dependency compatibility. Pair it with the supported-release production installer, hardening and backup guidance.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

Harvard IQSS develops the project with sustained multi-institution community participation. The maintained 6.12.1 release includes security fixes and detailed upgrade instructions, and the project documents its institutional research repository purpose.

Reviewed 2026-11-13.

- Reviewed release and corrected Docker-image notice: https://github.com/IQSS/dataverse/releases/tag/v6.12.1

- Institutional project and community: https://dataverse.org/about/

### Sources

- Production installation guide for 6.12.1: https://guides.dataverse.org/en/6.12.1/installation/index.html

- Production security, identifiers and storage configuration: https://guides.dataverse.org/en/6.12.1/installation/config.html

- Repository and collection scope: https://dataverse.org/about/

- Upstream AWS EC2 deployment script and instructions: https://guides.dataverse.org/en/6.12.1/developers/deployment.html

- Upstream software license: https://github.com/IQSS/dataverse/blob/develop/LICENSE.md

- Reviewed release and corrected Docker-image notice: https://github.com/IQSS/dataverse/releases/tag/v6.12.1

### Licensing sources

- https://github.com/IQSS/dataverse/blob/develop/LICENSE.md

### Infrastructure sources

- https://guides.dataverse.org/en/6.12.1/installation/index.html

- https://guides.dataverse.org/en/6.12.1/developers/deployment.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 6.12.1 installation guides document OIDC login with configurable providers and a separate Shibboleth integration. Provider registration, client/redirect settings and stable account identifiers require configuration; login is distinct from API-token access and repository permissions. Scope: Versioned self-hosted repository-user federation. Source: https://guides.dataverse.org/en/6.12.1/installation/oidc.html (reviewed 2026-11-21). Supporting source: Shibboleth integration — https://guides.dataverse.org/en/6.12.1/installation/shibboleth.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned 6.12.1 installation guide separates standard and container installation paths. Prepare the database, search/application services and configuration before following the selected deployment workflow. Scope: Dataverse 6.12.1 installation paths; not every community cloud package. Source: https://guides.dataverse.org/en/6.12.1/installation/prep.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The 6.12.1 guide gives an 8-GB RAM/50-GB disk test-VM example and a much larger Harvard reference with separate application, Solr and R servers plus RDS and S3. Those examples illustrate workload variation rather than a universal production minimum; data services, ingest and retention need separate capacity planning. Scope: Published test and institutional reference examples, not validated 100-user/1-TB HA sizing or a current cost estimate. Source: https://guides.dataverse.org/en/6.12.1/installation/prep.html (reviewed 2026-11-21).

- License pricing: Documented. The v6.12.1 software is Apache-2.0 licensed. Hosting, persistent storage, identifiers, external services and professional support require separate arrangements; a repository installation is distinct from using Harvard Dataverse as a hosted service. Scope: Versioned Dataverse software licence; optional components and services have separate terms. Source: https://github.com/IQSS/dataverse/blob/v6.12.1/LICENSE.md (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v6.12.1, published 2026-10-08. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream IQSS/dataverse release record; commercial editions and deployment packages may differ. Source: https://github.com/IQSS/dataverse/releases/tag/v6.12.1 (reviewed 2026-11-14).






