Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Self-hosted deployment overview

Deploy Scalekit on your own Kubernetes cluster to meet data residency, compliance, and network isolation requirements.

Scalekit’s self-hosted deployment lets you run the full Scalekit platform on your own Kubernetes cluster. All authentication data stays within your infrastructure — nothing leaves your network.

Use self-hosted deployment when your organization requires:

  • Data residency: Auth data must remain in a specific region or on-premises location
  • Network isolation: The auth service must not be reachable from the public internet
  • Compliance: Regulations such as FedRAMP, HIPAA, or internal security policies prohibit use of SaaS auth services
  • Air-gapped environments: Your deployment environment has no outbound internet access

Scalekit is deployed on Kubernetes via a Helm chart managed through the Scalekit distribution portal. You configure the deployment with a values.yaml file, apply Kubernetes secrets to your cluster, and connect the cluster to the portal — which handles chart delivery, migrations, and upgrades.

A self-hosted deployment runs as a single Kubernetes Deployment with multiple containers:

ComponentDescription
Auth serviceCore service handling login, token issuance, sessions, SSO, and SCIM
DashboardAdmin web UI for managing your Scalekit instance
FlagdFeature flag sidecar for runtime configuration
WebhooksWebhook delivery service
OpenFGAFine-grained authorization engine (optional)

Scalekit does not bundle a database or cache in production. You provision and manage these separately:

DependencyRequirementNotes
Kubernetes1.27 or laterAny managed or self-managed cluster
PostgreSQL15 or laterThree databases required: scalekit, webhooks, openfga
Redis6.2 or laterUsed for sessions, caching, and job queues
SMTPAny providerPostmark and SendGrid have first-class support
PathWhen to use
Quick startGet Scalekit running fast using bundled PostgreSQL and Redis. Ideal for evaluation and proof-of-concept. No external databases or kubectl secret commands needed.
Full installationProduction deployment with external PostgreSQL and Redis, full secret management, and your choice of ingress controller.