Everything an institution runs, on one platform.
Author with AI grounded in your own documents. Assess with rubrics and psychometrics. Certify verifiably. Run every campus, client company and department as its own organisation, under its own brand and domain, from one tenant.
What Lurno is
Lurno is a multi-tenant learning platform built by Augmental Learning Inc. for institutions rather than for a single course. One tenant holds every organisation you run — campuses, client companies, departments — each with its own brand, domain and administrators, while content, roles and reporting stay in one place. Inside it you author programs with AI grounded in documents you upload, assess with 19 question types and analytic, holistic or single-point rubrics, track competencies against a framework, issue certificates anyone can check on a public page, and ask questions of the whole record in reporting scoped by the same permissions as everything else. It runs in multiple languages, right-to-left included.
- Multi-tenant learning platform
- A learning platform where each customer's data sits in an isolated tenant, and where a tenant can itself contain nested organisations. A training provider keeps one organisation per client company; a school group keeps one per school. In Lurno that isolation is enforced underneath the platform itself, not by a screen that has to remember to filter.
Most institutions arrive carrying four tools: an LMS for delivery, an authoring tool for content, a survey tool for feedback, and a BI seat for the numbers. Each holds a piece of the learner's record, and nobody quite trusts the joins between them.
The eight pages below cover each area in detail. If you would rather start from your own shape, start at who we build for. Plans and member caps are on pricing.
Eight areas, one record
Everything on these pages is shipped. What is not, we badge — the next section lists it.
What holds the eight areas together
One tenant, many organisations
A tenant holds nested sub-organisations, and inside each one a branch tree — campus, faculty, department. A role granted at a branch cascades to every branch beneath it, so a campus administrator sees their campus and nothing above it. Roles are built from a permission catalogue and granted at eight scopes, from the platform down to a single group.
- A corporate academy runs training for 15 client companies from one tenant
- A K-12 publisher runs 114 schools on a single platform
Marked once, used four times
An attempt is graded once. That grade is the evidence behind a competency, the condition a certificate policy checks, and a row in reporting. Nothing is exported and re-joined, so the completion figure in the board pack is the one the grading queue produced.
Insights and reportingOne person, several roles
Someone who teaches one program and studies another moves between surfaces without a second account. Every role granted, consent recorded and export taken lands in an audit log that cannot be quietly edited that cannot be edited afterwards.
What is not shipped yet
Badged rather than buried. If one of these gates your rollout, say so and you get a date rather than a maybe.
SCORM 1.2, SCORM 2004, xAPI and LTI 1.3
In developmentModelled in the product; the runtime is being built. Talk to us if standards conformance gates your rollout.
Payments and checkout
In developmentDesigned, not built. Enrolment today is by invitation or by an administrator.
Self-serve signup and trials
In developmentAccounts are created by invitation. A demo is how you see the product for now.
SAML and OIDC single sign-on, MFA, passkeys
On the roadmapOn the roadmap. Partner sign-on (silent SSO) is shipped: your existing portal signs a handover assertion and the learner arrives already authenticated.
Native mobile apps
On the roadmapOn the roadmap. The web app is responsive and works in a phone browser today.
One platform against four tools
The comparison institutions actually make: Lurno against an LMS, an authoring tool, a survey tool and a BI seat bought separately.
| Capability | Lurno | LMS + authoring + survey + BI |
|---|---|---|
| Where the learner record lives | One database, one row per attempt | Split across four systems, joined by export |
| Adding a client or a campus | A sub-organisation in the same tenant, with its own brand and domain | A new instance, or one shared instance filtered by hand |
| Who can see what | One permission catalogue; a role granted at a branch cascades down it | Set per tool, and re-set in each when someone moves |
| Authoring | In the platform, with AI grounded in the documents you upload | A separate tool that exports a package |
| Feedback and wellbeing | Check-ins inside the platform, reported only in groups large enough to hide the individual | A survey tool with its own logins and its own export |
| Reporting | Certified metrics and plain-language questions, scoped by the same permissions | A BI seat, and someone to keep the pipeline alive |
| Certificates | Issued by policy on completion, verifiable on a public page | A separate credentialing tool, or a PDF |
| SCORM, xAPI and LTI | In development | Mature in most established LMSs |
Not a knock on the LMS. If you only need delivery and already own the other three tools, four tools cost less than one platform. The case for Lurno is the joins — and the fifteenth client, or the hundredth school.
Before the call
See it on your own org chart
Bring the shape you actually run — schools, client companies, departments — and we will show how it maps onto one tenant.