Your courses, your identity provider, your rules

Your Teachable library is years of work. Videos, PDFs, rich lesson copy, section structure — none of it belongs in a CSV export. Rebuilding by hand is a month of someone's life.

The import engine authenticates directly with your Teachable school, walks every course in your catalog, extracts the full curriculum hierarchy, downloads all media and documents from Teachable's CDN, re-hosts them on your new platform's asset storage, and replaces every original URL throughout the content — automatically.

• Catalog discovery first Browse all your Teachable courses before committing — select exactly which ones to import.

• Full content fidelity Headings, bold/italic, bullet lists, inline images, video embeds, and downloadable attachments all transfer intact.

• Asset deduplication Identical images shared across lessons are stored once, not ten times.

• Partial failure recovery One broken asset doesn't abort the whole job — the pipeline logs errors and completes with a partial-success status you can review.

• Live progress monitor Watch the pipeline move through each stage in real time. No refresh needed.

Not everything comes from a Teachable import. New programs need to be built — and instructors need a builder that doesn't slow them down with rigid forms or require a developer for every content change.

• Creation wizard A guided multi-step flow: title and description, thumbnail upload, first section — you're writing lessons in under two minutes.

• Drag-and-drop curriculum editor Reorder sections and lessons visually. Changes reflect immediately without a page reload.

• Rich text lesson editor Full WYSIWYG body: headings, lists, code blocks, inline images you paste or drag in — stored as structured JSON, not fragile HTML strings.

• Video embedding Paste a YouTube, Vimeo, Wistia, or Loom URL and the lesson player renders the embed automatically.

• Lesson attachments Upload PDFs and files directly to lessons — learners download them with signed, short-lived URLs that prevent unauthorized sharing.

• Publish controls with a pre-flight check A course won't publish until it has at least one published section and lesson — no accidentally empty catalogs.

Training providers and platform resellers host learning programs for multiple independent clients. Each client wants their own branding, their own SSO, their own learner directory — and they should never be able to see each other's data.

• True data isolation Every database query is scoped to the authenticated organization's ID — cross-tenant data leakage is architecturally prevented, not just access-controlled.

• Subdomain or path-prefix routing Each client gets acme.platform.com or /org/acme — resolved by middleware before the first query runs, with no per-tenant deployments.

• Per-tenant branding Each organization uploads its own logo and sets a primary brand color applied across the learner catalog and lesson player.

• Independent SSO per org Client A connects Okta, Client B connects Azure AD — configurations are isolated and don't interfere.

• Controlled org offboarding When a client contract ends, a confirmed deletion workflow queues a background job that purges all org data, assets, enrollments, and memberships — nothing lingers.