
# DSpace Self-Hosted



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


## DSpace Self-Hosted

Institutional digital repository for scholarly works, datasets and cultural collections.

- Listing: https://launchinyourcloud.com/directory/dspace/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause core; dependencies and optional commercial hosting/support have separate terms.
- Licensing model: open-source
- Installation: Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate.
- Architecture: Persistent Java backend and Node frontend services with PostgreSQL, Solr and repository storage
- Operations: 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.
- Product website: https://dspace.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 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.

The DSpace core is BSD-3-Clause. Review backend/frontend dependencies and any paid service-provider agreement separately.

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.


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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/ (checked 2026-11-13). 


### Cloud deployment evidence

- Johns Hopkins institutional DSpace deployment on AWS (aws): https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/
  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.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


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

Reviewed 2026-11-13.

- Project, governance and institutional community: https://dspace.org/

- Current 10.1 releases: https://dspace.org/download/

- Johns Hopkins repository deployment: https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/

### Sources

- Current backend/frontend downloads and upgrades: https://dspace.org/download/

- DSpace 10 production installation: https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944708/Installing%2BDSpace

- Johns Hopkins institutional DSpace deployment on AWS: https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/

- Upstream core license: https://github.com/DSpace/DSpace/blob/main/LICENSE

- Project, governance and institutional community: https://dspace.org/

### Licensing sources

- https://github.com/DSpace/DSpace/blob/main/LICENSE

### Infrastructure sources

- https://dspace.org/download/

- https://aws.amazon.com/blogs/publicsector/a-faster-more-resilient-digital-repository-migrating-dspace-to-aws/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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 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. Scope: Versioned DSpace repository-user OIDC plugin configuration, not machine API tokens. Source: https://github.com/DSpace/DSpace/blob/dspace-10.1/dspace/config/modules/authentication-oidc.cfg (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream backend development/test artifacts; not the AWS/JHU production reference. Source: https://github.com/DSpace/DSpace (reviewed 2026-11-14). Deployment artifact: https://github.com/DSpace/DSpace. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Production software/component prerequisites confirmed; whole-system hardware and HA sizing remain unconfirmed. Source: https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944708/Installing%2BDSpace (reviewed 2026-11-21).

- License pricing: Documented. 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. Scope: Versioned DSpace backend core; not an entitlement to every third-party package or service. Source: https://github.com/DSpace/DSpace/blob/dspace-10.1/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: DSpace/DSpace backend repository only; the separately released Angular frontend and commercial/provider packages may differ. Source: https://github.com/DSpace/DSpace/releases/tag/dspace-10.1 (reviewed 2026-11-14).






