ADL Open Source LRS

ADL Open Source LRS is a self-hosted repository for learning records collected through xAPI. It is best suited to teams building a small proof of concept who can operate their own infrastructure. Its open-source, configurable deployment is appealing, but the stated small-user scope makes it a poor choice for larger services.

Overview

The project says this version has been updated to IEEE 9274.1.1, also known as xAPI 2.0. It calls the release stable while describing it as intended for a small number of users in proof-of-concept work. That is a meaningful boundary: stability supports evaluation and limited use, but does not make this the right foundation for a service that needs to scale.

The software is distributed under the Apache License, Version 2.0, giving teams an open-source basis to configure and adapt it. The repository welcomes pull requests and suggests submitting an issue for users who do not want to edit code. This suits organizations willing to engage with a software project, rather than those seeking a managed service relationship.

Key features

Self-hosted deployment

Docker and Docker Compose are the recommended simplest installation route. The deployment brings together a Django web service running with uWSGI, an nginx HTTP/HTTPS proxy, PostgreSQL, RabbitMQ and Redis. Having the components packaged together reduces the burden of assembling a stack from scratch, but the resulting multi-service deployment still needs to be operated and maintained.

Database settings can be changed in settings.ini, which gives teams some control over installation configuration. The Docker guide also describes an included Certbot container for obtaining a certificate for a publicly available domain, with nginx restarted to use it. That is useful for a public deployment, though it remains the operator’s responsibility to run the host and deployment.

Integration controls and processing

OAuth is not enabled by default. Teams that need it must turn it on with the OAUTH_ENABLED setting and register clients with the LRS, so it is a configurable option rather than an out-of-the-box security setting.

Optional statement webhooks can filter incoming xAPI statements and forward matches to a client endpoint. They are disabled by default, and a webhook can include a secret so the LRS sends an HMAC hex digest in the X-LRS-Signature header. These controls can support integrations that need selective delivery and signature verification, but they require deliberate setup.

Celery handles activity-metadata retrieval, statement voiding and LRS-hook checks asynchronously. That separates these tasks from the immediate request flow, a useful design for this kind of processing. The repository does not position the project for high-volume operation, however; its small-user proof-of-concept scope remains the more important capacity constraint.

Pricing

ADL Open Source LRS costs nothing under its free plan, which is described as a proof of concept intended to support a small amount of users. There is no trial period to weigh against a paid subscription; the software is open source under Apache License 2.0. This is a strong fit for evaluation or a deliberately small deployment, but the free price should not be mistaken for a promise of production scale.

Platforms

The project supports API and web access and is self-hosted. That combination fits teams integrating xAPI data into their own systems and operating the service in their own environment, rather than buyers looking for a hosted LRS.

Who it's for

Choose ADL Open Source LRS for a small xAPI proof of concept when standards alignment, self-hosting and the ability to configure the deployment matter more than managed operations or room for a large user base. It is less suitable for organizations that need a hosted service, expect substantial growth, or do not want to maintain a multi-service stack.

Pros and cons

• Apache 2.0 open source: teams can use and adapt the software without a subscription price.
• Updated for xAPI 2.0: the stated alignment makes it relevant to teams working to that standard.
• Bundled Docker deployment: the recommended route packages the web service, proxy, database and supporting services, but still requires stack operations.
• Configurable integrations: optional OAuth and signed, filtered webhooks provide useful controls, though they are not enabled by default.
• Small-user proof-of-concept scope: this is the central drawback for teams planning a larger deployment.

Alternatives

Learning Record Store Software is the broader category to explore when comparing LRS options.

Consider Veracity Learning if you want a freemium alternative with a free Lite plan for five LRSs, based on your infrastructure. SQL LRS is another free, Apache 2.0, self-hosted option; its implementation and support services are quoted separately.

Cluelabs LRS is a freemium alternative with API, Android, iOS and web platforms, maintained by an eLearning company described as a provider of custom training solutions. Mosra offers a free launch-period plan with unlimited lessons and listed features and exports, with paid plans planned but not yet live.

xh is a free open-source command-line HTTP client, rather than an LRS. Jupiter offers a hosted Jove LRS free up to 1 million events per year. Ralph is a free, MIT-licensed LRS distributed as a Python package and Docker image. Sereni LRS may suit teams seeking a free plan with up to 100,000 xAPI statements or events, 1 GB of storage, unlimited LRSs, and unlimited reporting and analytics.

Verdict

ADL Open Source LRS is a sensible choice for technically capable teams that need a free, self-hosted xAPI 2.0 proof of concept and want control over configuration. The main reason to choose it is the combination of an open-source license and a packaged Docker deployment; the main reason to look elsewhere is its explicitly small-user scope, which makes it difficult to recommend for a growing or large-scale service.