DSpace Self-Hosted
Institutional digital repository for scholarly works, datasets and cultural collections.
5 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
Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate.
Runs in
Documented customer environment
Persistent Java backend and Node frontend services with PostgreSQL, Solr and repository storage
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Institution manages the application releases, collection permissions, metadata, storage, backups and upgrades. AWS can operate container compute through Fargate; the institution still operates its repository services.
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.
Johns Hopkins institutional DSpace deployment on AWS ↗ · 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 | Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate. |
|---|---|
| Infrastructure | Servers / containers Persistent Java backend and Node frontend services with PostgreSQL, Solr and repository 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 DSpace core is BSD-3-Clause. Review backend/frontend dependencies and any paid service-provider agreement separately. |
| License | BSD-3-Clause core; dependencies and optional commercial hosting/support have separate 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.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The dspace-10.1 backend supplies OIDC authentication configuration with provider endpoints, client credentials, redirect, identity-claim mapping, self-registration policy and an optional login group. Enable the appropriate authentication method and configure the matching frontend; the settings do not establish compatibility with every IdP or packaged image.
Versioned DSpace repository-user OIDC plugin configuration, not machine API tokens · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The upstream README explicitly says its Docker images/Compose quickstarts are not production-ready and are intended for development/testing. Match backend/frontend versions and follow the separate production architecture.
Upstream backend development/test artifacts; not the AWS/JHU production reference · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The 10.x installation guide separates the Java backend, Node/Angular frontend, PostgreSQL and Solr. Its example Tomcat heap setting is process-level configuration, not a complete host minimum; a quantitative production CPU/RAM/storage baseline for the full reference workload was not established.
Production software/component prerequisites confirmed; whole-system hardware and HA sizing remain unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The dspace-10.1 backend core is BSD-3-Clause licensed. Frontend packages, dependencies, hosting and any commercial support must be assessed separately; the source licence is not a managed repository subscription.
Versioned DSpace backend core; not an entitlement to every third-party package or service · 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 dspace-10.1, published 2026-09-14. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
DSpace/DSpace backend repository only; the separately released Angular frontend and commercial/provider 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 backend/frontend 10.1. Follow the current installation guide for runtime and database/search compatibility; protect Solr from public access and enable HTTPS. The Johns Hopkins AWS case study demonstrates an institutional deployment, not a turnkey installer or a blanket upstream cloud-support commitment. External identity, analytics and scholarly integrations are operator choices.
Community & maintenance
DSpace has established Lyrasis/community governance and named institutional use. Johns Hopkins describes its operating repository, while the project publishes matched 10.1 releases and ongoing maintenance guidance.
Category fit
- Archives & collections management
- Manages institutional and digital collections with deposit, metadata, access and discovery for scholarly and cultural material. Repository preservation is distinct from grant administration or a general enterprise records policy engine.
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
- Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
- 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
- Current backend/frontend downloads and upgrades ↗dspace.org
- DSpace 10 production installation ↗wiki.lyrasis.org
- Johns Hopkins institutional DSpace deployment on AWS ↗aws.amazon.com
- Upstream core license ↗github.com
- Project, governance and institutional community ↗dspace.org
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Johns Hopkins institutional DSpace deployment on AWS ↗ · AWS
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS and the Johns Hopkins authors describe the library team migrating and operating JScholarship on ECS/Fargate with cloud backing services. This establishes application hosting by an adopting institution, not a vendor-hosted subscription or upstream support certification. Adapt the architecture to the selected release and operational requirements.
- Johns Hopkins institutional DSpace deployment on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Project, governance and institutional community ↗dspace.org
- Current 10.1 releases ↗dspace.org
- Johns Hopkins repository deployment ↗aws.amazon.com