Files
kms/docs/self-hosting/overview.mdx
zeekay 0ebffbd529 fix: white-label KMS branding and fix broken identifiers
- Fix 381 files where branding script corrupted variable names
  (e.g. isHanzo KMSTemplate -> isKmsTemplate)
- Rebrand from "Hanzo KMS" to just "KMS" for white-label support
  (allows Lux KMS, Hanzo KMS, etc. via configuration)
- 856 files, purely string replacements, no logic changes
2026-02-13 10:25:11 -08:00

80 lines
2.3 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: ""
sidebarTitle: "Introduction"
description: "Learn how to self-host KMS on your own infrastructure."
---
Self-hosting KMS lets you retain data on your own infrastructure and network. Many organizations choose self-hosting for benefits in compliance and flexibility.
- Compliance: Deploying KMS in your own environment helps meet strict regulatory requirements (e.g. SOC 2, HIPAA, FIPS 140-3) by aligning with your existing security controls. All data remains under your governance, and KMS’s architecture supports compliance needs through strong encryption and access controls.
- Flexibility: You have complete control over deployment topology and integrations. KMS can run in diverse environments. From air-gapped bare-metal servers to Kubernetes clusters or cloud VMs, this flexibility lets you tailor networking, security, and performance configurations to fit your organization’s needs.
Choose from a number of deployment options listed below to get started.
<CardGroup cols={2}>
<Card
title="Docker"
color="#000000"
icon="docker"
href="./deployment-options/standalone-kms"
>
Use the fully packaged docker image to deploy KMS anywhere.
</Card>
<Card
title="Kubernetes"
color="#000000"
icon="kubernetes"
href="./deployment-options/kubernetes-helm"
>
Deploy KMS on Kubernetes using our Helm chart.
</Card>
</CardGroup>
<CardGroup cols={2}>
<Card
title="Docker Compose"
color="#000000"
icon="docker"
href="./deployment-options/docker-compose"
>
Install KMS using our Docker Compose template.
</Card>
<Card
title="Docker Swarm"
color="#000000"
icon="docker"
href="./deployment-options/docker-swarm"
>
Install KMS using our Docker Swarm template.
</Card>
</CardGroup>
<CardGroup cols={2}>
<Card
title="AWS"
color="#000000"
icon="aws"
href="./deployment-options/aws-native"
>
Deploy KMS on AWS using ECS with Fargate.
</Card>
<Card
title="GCP"
color="#000000"
icon="google"
href="./deployment-options/gcp-native"
>
Deploy KMS on GCP using GKE.
</Card>
</CardGroup>
<Card
title="Linux package"
color="#000000"
icon="linux"
href="./deployment-options/native/linux-package/installation"
>
Install KMS on your system without containers using our Linux package.
</Card>