openLRS
5.6#17 in learning record store softwareWebAPISelf-hosted
Visit| Fact | openLRS | SQL LRS |
|---|---|---|
| Authentication | The /lrs endpoint requires an X-Signature header calculated from a secret shared by the learning platform and openLRS. | SQL LRS supports OpenID Connect over OAuth 2.0 for xAPI endpoints and administrative functions. |
| Deployment | The instructions describe building the frontend and serving it with the Express backend on a server. | SQL LRS is available through GitHub, DockerHub, and Platform One’s Iron Bank, and customers host it themselves. |
| Headquarters | Potsdam, Germany | Savage, Maryland, USA |
| License | The repository states that openLRS is open source under the MIT License. | SQL LRS is distributed under the Apache 2.0 license and may be used in commercial projects. |
| Purpose | openLRS stores and retrieves learning records generated by learning activities and supports the Experience API (xAPI). | SQL LRS stores xAPI statements, attachments, and documents as a Learning Record Store. |
No prices published.
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.
SQL LRS may suit organizations that need to collect or exchange xAPI learning data and can host the software themselves. It may also fit teams connecting structured learning records to BI or AI systems.