---
title: "Adl Lrs"
description: "ADL wrote the Experience API, and this is their reference implementation of a learning record store: a Django application that accepts, validates and serves xAPI statements, with OAuth support and a Docker Compose installation path. It has been going since 2012 and was updated to xAPI 2.0 — that is, IEEE 9274.1.1 — which makes it one of the few implementations tracking the standard's move under IEEE stewardship."
canonical_url: "https://scorm-tools.com/tools/adl-lrs"
last_updated: "2026-10-31T10:21:59.365Z"
---

ADL wrote the Experience API, and this is their reference implementation of a learning record store: a Django application that accepts, validates and serves xAPI statements, with OAuth support and a Docker Compose installation path. It has been going since 2012 and was updated to xAPI 2.0 — that is, IEEE 9274.1.1 — which makes it one of the few implementations tracking the standard's move under IEEE stewardship.

Its value is as a reference rather than as infrastructure, and the project says so itself: stable, but intended to support a small number of users as a proof of concept. That is an unusually candid README, and it should be believed. If you are debugging whether your content's statements are well-formed, or arguing about how a particular part of the spec should behave, having ADL's own implementation to test against settles things quickly. If you need an LRS that will hold years of statements for thousands of learners, look at SQL LRS or a commercial product instead.

Maintenance reads as institutional rather than energetic. The last tagged release is v2.0.0 from June 2023, with commits continuing into November 2025 — attended to, not actively developed. For a reference implementation that is a reasonable state to be in; for a dependency it is a reason to look elsewhere.