Larmer LRS vs openLRS
Larmer LRS
larmerbrown.comopenLRS
github.comSide by side
| Figure | Larmer LRS | openLRS |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Learning Record Store Software | 7.6 (#12) | 7.3 (#18) |
| API | It provides an advanced search API and a simplified query language called VQL for querying and aggregating xAPI data. | The documented /lrs endpoint accepts POST requests to create an LRS entry. |
| Authentication | The page says basic authentication and two factor email verification are supported by default, with IAM or SSO integration options including OpenID Connect providers such as Okta, GLUU, and Auth0. | The /lrs endpoint requires an X-Signature header calculated from a secret shared by the learning platform and openLRS. |
| Deployment | Larmer LRS is available as SaaS in a Larmer Brown private cloud or as an on premise solution. | The instructions describe building the frontend and serving it with the Express backend on a server. |
| Purpose | Larmer LRS stores xAPI learning records and provides granular tracking, reporting, and learning analytics. | openLRS stores and retrieves learning records generated by learning activities and supports the Experience API (xAPI). |
| Support | Subscriptions include technical and telephone support and future upgrades; a four hour virtual workshop and bespoke support are also offered, and Premier Subscription includes consultancy support. | The repository provides setup and deployment instructions; it does not state a support service or response commitment. |
Plans
In their own words
Larmer LRS
Larmer LRS has no write-up on Specifiction yet; its figures are above.
openLRS
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.