August 18, 2026
AgentKit

Self-hosted Scalekit: run in your VPC or fully on-prem, air-gapped included

"Our data cannot leave our infrastructure" used to end the deal. Now you pick the boundary: managed by Scalekit, running in your own VPC, or fully on-prem including air-gapped environments. Same SDKs, same APIs, same integration you already wrote.

Some buyers cannot use shared cloud infrastructure, full stop. Regulated industries, government workloads, and data-residency mandates all reduce to the same requirement: the auth layer runs where they say it runs. Scalekit now deploys across that whole spectrum: fully managed, inside your VPC, or on-prem in air-gapped environments.

The integration does not change with the deployment model. The SDKs, APIs, and dashboard behave identically whether Scalekit runs in our cloud or inside a customer's private network, so the code you wrote against the managed service carries over unmodified when an enterprise deal demands a private deployment.

How it works

  • Choose the deployment boundary per environment: managed cloud, your VPC, or fully on-prem including air-gapped setups.
  • Bring your own KMS key and key policy, so encryption control travels with the deployment.
  • Pick US or EU data residency to satisfy regional requirements.
  • SDKs and APIs are identical across deployment models; no separate integration for self-hosted customers.

Talk to us to scope a self-hosted deployment.

Share on

Updates you might like

No items found.

Self-hosted Scalekit: run in your VPC or fully on-prem, air-gapped included

Some buyers cannot use shared cloud infrastructure, full stop. Regulated industries, government workloads, and data-residency mandates all reduce to the same requirement: the auth layer runs where they say it runs. Scalekit now deploys across that whole spectrum: fully managed, inside your VPC, or on-prem in air-gapped environments.

The integration does not change with the deployment model. The SDKs, APIs, and dashboard behave identically whether Scalekit runs in our cloud or inside a customer's private network, so the code you wrote against the managed service carries over unmodified when an enterprise deal demands a private deployment.

How it works

  • Choose the deployment boundary per environment: managed cloud, your VPC, or fully on-prem including air-gapped setups.
  • Bring your own KMS key and key policy, so encryption control travels with the deployment.
  • Pick US or EU data residency to satisfy regional requirements.
  • SDKs and APIs are identical across deployment models; no separate integration for self-hosted customers.

Talk to us to scope a self-hosted deployment.

Schedule a demo with Scalekit today.

More Related Posts