Self-hosted learning management, honestly reviewed. No marketing fluff, just what you get when you deploy it yourself.

TL;DR

What it is: Open-source (AGPL-3.0) learning management platform — create, sell, and manage online courses with a block-based editor, AI features, real-time collaboration, and code execution in 30+ languages [README].
Who it’s for: Independent course creators escaping Teachable/Kajabi bills, educators who want data ownership, agencies building white-label academies for clients, and developers who want a modern Next.js/FastAPI LMS they can extend [homepage].
Cost savings: Teachable starts at $29/mo (they take 5% of sales on the basic plan), Thinkific at $36/mo, Kajabi at $119/mo. LearnHouse self-hosted runs on a $5–15/mo VPS with no platform fees and no per-student pricing [homepage].
Key strength: The feature-to-maturity ratio is unusual. At 1,332 GitHub stars, LearnHouse ships real-time collaborative boards, live code execution with auto-grading, podcast hosting, AI playgrounds, and a CLI setup wizard — features you’d expect from a tool with 10x the community [README].
Key weakness: The AGPL-3.0 license is a real constraint for commercial deployments: if you embed LearnHouse in a SaaS product you sell, AGPL requires you to open-source that product. The truly enterprise-useful features — SSO, payments, SCORM importing, RBAC, multi-tenancy, white-labeling — are gated behind an Enterprise plan with no public pricing [README][homepage].

What is LearnHouse

LearnHouse is a learning management system (LMS) built on Next.js, FastAPI, and PostgreSQL. The core pitch is that it replaces the Teachable/Thinkific/Kajabi tier of course creation platforms with something you actually own — no platform fees, no vendor lock-in, no monthly bill that scales with your revenue [homepage].

What separates it from older self-hosted alternatives like Moodle is the tech stack and the editor. The content editor is block-based — the README describes it as “Notion-like” — and you can mix text, video, code blocks, quizzes, and file uploads on a single page [README]. The runtime is modern: Next.js 14 on the frontend, FastAPI on the backend, Yjs for real-time collaboration, Tiptap for the editor, CodeMirror for code execution, and Redis for presence/sessions [README].

The project is self-described as “The next-gen open-source platform for world-class educational content” on GitHub, which is marketing-speak, but the README’s feature list is unusually complete for a 1,332-star project. It launched a CLI management tool (npx learnhouse@latest setup) that handles deployment, updates, backups, and diagnostics — which is a better operator experience than most tools at this star count offer [README].

The company behind it offers a managed cloud and sells an Enterprise plan. The open-source core is AGPL-3.0 licensed, not MIT, which matters for how you can use it commercially [README].

Why people choose it over Teachable, Kajabi, and Moodle

Independent third-party reviews of LearnHouse specifically are sparse at the time of writing — the project hasn’t yet reached the visibility tier where review sites like Capterra or G2 have substantial user feedback. That’s itself a signal: this is an early-stage tool, not a mature market leader. What follows draws primarily from the README, official website, and the established patterns of how tools in this category compete.

Versus Teachable and Thinkific. The clearest case. Both platforms take a percentage of sales (Teachable’s basic plan takes 5%), have student count limits, and give you no access to your own data — it lives on their servers. LearnHouse self-hosted takes 0% of sales, has no student limits, and your course content sits in a PostgreSQL database you control [homepage][README]. The trade-off is operational responsibility.

Versus Kajabi. Kajabi is the premium end of this market — $119/mo to start, but it includes email marketing, landing pages, and a polished course player. LearnHouse is competing on price and data ownership, not feature parity in marketing tools. If you’re using Kajabi primarily for its email sequences and funnels, LearnHouse doesn’t replace those directly without integrations [homepage].

Versus Moodle. Moodle has been around since 2002, has 1,800+ plugins, and is used by universities and enterprises worldwide. It’s also a PHP monolith that requires a Moodle administrator to run well and has a UI that looks like 2008. LearnHouse’s tech stack (Next.js, FastAPI, TypeScript) is more approachable for developers, the editor is significantly better, and the setup experience is not comparable. Moodle requires a LAMP stack and manual configuration; LearnHouse requires npx learnhouse@latest setup [README].

Versus Open edX. Used by MIT, Harvard, and corporate training at scale. Operationally complex — running a production Open edX instance requires dedicated DevOps effort. LearnHouse is aiming at a much simpler operational profile while offering a similar course-centric model.

The honest summary: LearnHouse wins on setup simplicity, modern UX, and cost against commercial SaaS. It wins on developer experience and feature depth against old-school open-source (Moodle, Open edX). It loses on ecosystem maturity and community size compared to everyone in both categories.

Features: what it actually does

Core learning:

Block-based content editor: text, video, code blocks, quizzes, embeds, file uploads on one page [README]
Courses with structured modules and progress tracking [README]
Collections — bundle courses into curated packages [README]
Assignments with submission tracking [README]
Auto-grading code in 30+ programming languages via real execution (CodeMirror + sandbox) [README]
Certificates generated on course completion [README]
Discussions/community forums for learners [README]

Collaboration and real-time:

Collaborative whiteboards (Boards) powered by Yjs for real-time sync [README]
AI Playgrounds — AI-generated interactive simulations and diagrams [README]
Podcasts — host audio content, distribute to Apple Podcasts and Spotify [homepage]

AI features:

Context-aware AI study assistant for learners [README]
AI content generation assistance for course creators [README]
AI Playgrounds for interactive learning elements [README]

Platform and ops:

REST API for custom frontends and integrations [homepage][README]
CLI with start, stop, update, backup, doctor, and logs commands [README]
Built-in SEO: metadata, sitemaps, open graph [README]
19 languages supported out of the box [homepage]
User Groups for organizing learner cohorts and access control [README]
Analytics for engagement and course performance [README]
Integrations: YouTube, Vimeo, Loom, Figma, Stripe, Google Analytics, Notion, Slack, Zoom, Calendly, Mailchimp, and 20+ others [homepage]

Enterprise tier (not in open-source core):

Payments — sell courses with 0% platform fees (via Stripe, 40+ countries) [homepage]
SSO/OIDC — single sign-on with your identity provider [homepage][README]
Multi-tenancy — multiple isolated organizations from one instance [homepage][README]
RBAC — fine-grained roles and permissions [homepage]
SCORM importing — bring existing courses in without rebuilding [homepage]
White-labeling — fully custom branding [homepage]
Audit logs [homepage]
SLA and priority support [homepage]

The payment and SSO gating is the most consequential limitation. If you’re building a paid course business, Payments being Enterprise-only means you need either the Enterprise plan or you wire Stripe directly yourself outside LearnHouse’s UI. SSO being Enterprise-only is standard for the LMS category but worth noting for teams already on Okta or Google Workspace [README][homepage].

Pricing: SaaS vs self-hosted math

LearnHouse Cloud:

Free plan: free forever [homepage]
Paid plans: pricing not publicly listed — the website says “transparent plans for every scale” but routes you to a Get Started flow rather than a pricing page. Data not available for specific tier costs at time of writing.
Enterprise: contact sales [homepage]

Self-hosted (AGPL-3.0 core):

Software: $0
VPS to run it: $5–15/mo on Hetzner, Contabo, or DigitalOcean depending on instance size
PostgreSQL and Redis: bundled in the Docker setup
Payments and SSO: require Enterprise license — price unknown without talking to sales

What you’re replacing:

Platform	Starting price	Platform fee	Student limit
Teachable Basic	$29/mo	5% per sale	Unlimited
Thinkific Basic	$36/mo	0%	1 community
Kajabi Basic	$119/mo	0%	50 products
Podia Mover	$39/mo	0%	Unlimited
LearnHouse self-hosted	~$10/mo VPS	0% (Payments gated)	Unlimited

The math works if you’re running a real course business. A creator doing $2,000/mo revenue on Teachable Basic pays $29/mo subscription plus $100 in platform fees — $129/mo. LearnHouse self-hosted is $10/mo VPS plus whatever you pay someone to deploy it. If Payments aren’t gated for your use case (open courses, free content), the savings are straightforward. If you need to sell courses, the calculus changes until Enterprise pricing is known.

Deployment reality check

The CLI setup is the most interesting part of LearnHouse’s deployment story. One command:

npx learnhouse@latest setup

…walks you through domain, database, admin account, and optional features, then generates all config files and starts your instance [README]. The follow-on commands (start, stop, update, backup, doctor) are the kind of operator tooling that most self-hosted projects never build.

What you actually need:

A Linux VPS with at least 2–4GB RAM for a production instance
Node.js and npx (the CLI handles Docker orchestration for you)
A domain name and reverse proxy for HTTPS
PostgreSQL and Redis — bundled in the default setup [README]
An SMTP provider for email (invites, certificates, notifications)

What can go sideways:

The AGPL-3.0 license. If you’re a developer building a SaaS product on top of LearnHouse, AGPL requires you to release your source code. This is a real constraint that the MIT-licensed alternatives don’t impose. Read the license before you build a business on it.
Enterprise features are required for core monetization. If you want to sell courses through the platform’s built-in payment flow rather than embedding a Stripe payment link yourself, you need the Enterprise plan. Pricing is not public, which makes budget planning difficult.
Small community at 1,332 stars means fewer Stack Overflow answers, fewer community plugins, and more reliance on the core team’s responsiveness when you hit issues.
No independent production case studies available at time of review. Established tools like Moodle have years of documented production deployments from universities and enterprises. LearnHouse’s production track record is not yet well-documented publicly.

Realistic time estimate for a developer: 30–60 minutes to a working instance. The CLI genuinely reduces this compared to most self-hosted tools. For a non-technical founder: 2–4 hours with a guide, or hire someone for a one-time setup.

Pros and cons

Pros

CLI-first setup. npx learnhouse@latest setup is not a gimmick — having backup, update, doctor, and logs commands built into the tool is an operational maturity signal that most self-hosted projects skip entirely [README].
Code execution in 30+ languages. Real sandbox execution with auto-grading is a feature that costs extra on most commercial LMS platforms and is typically absent from open-source competitors. Having it in the core is genuinely differentiating [README].
Real-time collaboration. Yjs-powered collaborative whiteboards are infrastructure-level work, not a simple feature. Most course platforms don’t have this at all [README].
Modern tech stack. Next.js + FastAPI + TypeScript is a stack that developers recognize and can extend without learning legacy architecture [README].
Zero platform fees. Self-hosted means your $1,000/mo course revenue stays yours [homepage].
19 languages out of the box. Meaningful for non-English course creators [homepage].
AI features without vendor lock-in. AI playgrounds and study assistants run in your environment [README].

Cons

AGPL-3.0 is a real restriction. Not MIT. If you embed LearnHouse in a commercial product, you must open-source that product. This rules out using it as a white-label course engine inside a closed SaaS [README].
Core monetization is Enterprise-gated. Payments and SSO behind a paywall with unknown pricing makes it hard to budget for a paying-course use case [homepage][README].
Small community. 1,332 stars vs Moodle’s decades of ecosystem. Plugin library is not comparable. If you need something specific, you’re likely writing it yourself [README].
No public Enterprise pricing. “Talk to us” is not a pricing model you can plan around. Depending on the number, the self-hosted cost advantage may narrow significantly for teams needing SSO and payments [homepage].
Limited independent production evidence. No third-party reviews with production data at scale available at time of writing.
SCORM behind Enterprise. If you’re migrating from another LMS and have SCORM content, you need the Enterprise tier to import it [homepage].

Who should use this / who shouldn’t

Use LearnHouse if:

