edu-sharing

edu-sharing is built for organizations that need educational content to move between learning platforms, repositories, and authoring tools. It is most suitable for schools, universities, public bodies, businesses, and associations able to operate a repository themselves or engage a service partner. The strongest reason to choose it is its combination of open-source control and structured content governance; the main caution is that deployment and mobile access carry infrastructure responsibilities.

Overview

edu-sharing combines an educational cloud, OER search, and storage for learning materials, metadata, tools, and didactical scenarios. Its value is greatest when an organization already uses several learning systems and wants content to remain reusable across them, rather than locking resources inside one platform.

Private, shared, and editorial collections support different working patterns, from personal drafting to institution-wide publication. Permissions, role controls, approval workflows, version history, content reuse, and SCORM/xAPI support make it a serious repository for governed learning content rather than a simple file share.

Key features

Collections and governance: Teams can create private, shared, and editorial collections and decide who may use each one. Approval workflows and version history suit content that needs review and controlled updates.

Connected learning stack: Plug-ins for Moodle, ILIAS, MediaWiki, TYPO3, and OpenOLAT, plus connectors for OnlyOffice and ONYX Editor, help organizations keep existing systems in the workflow.

Identity and access: LDAP, Shibboleth, and SSO connections can map users, groups, and organizations, reducing the need to maintain separate identity structures.

API and standards: A REST API documented with the OpenAPI Specification supports integration work, while SCORM and xAPI support helps with standards-based learning content.

Protected materials: The safe adds a separately secured area with a second password and role- or permission-based access. Configurable upload filters can inspect content and extensions and block disguised file types.

Self-hosting: Organizations can install and adapt edu-sharing on their own servers. Docker images and downloads for the repository and rendering service are offered, including a 10.0 RC release.

Pricing

edu-sharing Open Source — free: The open-source product and materials can be downloaded without charge. This suits institutions with technical capacity, or those prepared to contract a partner, and avoids a per-seat software fee. The trade-off is that hosting, configuration, updates, training, and support come through service providers and development partners rather than being included in the free download.

Service partners can provide hosting, installation, configuration, updates, training, and support. That route is appropriate for organizations that want the platform's control without running every operational task themselves, but the service cost is arranged separately.

Platforms

edu-sharing supports Android, iOS, web access, APIs, and self-hosted deployment. The Android and iOS app works on smartphones and tablets only when an accessible edu-sharing repository, rendering service, and user account are in place. Mobile users therefore depend on the organization's repository architecture; the app is not a standalone substitute for that infrastructure.

Who it's for

Choose edu-sharing when a school, university, public authority, business, or association needs one governed content layer across multiple learning environments, wants open-source deployment, or requires integration with existing identity systems. It is less appropriate for a small team seeking a turnkey hosted library with no repository administration, especially if mobile access must work without organization-managed services.

Pros and cons

Pros

Open-source, self-hosted deployment gives organizations control over infrastructure and adaptation.

Collection permissions, approval workflows, version history, and role controls support accountable publishing.

Broad plug-in, connector, identity, API, and learning-standard coverage helps connect an established education stack.

A separate safe and upload filtering add safeguards for protected or potentially disguised files.

Cons

Mobile use requires an accessible repository and rendering service as well as an account.

Running the repository, rendering service, and updates requires operational expertise or a paid service partner.

The free software download does not include hosting, implementation, training, or support.

Alternatives

For a broader comparison, see Learning Content Management Systems. Choose LCMS Cloud instead if a paid service with a seven-day free trial and web or self-hosted deployment better fits your evaluation process; its Starter plan is 149 IDR a month. AContent is another free, open-source LCMS with API, desktop, Linux, Windows, web, and self-hosted support, making it a better fit when those platform options matter more than edu-sharing's repository integrations. Edlib offers free self-hosting under GPL 3.0 and a paid Teams plan at $23 a month, useful when you want an open-source route with an explicit team offering. eXact LCMS suits organizations seeking hosted or on-premises deployment with parametric settings and custom pricing. LON-CAPA is free self-hosted software with no software or cluster fee, but requires a dedicated server and ongoing maintenance. MadCap Flare is a paid Windows/web authoring option, with its Starter desktop plan at $3,150 a year, for teams focused on topic-based and micro-content authoring. Edu-Suite CMS provides a SaaS-oriented path with a free Starter tier for up to five users and a 249.00 EUR monthly Growth plan. Instancy LCMS is a paid, custom-priced subscription for Android, iOS, and web deployments.

Verdict

edu-sharing is a strong choice for education-focused organizations that need interoperable repositories, governed collections, and the freedom to self-host or tailor integrations. Choose it for control and cross-platform content reuse; look elsewhere if you want a fully managed, immediately mobile-ready service without repository and rendering-service responsibilities.