openLRS
openLRS is a Learning Record Store for storing and retrieving records produced by learning activities.
What openLRS is
openLRS is a Learning Record Store for storing and retrieving records produced by learning activities. It supports xAPI, also called Tin Can API, and pairs an Express backend for record handling with a React frontend for displaying records. A learning platform creates an entry by sending a POST request to the `/lrs` endpoint. Requests need xAPI data and session metadata, including a custom consumer and context ID, plus an `X-Signature` header calculated from a secret shared with openLRS. The project was built for openHPI and the KI Campus H5P Tool, though it can be adapted for other platforms. Its Moodle plugin captures xAPI events from H5P content and forwards them to an external openLRS for analysis. Deployment requires MongoDB, Node modules, and a server running the Express backend. The Moodle plugin setup also needs an external LRS URL, secret key, consumer ID, and Moodle web service token. The repository states that openLRS is available under the MIT License, but GitHub reports it was archived on February 20, 2026, and is read-only. The project is associated with openHPI in Potsdam, Germany.
Good
- Supports xAPI learning records.
- Includes Express backend and React frontend.
- Moodle plugin forwards H5P events to an external LRS.
- Software is available under the MIT License.
Watch out
- Repository is archived and read-only.
- Deployment requires MongoDB and Node modules.
- Requests need a shared-secret signature.
- Moodle setup requires several credentials and configuration values.
Who it suits
openLRS may suit teams that need an xAPI record store for learning platforms, including Moodle setups that capture H5P events. Its archived, read-only repository and self-hosting requirements are central considerations.
Verdict
openLRS provides an xAPI-focused store and a Moodle plugin for H5P event capture. Its archived status, server requirements, and request authentication requirements should be weighed before adopting it.
The facts
Each one read from openLRS's own pages, with the date it was checked.
What it does
- API
- The documented /lrs endpoint accepts POST requests to create an LRS entry.checked 8 Oct 2001
- API endpoint
- The LRS endpoint accepts POST requests at /lrs to create an entry.checked 4 Oct 2001
- Authentication
- The /lrs endpoint requires an X-Signature header calculated from a secret shared by the learning platform and openLRS.checked 8 Oct 2001
- 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.checked 4 Oct 2001
- Data format
- Requests to the endpoint must contain xAPI data and session metadata, including a custom consumer and context ID.checked 4 Oct 2001
- Deployment
- The instructions describe building the frontend and serving it with the Express backend on a server.checked 8 Oct 2001
- Deployment requirements
- The setup instructions require MongoDB, Node modules, and a server deployment using the Express backend.checked 4 Oct 2001
- Intended use
- The project says it was built for the openHPI/KI Campus H5P Tool and can be adapted for other platforms.checked 8 Oct 2001
- Interface
- The repository contains an Express backend for storing and retrieving xAPI records and a React frontend for displaying records.checked 8 Oct 2001
- License
- The repository states that openLRS is open source under the MIT License.checked 8 Oct 2001
- Moodle integration
- The openLRS Moodle plugin captures xAPI events from H5P content and sends them to an external openLRS for analysis.checked 8 Oct 2001
- Moodle setup
- The Moodle plugin requires an external LRS URL, a secret key, a consumer ID, and a Moodle web service token.checked 4 Oct 2001
- Project status
- GitHub says the repository was archived on February 20, 2026, and is read-only.checked 8 Oct 2001
- Purpose
- openLRS stores and retrieves learning records generated by learning activities and supports the Experience API (xAPI).checked 8 Oct 2001
- Repository status
- GitHub states that the repository was archived on February 20, 2026, and is read-only.checked 4 Oct 2001
- Storage requirement
- The setup instructions require MongoDB and configuration of its connection URL, database, and xAPI collection.checked 8 Oct 2001
- Support
- The repository provides setup and deployment instructions; it does not state a support service or response commitment.checked 8 Oct 2001
- xAPI support
- It supports the Experience API (xAPI), also known as Tin Can API.checked 4 Oct 2001
The company
- Headquarters
- Potsdam, Germanychecked 28 Sep 2001
- Maker identity
- The openHPI imprint identifies Hasso-Plattner-Institut für Digital Engineering gGmbH as the organization behind openHPI.checked 4 Oct 2001
- Maker location
- The openHPI GitHub organization lists its location as Potsdam, Germany.checked 4 Oct 2001
Alternatives to openLRS
- 1
xh
Free planOpen sourceAndroidLinuxmacOSWindows7.6Free plan - 2
SQL LRS
Free planOpen sourceWebAPILinuxmacOS7.5Free plan - 3
Cluelabs LRS
Free planAndroidiOSWebAPI7.2From $19.95 a month - 4
Veracity Learning
Free planWebAPILinuxmacOS7.1From $100 a month - 5
Mosra
Free planWebmacOSSelf-hostedWindows7.0Free plan - 6
GrassBlade LRS
AndroidiOSWebAPI6.7From $5.50 a month