Self-Hosting Teleport
These guides show you how to run a self-hosted Teleport cluster in production.
Getting started
Self-hosted Teleport Enterprise subscriptions require a valid license. We recommend reaching out to us directly to learn more about getting started with this deployment option and start planning your approach. Self-hosted Teleport Enterprise deployments typically take place in conversation with the team at Teleport.
While designing a deployment, you can consult the High Availability guide for the components of a production Teleport cluster.
Dedicated account dashboard
Teleport Enterprise subscriptions include a dedicated account dashboard with their preferred subdomain of teleport.sh. The dedicated account dashboard provides subscription administrators access to the license file, support links and Teleport Enterprise binary downloads.
Guides to self-hosting Teleport
- Enterprise License File: How to manage your Teleport Enterprise license file.
- Deployment Guides (section): Teleport Installation and Configuration Reference Deployment Guides.
- Helm Deployments (section): How to install and configure Teleport in Kubernetes using Helm
- Key Management (section): Provides information on managing Teleport private keys with a third-party service.
- Reliability (section): The guides in this section show you Teleport capabilities for ensuring the
- Self-Signed Certificates: This guide shows you how to run Teleport using self-signed certificates, which is helpful for testing or demo environments.
- TLS Routing Migration: How to upgrade an existing Teleport cluster to single-port TLS routing mode
- Trusted Clusters: Explains how you can configure a trust relationship and manage access between two Teleport clusters.