Skip to Content
Edit on GitHub

Cloud vs Self Hosting

LearnHouse is open-source software. You can use the managed LearnHouse Cloud platform or deploy the Community Edition on your own infrastructure. This page explains the differences so you can make an informed choice.

Comparison

☁️ LearnHouse CloudπŸ–₯️ Self Hosting
🌍 Worldwide CDNβœ… Includedβš™οΈ Manual setup + additional cost
πŸ”„ Weekly updatesβœ… AutomaticπŸ”§ Manual
πŸ› οΈ Maintenanceβœ… Managed by the LearnHouse teamπŸ‘€ Your responsibility
πŸ”’ Security patchesβœ… Applied automaticallyπŸ”§ Manual
πŸ“Š Threat & uptime monitoringβœ… Included❌ Not included
πŸ” SSL certificateβœ… IncludedπŸ”§ Manual
πŸ’Ύ Continuous backupsβœ… Includedβš™οΈ Manual + additional cost
πŸ“ˆ Scalabilityβœ… Automaticβš™οΈ Depends on your provider
πŸ–₯️ Direct SSH & DB access❌ Not availableβœ… Full access
🎧 Product supportβœ… Email supportπŸ‘₯ Community support
πŸ’š Where your money goesβœ… Supporting the team and funding new features🏒 Third-party hosting companies

☁️ When to choose LearnHouse Cloud

Best for: teams, organizations, and businesses that want to focus on content and learners β€” not infrastructure.

  • Launch in minutes β€” no servers to provision, no DevOps overhead. Your team can start building courses immediately.
  • Zero-maintenance operations β€” updates, security patches, SSL certificates, and backups are handled automatically by the LearnHouse team.
  • Enterprise-grade reliability β€” global CDN, threat monitoring, uptime guarantees, and automatic scaling out of the box.
  • Priority support β€” dedicated email support with faster response times for production issues.
  • Invest in the product β€” your subscription directly funds development of new features and improvements for the entire LearnHouse ecosystem.

LearnHouse Cloud is the recommended option for most organizations. It eliminates operational complexity and lets your team focus entirely on creating great learning experiences.

πŸ–₯️ When to choose Self Hosting

Best for: enterprises, institutions, and teams with strict infrastructure requirements and dedicated engineering resources.

  • Full data sovereignty β€” host on your own infrastructure with complete control over where data lives. Ideal for organizations with data residency mandates.
  • Regulatory compliance β€” meet on-premises hosting requirements for HIPAA, SOC 2, internal security policies, or government regulations.
  • Deep infrastructure access β€” direct SSH, database access, and full control over networking, storage, and compute resources.
  • Custom integrations β€” connect to internal systems, private networks, SSO providers, and proprietary tooling without restrictions.
  • Dedicated engineering teams β€” organizations with DevOps or platform engineering teams that prefer to own their deployment pipeline.

Self hosting requires your team to manage updates, backups, security patches, and scaling. Make sure you have the engineering capacity before choosing this path.

Both options give you access to the same core feature set. Self-hosted instances can be upgraded at any time by pulling the latest release from the Community Edition repositoryΒ .

Next steps