Skip to Content

Cloud vs Self Hosting

You can use the managed ZəkaHouse Cloud platform or self-host the platform on your own infrastructure using the ZəkaHouse CLI. This page explains the differences so you can make an informed choice.

Comparison

☁️ ZəkaHouse Cloud🖥️ Self Hosting
🌍 Worldwide CDN✅ Included⚙️ Manual setup + additional cost
🔄 Weekly updates✅ Automatic🔧 Manual
🛠️ Maintenance✅ Managed by the ZekaLab 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 ZəkaHouse Cloud

Best for: teams and organizations that want to spend their time on content and learners rather than 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 ZekaLab 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 ZəkaHouse ecosystem.

ZəkaHouse 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: institutions and teams with strict infrastructure requirements and engineers available to run the deployment.

  • Data sovereignty: host on your own infrastructure and decide where data lives. This matters for organizations with data residency requirements.
  • Regulatory compliance: meet on-premises hosting requirements for HIPAA, SOC 2, internal security policies, or government regulations.
  • Infrastructure access: direct SSH, database access, and full control over networking, storage, and compute.
  • Custom integrations: connect to internal systems, private networks, SSO providers, and proprietary tooling.
  • Your own pipeline: suits 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 with zeka-learnhouse update — see Updates for how upgrades work for a self-hosted deployment.

Next steps