Teleport Enterprise Self-Hosted

Commercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Teleport Helm charts on EKS, AKS or GKE; official Terraform deployment paths are also documented

  2. Operated by

    Your team

    Customer manages Kubernetes or VMs, backend state, storage, DNS, TLS, upgrades, capacity, backups and the Enterprise license.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Teleport Enterprise on AWS EKS ↗ · Source checked 2026-11-18

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Teleport Enterprise on Azure AKS ↗ · Source checked 2026-11-18

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Teleport Enterprise on Google GKE ↗ · Source checked 2026-11-18

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodTeleport Helm charts on EKS, AKS or GKE; official Terraform deployment paths are also documented
InfrastructureServers / containers
Teleport runs persistent authentication and proxy services with provider-backed state and network dependencies.
Licensing modelCommercial Only
The selected Enterprise Self-Hosted edition requires a commercial subscription and license file.
LicenseCommercial Teleport Enterprise Self-Hosted subscription and license file required.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 9 documented · 3 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

Teleport’s Marketplace announcement describes cloud or self-hosted deployment, but the linked current AWS offer prodview-fnmgbsyr3kwko prices its dimension as Cloud only and excludes support. It does not establish self-hosted licence terms. Obtain a self-hosted order/private-offer identifier, entitlement and support terms rather than transferring the public Cloud price to this deployment.

Current linked public AWS offer versus separately negotiated Enterprise Self-Hosted entitlement · Source ↗ · Broader vendor Marketplace announcement ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

The linked AWS public offer prices Cloud only; it does not establish eligible spend for Enterprise Self-Hosted. Confirm a self-hosted private offer, its billed entitlement/support dimensions and the buyer’s applicable AWS commitment terms. Do not transfer the public Cloud offer’s procurement or credits to a self-hosted order.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · AWS commitment qualification is product/agreement-specific ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The feature matrix assigns SAML and OIDC SSO to Enterprise Self-Hosted. Configure the IdP connector, roles and login policy; the Community GitHub-login option is a separate edition boundary.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

Teleport Enterprise Identity Governance documents SCIM 2.0 for users/groups with SAML SSO, OAuth client credentials and matching Access Lists. It requires v17.6.1 or v18.0.3+; the IdP pushes changes into Teleport, not the reverse. Confirm the Identity Governance entitlement and tested deactivation/session-lock behavior.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Compliance attestations
Edition-dependentEvidence and scope for Compliance attestations

Teleport’s v18.11.10 documentation identifies BoringCrypto fips-20220613, CMVP 4735, in Enterprise FIPS builds from 17.7.3/18.0.0. NIST lists the FIPS 140-3 Level 1 module as active, with a July 22, 2029 sunset and approved-mode/tested-configuration conditions. This validates the cryptographic module, not Teleport as a whole, every OS/CPU combination or a customer’s FedRAMP authorisation.

Enterprise FIPS-build cryptographic-module boundary; operating environment and approved-mode conditions still require assessment · Source ↗ · NIST module status, caveats and tested configurations ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The chart separates Auth/Proxy services and configures TLS, backing storage and Enterprise licence secrets. Avoid treating standalone local storage as HA. Authentication, roles, short-lived certificates, audit/session storage and backup protection need an explicit deployment policy.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · HA scaling and service separation ↗ · Identity governance provisioning controls ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation

Teleport explicitly supports fully air-gapped clusters, including privately reachable Auth and Proxy services. Enterprise uses a local licence file. Automatic licence updates require api.teleport.sh, but the cluster continues without that access while its local licence remains valid. Transfer renewed licences and release artifacts deliberately, and provide internal IdP, DNS, certificates, audit/storage backends and client access.

Fully self-hosted Teleport Enterprise with a valid local licence and internally reachable dependencies · Source ↗ · Offline licence behavior and expiry boundary ↗ · Vendor statement of air-gapped self-hosting ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream teleport-cluster Helm chart configures Enterprise images using enterprise: true and a customer licence secret. The reviewed chart source is pinned to v18.11.10. Follow the separate EKS/AKS/GKE backend and network configuration guides.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · Deployment artifact ↗ (Teleport v18.11.10 chart source) · Reviewed 2026-11-18

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

Teleport publishes an illustrative HA configuration for up to 10,000 SSH nodes: two Proxy instances at 4 vCPU/8 GB and two Auth at 8 vCPU/16 GB, with appropriate external storage. It is a scale example, not the minimum for 100 users. Kubernetes API request rate, sessions, registered clusters and recording volume require measurement.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The June 16, 2026 Enterprise guide bills Monthly Active Users and Teleport Protected Resources, with Standard/Premium feature bundles; Priority Support is included for self-hosted deployments. It publishes metric definitions, not numeric rates. Request a self-hosted quote with protected resources, machine identities and entitlements; public Cloud Marketplace prices are not self-hosted rates.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · Public offer explicitly prices Cloud only ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

The current pricing guide defines MAUs and hourly/monthly averaged Protected Resources but gives no rates. One hundred internal users is at most a user assumption, not a resource or machine-identity count; 1 TB is not a session-recording retention model. Supply MAUs, protected resources/bots, recording volume/retention, auth/proxy/backend HA design and a self-hosted licence quote before completing the AWS us-east-1 budget.

Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput · Source ↗ · Self-hosted topology and backend sizing ↗ · Current AWS Linux EC2 rates; workload/topology still required ↗ · Storage performance and charging inputs ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Teleport v18.11.10 was published November 16, 2026. Match Enterprise images, cluster chart, clients and Terraform provider to the supported upgrade path. Community repository publication does not itself establish the buyer’s commercial support term.

Teleport Enterprise Self-Hosted: selected customer-operated edition · Source ↗ · Teleport application change log ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

This entry covers Enterprise Self-Hosted, not Teleport Enterprise Cloud. Community licensing and feature availability differ; confirm the purchased edition and current upgrade compatibility.

Category fit

Identity & access management
Provides identity-aware access to servers, Kubernetes, databases and applications through customer-operated authentication and proxy services.

Compare within Identity & access management

  • authentikIdentity provider for centralized authentication and access policies across connected applications.
    • AWS
    Customer-operated · Open Source / Open Core
  • FusionAuth Self-HostedProprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Render
    Customer-operated · Commercial Only
  • HashiCorp Boundary EnterpriseCommercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Infisical Self-HostedSelf-hosted secrets-management platform with application and machine-identity access workflows.
    • AWS
    • Google Cloud
    • Vultr
    Customer-operated · Open Source / Open Core
  • Keycloak Self-HostedIdentity and access management for application sign-on, federation and authorization.
    • AWS
    • Azure
    Customer-operated · Open Source / Open Core
  • NetBird Self-Hosted Community EditionOpen-source zero-trust networking control plane self-hosted on a customer cloud VM.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • DigitalOcean
    • Hetzner
    Customer-operated · Open Source / Open Core
  • OpenBaoFoundation-governed secrets, key and certificate management with a customer-operated server.
    • Linode
    Customer-operated · Open Source / Open Core
  • OpenVPN Access ServerSelf-hosted business VPN and network-access server deployed in the customer's cloud account.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only

Showing 8 of 10 other listings in Identity & access management. These products address related workflows; read their category-fit notes before comparing scope. See all of Identity & access management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Teleport Enterprise on AWS EKS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      Teleport documents a full HA Auth and Proxy deployment on customer EKS with AWS backing services.

    • Teleport Enterprise on Azure AKS ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      Teleport documents a full HA deployment on customer AKS.

    • Teleport Enterprise on Google GKE ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      Teleport documents a full HA deployment on customer GKE.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory