Build
Connect & operate
Design & teams
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Book a scoping call
AI software
LLM & data systems
Vibe coding
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Plan smarterEstimate before you commitCost ranges, scope templates, and the questions we ask in discovery — free, no form.Open the cost calculator
Real conversationsTalk with a technical leadNo SDR, no discovery gauntlet. The person on the call is the one who scopes the build.Book a call
Open-Source CMS · learnhouse

learnhouse

LearnHouse is an open-source learning management platform built with Next.js/React and FastAPI/Python, offering course creation, interactive content editing, real-time collaboration, code execution, and AI-powered features. It supports self-hosting via CLI and includes analytics, certificates, discussions, and podcast management.

Source: GitHub — github.com/learnhouse/learnhouse
1.8k
GitHub stars
394
Forks
TypeScript
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorylearnhouse/learnhouse
Ownerlearnhouse
Primary languageTypeScript
LicenseAGPL-3.0 — OSI-approved
Stars1.8k
Forks394
Open issues17
Latest release1.3.1 (2026-07-06)
Last updated2026-07-07
Sourcehttps://github.com/learnhouse/learnhouse

What learnhouse is

Full-stack TypeScript/Python application with Next.js frontend, FastAPI backend, PostgreSQL/Redis infrastructure, real-time WebSocket collab server (Hocuspocus/Yjs), block-based editor (Tiptap), code execution sandbox (30+ languages), and integrations with Stripe, AWS S3, Google Gemini, and LlamaIndex for AI features.

Quickstart

Get the learnhouse source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/learnhouse/learnhouse.gitcd learnhouse# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Self-hosted corporate or institutional learning platforms

Organizations needing full control over infrastructure, user data, and customization can deploy LearnHouse on-premise with multi-org support (enterprise), SSO, and role-based access control.

Interactive technical education with live code execution

Educators teaching programming or data science can leverage auto-grading, code playgrounds with 30+ language support, and AI-generated interactive elements for hands-on learning.

Community-driven open content platforms

Startups or nonprofits building public course catalogs can use the open-source base, headless API, custom branding, and SEO optimization to create differentiated learning experiences without vendor lock-in.

Implementation considerations

  • AGPL-3.0 license requires that any modified or hosted version disclose source code and grant downstream users the same freedoms. Review legal implications if you plan to build proprietary extensions.
  • Self-hosting via CLI is documented, but operational complexity (PostgreSQL, Redis, Docker, backups, monitoring) requires dedicated DevOps or infrastructure team.
  • AI features (Gemini, LlamaIndex) require external API credentials and will incur recurring costs; pricing and rate limits are not specified in data.
  • Real-time collaboration server (Collab) adds architectural complexity; ensure WebSocket scalability and failover strategy for production deployments.
  • Code execution sandbox (30+ languages) implies security sandboxing logic; audit and test thoroughly before exposing to untrusted user input.

When to avoid it — and what to weigh

  • Requiring proprietary or closed-source guarantees — LearnHouse is AGPL-3.0 licensed. Any modifications or hosting of custom versions must remain open-source. If you need closed-source derivatives, this is not suitable.
  • Seeking rapid enterprise SaaS with minimal operational overhead — Self-hosting requires DevOps expertise (Docker, PostgreSQL, Redis, reverse proxy). No official managed cloud offering described. Setup and maintenance are non-trivial.
  • Need for battle-tested, production-grade stability with long-term support SLA — Project is 4 years old with moderate activity (1.3.1 released mid-2026, 17 open issues). Single maintainer (Sweave) noted. Production readiness and support commitments are Unknown.
  • Heavy reliance on proprietary third-party LMS integrations — Limited integration ecosystem described. Custom integrations with existing SCORM, Canvas, or Moodle systems are not mentioned and would require custom development.

License & commercial use

AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license requiring source code disclosure of any modifications and network-accessible deployments. Commercial use is permitted under AGPL terms, but you must offer source access to users. Modifications must remain open-source.

AGPL-3.0 permits commercial use, but with strict conditions: any modified or hosted version must disclose source code and grant users identical freedoms. A commercial SaaS using custom LearnHouse code requires either: (a) open-sourcing modifications, or (b) obtaining a separate commercial license from the maintainer (not mentioned as available). Legal review is strongly recommended before proceeding.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityHigh
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Project includes security reporting policy ([email protected]), which is a positive signal. Considerations: (1) Code execution sandbox (30+ languages) must isolate user code; audit isolation and resource limits. (2) AGPL disclosure requirement means source code and modifications are visible to attackers; ensure no secrets in git history. (3) PostgreSQL and Redis must be secured (network access, credentials, updates). (4) OAuth/SSO (enterprise feature) security depends on implementation; verify token handling and scope restrictions. (5) AI integrations (Gemini, LlamaIndex) send data to external APIs; check data handling agreements. No security audit report, vulnerability history, or penetration test results provided in data.

Alternatives to consider

Moodle

Mature, widely deployed LMS with 20+ years of history, extensive plugin ecosystem, and institutional support. GPL-licensed but larger community. Steeper learning curve for content creation but battle-tested for scale.

Open edX

Open-source platform (AGPL) developed by edX and community. Stronger enterprise/MOOC features, xAPI support, and bigger ecosystem. More complex deployment and maintenance; requires Python/Django expertise.

Teachable or Thinkific (SaaS)

Proprietary SaaS with minimal ops overhead, strong UX, built-in payments, and email support. No self-hosting or code ownership, recurring fees. Better for small creators who prioritize ease-of-use over control.

Software development agency

Build on learnhouse with DEV.co software developers

Review our implementation guide, connect with our architects to assess AGPL compliance and DevOps readiness, and plan a proof-of-concept deployment.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

learnhouse FAQ

Can I use LearnHouse commercially?
Yes, AGPL-3.0 permits commercial use. However, if you host or modify LearnHouse, you must offer source code access to users and respect copyleft terms. Building proprietary extensions requires either open-sourcing them or obtaining a separate commercial license (status Unknown).
Do I need to self-host, or is there a managed SaaS option?
No official managed SaaS is described. LearnHouse is designed for self-hosting via CLI (Docker-based). You are responsible for infrastructure, updates, backups, and operations. Enterprise features (Payments, SSO, Multi-Org) are available in self-hosted deployments.
What payment options does LearnHouse support?
Stripe integration is mentioned as an enterprise feature. Other payment gateways (PayPal, Razorpay, etc.) are not documented. Implementation status and scope of the payment module require clarification.
Is LearnHouse suitable for SCORM or xAPI standards?
Not mentioned in available data. If your institution requires SCORM compliance, xAPI tracking, or interoperability with Moodle/Canvas, you must verify LearnHouse support or plan custom development.

Build it with a software development company

Pairing learnhouse with the rest of your stack is where most open-source cms projects stall. DEV.co is a software development agency that does the integration work — plus AI development when models are in scope.

Ready to evaluate LearnHouse for your learning platform?

Review our implementation guide, connect with our architects to assess AGPL compliance and DevOps readiness, and plan a proof-of-concept deployment.