Skip to content

Cloud vs Self-Hosted

Kitbase is available as a fully managed cloud service or as a self-hosted deployment you run on your own infrastructure. Both options use the same codebase and offer the same core analytics and feature flag capabilities.

Comparison

FeatureCloudSelf-Hosted
PricingFree tier + paid plansFree forever
Usage limitsBased on planUnlimited
SetupInstant — no infrastructure neededDocker Compose on your server
HostingManaged by KitbaseYour own infrastructure
Maintenance & updatesAutomaticManual (docker compose pull)
SSL certificatesIncludedAuto-provisioned via Caddy
Data locationKitbase-managed serversYour servers, your jurisdiction
Product analytics
Feature flags
Custom events
Autocapture
Session tracking
User identification
Webhooks
API access
All SDKs
Team membersBased on planUnlimited
ProjectsBased on planUnlimited
Social login (Google, GitHub)
Slack integration
Email deliveryBuilt-inBring your own (SMTP, SES, or Resend)
Uptime SLAAvailable on paid plansDepends on your infrastructure
SupportEmail + priority on paid plansCommunity / self-service
BackupsManaged automaticallyYour responsibility
ScalingHandled by KitbaseYou manage scaling
Database accessNo direct accessFull access to MySQL + ClickHouse

When to choose Cloud

  • You want to get started quickly with zero infrastructure
  • You prefer a managed service with automatic updates and backups
  • You need social login (Google / GitHub) for your team
  • You want built-in Slack notifications
  • You don't want to manage databases, servers, or SSL

When to choose Self-Hosted

  • You need unlimited events, users, and projects with no usage caps
  • Data residency or compliance requirements mandate hosting in a specific region
  • You want full control over your infrastructure and data
  • You need direct access to the underlying databases
  • You want to run Kitbase inside your private network

Getting started

Released under the MIT License.