Product

LMS Platform

LMS Platform concept — academy hub with learning content and learner nodesAcademy hubAcademy coreMulti-tenant · role-based accessCoursesVideoQuizzesDocumentsLearners · instructors · tenant domains
In development

Conceptual illustration: academy core with content tiles and learner nodes.

A scalable learning platform architecture designed for academies and organizations with tenant-specific users, instructors, learners, content and domains.

In development — a conceptual product, not yet shipped. This page records direction, not available software.

Overview

Built to solve a real workflow problem.

The problem

Learning businesses often start with a single academy and course set, then grow into multiple programs, instructor teams, learner audiences and branded domains. Platforms built without tenancy in mind force every new academy to copy code, duplicate data or share permissions that should stay isolated.

Who it's for

This is scoped for academies and training organizations that need one platform boundary and many isolated tenants.

  • Academies running multiple brands, programs or learner segments
  • Training providers delivering recorded or video learning
  • Organizations with internal and external learning audiences

How it works

A multi-tenant academy model separates platform administration from tenant domains. Each academy gets tenant-specific users, instructors, learners and content, with tenant/domain isolation at the data and delivery layers. The architecture keeps shared platform services (auth, media, storage, analytics) while isolating ownership and permissions.

Primary audienceAcademies, training organizations and institutions that run several learner groups, courses and domains under one platform.

Capabilities

What the platform is built to do.

The parts of the system, and where each one sits in the process. Every capability here is part of one system rather than a separate tool.

  • Tenancy

    Multi-Tenant Academy Model

    Each academy is a tenant with its own users, instructors, learners and content, isolated at the data and delivery layers rather than sharing one namespace.

    • Tenant isolation
    • Data layer
    • Delivery layer

    Design direction

  • Access

    Instructor & Learner Roles

    Instructor and student roles with permission boundaries, held per tenant rather than shared across the platform.

    • Instructors
    • Learners
    • Permission boundaries

    Design direction

  • Content

    Recorded & Video Learning

    Courses, recorded learning and video content for a tenant's learners, with the media served from shared platform services.

    • Courses
    • Recorded
    • Video

    Design direction

  • Tenants

    Tenant Domains & Branding

    Each academy gets tenant-specific domains and branding, so several brands run on one platform rather than several copies.

    • Tenant domains
    • Branding

    Design direction

  • Administration

    Administration & Analytics per Tenant

    Administration and analytics per tenant, with tenant administration kept separate from platform administration.

    • Platform admin
    • Tenant admin
    • Analytics

    Design direction

  • Platform

    Cloud-Ready Architecture

    Scalable, cloud-ready architecture built on shared platform services rather than a copy per tenant, so a new academy does not duplicate data.

    • Shared services
    • No copied code
    • Tenant isolation

    Design direction

Workflow

How it works end to end.

One representative path through the system, in the order the stages run.

  1. Onboard tenant

    An academy is added as an isolated tenant with its own domain.

  2. Set up people

    Instructors and learners are created in that tenant with their own permission boundaries.

  3. Publish content

    Courses and recorded or video learning are added for that tenant.

  4. Deliver learning

    Learners reach that content inside the tenant boundary, on the tenant's own domain.

  5. Administer separately

    Platform administration stays apart from tenant administration, with analytics per tenant.

Conceptual view

How the platform is arranged.

The layers the capability set is built on, and the parts that sit in each one.

  1. Platform administration

    Where the shared platform is configured, apart from any tenant.

    • Platform settings
    • Shared services
    • Authentication
    • Media and storage
    • Analytics
  2. Tenant boundary

    Where each academy's ownership and permissions are kept isolated.

    • Tenant isolation
    • Ownership
    • Data layer
    • Delivery layer
  3. Tenant domains

    Where each academy is reached on its own domain.

    • Tenant domains
    • Branding
  4. People and roles

    Where instructors and learners exist inside a tenant.

    • Instructors
    • Learners
    • Permission boundaries
  5. Learning content

    Where a tenant's courses and media are held and delivered.

    • Courses
    • Recorded learning
    • Video learning

Conceptual only. These layers describe the intended structure of the product, not deployed infrastructure, and this page does not describe a shipped system.

Interested in the LMS Platform?

The LMS Platform is in development. Talk to us about early access, or about a related custom build.