openLRS
github.com
What it is
openLRS is a free, open-source Learning Record Store for storing and retrieving learning records generated by learning activities. It supports the Experience API, also called xAPI or Tin Can API. The project includes an Express backend that stores and retrieves records and a React frontend that displays them. Learning platforms create entries by sending xAPI data and session metadata to the /lrs endpoint with a POST request. Requests require an X-Signature header calculated from a shared secret, plus a custom consumer and context ID. openLRS was built for openHPI and the KI Campus H5P Tool and can be adapted for other platforms. Its Moodle plugin captures xAPI events from H5P content and sends them to an external openLRS for analysis. Self-hosting requires MongoDB, Node modules, database configuration, and a server running the Express backend. The repository is available under the MIT License, but GitHub lists it as archived and read-only from February 20, 2026.
Spec sheet
- Purpose
- openLRS stores and retrieves learning records generated by learning activities and supports the Experience API (xAPI).Read 8 Oct 2026 · github.com
- Deployment
- The instructions describe building the frontend and serving it with the Express backend on a server.Read 8 Oct 2026 · github.com
- API
- The documented /lrs endpoint accepts POST requests to create an LRS entry.Read 8 Oct 2026 · github.com
- Support
- The repository provides setup and deployment instructions; it does not state a support service or response commitment.Read 8 Oct 2026 · github.com
- License
- The repository states that openLRS is open source under the MIT License.Read 8 Oct 2026 · github.com
- Headquarters
- Potsdam, GermanyRead 28 Sep 2026 · github.com
- API endpoint
- The LRS endpoint accepts POST requests at /lrs to create an entry.Read 4 Oct 2026 · github.com
- Authentication
- The /lrs endpoint requires an X-Signature header calculated from a secret shared by the learning platform and openLRS.Read 8 Oct 2026 · github.com
- Backend and frontend
- The backend is an Express app that stores and retrieves xAPI records, and the frontend is a React app that displays records.Read 4 Oct 2026 · github.com
- Data format
- Requests to the endpoint must contain xAPI data and session metadata, including a custom consumer and context ID.Read 4 Oct 2026 · github.com
- Deployment requirements
- The setup instructions require MongoDB, Node modules, and a server deployment using the Express backend.Read 4 Oct 2026 · github.com
- Intended use
- The project says it was built for the openHPI/KI Campus H5P Tool and can be adapted for other platforms.Read 8 Oct 2026 · github.com
- Interface
- The repository contains an Express backend for storing and retrieving xAPI records and a React frontend for displaying records.Read 8 Oct 2026 · github.com
- Maker identity
- The openHPI imprint identifies Hasso-Plattner-Institut für Digital Engineering gGmbH as the organization behind openHPI.Read 4 Oct 2026 · open.hpi.de
- Maker location
- The openHPI GitHub organization lists its location as Potsdam, Germany.Read 4 Oct 2026 · github.com
- Moodle integration
- The openLRS Moodle plugin captures xAPI events from H5P content and sends them to an external openLRS for analysis.Read 8 Oct 2026 · github.com
- Moodle setup
- The Moodle plugin requires an external LRS URL, a secret key, a consumer ID, and a Moodle web service token.Read 4 Oct 2026 · github.com
- Project status
- GitHub says the repository was archived on February 20, 2026, and is read-only.Read 8 Oct 2026 · github.com
- Repository status
- GitHub states that the repository was archived on February 20, 2026, and is read-only.Read 4 Oct 2026 · github.com
- Storage requirement
- The setup instructions require MongoDB and configuration of its connection URL, database, and xAPI collection.Read 8 Oct 2026 · github.com
- xAPI support
- It supports the Experience API (xAPI), also known as Tin Can API.Read 4 Oct 2026 · github.com
Strong points and limits
Strong points
- Free and released under the MIT License
- Supports xAPI learning records
- Includes Express backend and React frontend
- Moodle plugin forwards H5P events
- Available through API and web interfaces
Limits
- Repository is archived and read-only
- Self-hosting requires MongoDB and server deployment
- Requests require signature and session metadata
- No support service or response commitment is stated
Who it suits
It suits organizations needing a self-hosted xAPI record store that they can adapt. Moodle users with H5P event tracking are a stated use case.
Verdict
openLRS provides a focused, self-hosted xAPI store with a web interface and Moodle integration. Its archived, read-only status is important when evaluating it for new deployments.
Where Specifiction places it
- Learning Record Store Software#18 of 237.3