The server side of your interactive content.

The backend layer of the CDK — a self-hostable Node service that stores, searches, and delivers your content through a clean REST API, with LTI 1.3 and Google Classroom integrations built in.

Node + REST

A Node server with a REST API at its core.

It runs on modern Node and exposes everything as REST endpoints — content, media, identity, tracking — so any client or stack can talk to it.

Modern Node runtime

Built for Node 22+ with native ESM. Ship it with Docker or run it on any host — no exotic infrastructure required.

REST API

Documents, media streams, identity, xAPI statements, oEmbed and AI endpoints — every capability is a plain REST route you can call from anywhere.

Modular by design

Each group of endpoints mounts independently and talks to storage through repository interfaces — enable what you need, replace what you want.

Your infrastructure

Self-host it on your own servers and keep full control of your data — it deploys and scales like any other Node service.

Data layer

PostgreSQL as the single source of truth.

Everything the backend stores lives in Postgres: documents, media metadata, users, and results — one battle-tested database that also powers search.

  • One database for everything

    Content, asset metadata, identity, and xAPI results share a typed schema with versioned migrations.

  • Search built in

    Full-text search across your modules runs directly on Postgres — no separate search engine to deploy, sync, or pay for.

  • Proven operations

    Backups, replication, and scaling are standard Postgres practice — use a managed database or run your own.

Integrations

Speaks LTI and Classroom natively.

Backend connects your content to the platforms where teaching happens — as an LTI 1.3 tool inside any LMS, and directly with Google Classroom.

LTI 1.3

Deliver your modules inside any LTI-compatible LMS, with identity flowing from the platform.

  • Launch modules inside Moodle, Canvas, and any LTI 1.3 platform.
  • Users arrive signed in — identity comes from the LMS.
  • Acts as tool or platform, with key management handled for you.

Google Classroom

Bring courses and people in, push assignments out, and read submissions back.

  • Import courses and rosters — students and teachers.
  • Create coursework linked to your modules.
  • Read submissions back to track completion and results.

Get in touch

Questions about features, pricing, or workflows?

Product of interest