Brightspace models a course. You are running an organisation chart.
Brightspace is a mature academic LMS built around the term: a course, a roster, a transcript. That is the right shape for one university. It is the wrong shape for a publisher running 114 schools or an academy training fifteen client companies, where the unit that needs its own brand, domain and administrators is the organisation.
Should you choose Brightspace or Lurno?
Brightspace is one of the strongest academic platforms available, and for a single university or district wanting deep term-based workflows, accreditation evidence and a long integration list, it remains a sound choice. Lurno suits an operator running several organisations rather than one: a school group, a K-12 publisher, a training provider selling to client companies. Lurno is multi-tenant to the root — one account holds nested sub-organisations, each with its own domain, branding, roles and administrators, while the parent keeps a view across them. Brightspace publishes no pricing and third-party benchmarks put institutional minimums around $10,000 to $15,000 a year, which assumes one institution; Lurno publishes four tiers from $119 a month with the member and sub-organisation caps beside each. Lurno's AI agents draft courses, suggest grades and assemble reports, and none of them can apply its own work. SCORM, xAPI and LTI 1.3 runtimes are in development at Lurno, so plan around that if your library is already packaged.
- Organisation-shaped versus term-shaped
- A term-shaped platform assumes a course with a start date, a roster and a transcript at the end. An organisation-shaped one assumes a tree: companies, campuses or departments that each need their own administrators, branding and reporting boundary, with learning happening inside them on whatever schedule suits. Continuing education, client academies and compliance training rarely fit a term.
What decides this one
The rows an operator running more than one organisation argues about.
| Capability | Lurno | D2L Brightspace |
|---|---|---|
| The unit it is built around | The organisation — a tree of them, each with its own administrators | The course, inside one institution |
| Running many organisations | Nested sub-organisations, each with domain, branding and roles | Multi-tenancy exists at the institution level |
| Published pricing | Four tiers, on the [pricing page](/pricing) | None published |
| Entry point | $119 a month, up to 1,000 members | Third-party benchmarks put institutional minimums around $10,000–$15,000 a year |
| When you learn the price | Before the first call | After a sales cycle |
| Learning outside a term | The default — compliance, onboarding and client academies run continuously | Possible, but the model assumes a term |
| AI agents | Draft courses, suggest grades, assemble reports — and hand every one to a person | AI features across the suite; check what runs unattended |
| Guardians and parents | Built in, scoped by data category | Available; strongest in the K-12 configuration |
| Getting set up | Your own administrators, in the admin interface | Institutional deployment, typically with services |
| Accreditation and term workflows | Competency frameworks with evidence; not term-modelled | Deep — this is the home ground |
| SCORM, xAPI, LTI | In development | Supported |
Three differences you would notice in the first month
Add a campus without adding a contract
A new school, client company or department is a node in the tree. It gets its own branding, its own web address and its own administrators, and it inherits what the parent set unless it overrides. The parent reports across all of them without logging into each.
- Nested organisations, not portals inside one institution
- Administrators scoped to their own node
- One account, one contract, one place to look
Learning that does not wait for a term
Compliance training starts when someone joins. A client academy opens when the contract signs. Onboarding runs continuously. None of that maps onto a semester, and a platform that assumes one makes you work around it.
- Enrolment when it is needed, with due dates and recertification
- Overdue compliance reported as a backlog, not a grade book
- Certificates that expire and re-issue on their own interval
A number before the discovery call
Brightspace does not publish pricing, and the institutional minimums quoted by third parties assume you are one institution. If you are five, the arithmetic is not obvious. Lurno's tiers are published with the caps next to them.
- $119, $299 and $599 a month, plus a quoted Institution tier
- Sub-organisation caps listed against each tier
- One contract covering the whole tree
Where Brightspace is the better choice.
If you are a single university or a district running degree programmes, Brightspace is the stronger platform and it is not close. Accreditation evidence, term-based workflows, gradebook depth, a long list of student-information integrations and years of institutional practice behind it — that is its home ground, and Lurno does not model a term at all. Brightspace also supports SCORM, xAPI and LTI today, where ours are in development, which matters if your library is already packaged or you launch tools into courses. The case for Lurno starts when the thing you are running is a group of organisations rather than one institution, and when learning has to happen outside a semester.
What running several organisations actually needs
Every organisation on its own domain
Its own web address, branding and sign-in page, so a learner never sees a platform name that is not theirs.
Administrators scoped to their node
A campus administrator manages their campus and cannot see into another. The parent sees across all of them.
Terminology you set
Rename what your people already say — section, class, programme — per organisation and per language.
Reporting that spans the tree
Ask a question in plain language and get a report scoped by the same permissions as everything else.
Guardians, scoped by data category
Parents see attendance without seeing wellbeing, or progress without seeing behaviour. Set per organisation.
An audit log that cannot be edited
Hash-chained and append-only, with access reviews, GDPR tooling and a FERPA addendum alongside it.
The rest of the shortlist
Before you book the call
Bring your org chart to the demo.
Show us how your campuses or client companies nest, and we will build that tree in front of you on the call.