Skip to main content
Stacklane

Learning Management Systems, LTI 1.3, OneRoster, SCORM, built for the institution that has to defend the data.

Most LMS projects fail not because of the courseware engine but because of the integrations. Roster sync from the SIS, single sign-on from the IdP, gradebook write-back to the existing system, content launching from external tools. We build the integration layer first and the courseware UI on top of that.

What we build

  • LTI 1.3 as the courseware contract

    Tool providers launch into the LMS with LTI 1.3 (Deep Linking, AGS for grades, NRPS for rosters). The platform issues client credentials, manages key rotation, and exposes the standard endpoints. Schools onboard new tools without engineering involvement.

  • OneRoster sync as the rostering bus

    Daily delta sync from the SIS via OneRoster CSV or REST. Students, teachers, classes, and enrollments flow into the LMS without admin re-entry. Mid-year transfers propagate; end-of-year archival is a config change.

  • SCORM + xAPI tracking

    Legacy content lands as SCORM 1.2 or 2004; modern content emits xAPI to a learning record store. The platform reads both and presents a unified progress view so teachers don't ask 'which system was that course in'.

  • Multi-tenant institutions

    District, school, classroom, tenancy at three levels with admins per level. Branding, policies, and feature flags scope to the tenant. A district admin sees aggregate progress; a teacher sees their class.

  • Live + async with one timeline

    Live classes (via Zoom or LiveKit) and async assignments live on the same student timeline. Attendance from live sessions counts toward engagement metrics; recordings post automatically with auto-generated transcripts.

  • Accessibility built for the regulator

    WCAG 2.2 AA throughout, captioning baked into the video pipeline, keyboard navigation tested against real assistive tech. The next state accessibility audit is a regression check, not a re-engineering project.

Where this fits

  1. You're building an LMS and the SIS integration matrix is starting to look like the actual product.

  2. Your existing LMS is monolithic and the institution can't move to modern courseware tools without ripping out the whole system.

  3. A state accessibility regulator is auditing your platform and the current implementation isn't going to pass.

Tech stack

  • TypeScript
  • Postgres
  • LTI 1.3
  • SCORM
  • OneRoster

Want this for your team?

30 minutes with a founder or senior engineer. We'll scope what you need and tell you straight whether Stacklane fits.

Book a Free Call