You’re a course creator paying $30–120/mo to Teachable or Kajabi and your content is ready — you want to own your data and cut the bill.
You’re an educator or small academy that offers free or community-funded courses and doesn’t need built-in payment flows.
You’re an agency building a white-label LMS for a client (with Enterprise licensing) and want a modern stack you can customize.
You’re a developer who wants a real-time, AI-capable LMS you can extend — the Next.js/FastAPI/TypeScript stack is approachable.
You’re comfortable with AGPL licensing or your use case doesn’t involve embedding LearnHouse in a product you sell.

Skip it (use Moodle or Open edX) if:

You need a 20-year ecosystem of plugins, integrations, and documented production deployments.
You’re a university or enterprise that needs SCORM compliance and LTI integration baked in at the open-source tier.
Your IT team only knows PHP.

Skip it (stay on Teachable or Thinkific) if:

You need built-in email marketing and funnels — LearnHouse doesn’t replace the broader creator marketing stack.
You have no technical support available and need to start selling courses this week.
Platform fees are irrelevant to your revenue volume.

Skip it (find an MIT-licensed alternative) if:

You’re building a SaaS product and need to embed a course engine without open-sourcing your app. AGPL makes LearnHouse unusable for this use case without a commercial license.

Alternatives worth considering

Moodle — The incumbent. PHP, complex, 1,800+ plugins, used by every university you’ve heard of. Battle-tested at scale, painful to operate and design around in 2026. Free (GPL).
Open edX — The enterprise open-source LMS, runs Harvard and MIT’s online programs. Kubernetes-scale ops requirement. Not for solo founders or small teams.
Teachable — The easiest SaaS path. $29/mo starter with 5% platform fees. No ops overhead. You’re renting the platform.
Thinkific — Similar to Teachable, slightly more generous free tier, 0% platform fees on paid plans, still fully SaaS.
Kajabi — Premium all-in-one: LMS + email marketing + landing pages + community. $119/mo+. The right call if you’re treating course creation as a serious business and need the full stack without stitching tools together.
Podia — Cheaper Kajabi alternative at $39/mo, simpler feature set. No ops.
Canvas (Instructure) — SaaS/self-hosted hybrid, popular in US higher education, not designed for independent creators.

For a non-technical founder escaping Teachable/Kajabi: the realistic shortlist is LearnHouse vs staying on SaaS. LearnHouse wins on cost and data ownership. SaaS wins on reliability, support, and zero ops. The decision point is how much you value owning your infrastructure vs. the operational burden of maintaining it.

Bottom line

LearnHouse is a better-than-expected tool at its current stage. The CLI setup, real-time collaboration, code execution, and AI features are not what you expect from a 1,332-star project, and the modern stack makes it something developers can actually extend. For a course creator paying Kajabi prices who has even one technical contact they can call for a deploy, the economics are obvious.

The constraints are real: AGPL-3.0 limits commercial embedding, the enterprise features (payments, SSO, multi-tenancy, SCORM) that make it a full platform replacement sit behind undisclosed pricing, and the community is small enough that you’ll be early. If you need production references and a 10-year plugin ecosystem, Moodle is still the answer. If you need to start selling courses tomorrow without touching a terminal, stay on Teachable.

But if you’re building an online academy and want to own the infrastructure, the data, and the destiny of the platform — and you can afford one afternoon of setup — LearnHouse is the most credible open-source option in this category right now that doesn’t require a DevOps team to operate.

If the deployment step is the blocker, that’s exactly what upready.dev deploys for clients. One-time fee, you own it from day one.

Sources

Primary sources (used throughout):

LearnHouse GitHub Repository and README — https://github.com/learnhouse/learnhouse (1,332 stars, AGPL-3.0, CLI-based deployment documentation, full feature list)
LearnHouse Official Website — https://www.learnhouse.app (homepage, feature descriptions, integration list, enterprise feature list)
LearnHouse Enterprise Page — https://www.learnhouse.app (Enterprise tier feature gating: SSO, RBAC, SCORM, multi-tenancy, payments, white-labeling)

Competitor pricing references: