Dataverse Self-Hosted
Institutional research-data repository for dataset preservation, metadata, access and citation.
6 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release.
Runs in
Documented customer environment
Java/Payara application with PostgreSQL, Solr and local or object data storage
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Institution operates application and infrastructure, permissions, persistent identifiers, database/files, backups, monitoring and upgrades. External identity, citation and analysis services require configuration.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Upstream AWS EC2 deployment script and instructions ↗ · Source checked 2026-11-13
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release. |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core The Dataverse application is Apache-2.0. Stored research datasets can use different rights and licenses; component licenses and optional services remain separate. |
| License | Apache-2.0 application; dependencies and dataset reuse licenses are separate. |
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.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Versioned self-hosted repository-user federation · Source ↗ · Shibboleth integration ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Dataverse 6.12.1 installation paths; not every community cloud package · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Published test and institutional reference examples, not validated 100-user/1-TB HA sizing or a current cost estimate · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Versioned Dataverse software licence; optional components and services have separate terms · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream IQSS/dataverse release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 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.
Scope & considerations
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.
Community & 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.
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.
Compare within Archives & collections management
- ArchesOpen-source cultural-heritage inventory and resource-information platform.
- AWS
- ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
- AWS
- ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
- AWS
- Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- AWS
- BrowsertrixOpen-source browser-based web archiving and collection-management application.
- DigitalOcean
- DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
- AWS
- Fedora RepositoryOpen-source preservation repository with an AWS Terraform deployment.
- AWS
- FormKiQ Archives and Collections Management Directory PublisherConnect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.
- AWS
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Production installation guide for 6.12.1 ↗guides.dataverse.org
- Production security, identifiers and storage configuration ↗guides.dataverse.org
- Repository and collection scope ↗dataverse.org
- Upstream AWS EC2 deployment script and instructions ↗guides.dataverse.org
- Upstream software license ↗github.com
- Reviewed release and corrected Docker-image notice ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Upstream AWS EC2 deployment script and instructions ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Upstream AWS EC2 deployment script and instructions ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Reviewed release and corrected Docker-image notice ↗github.com
- Institutional project and community ↗dataverse.org