Teleport

Teleport is an open-source access management platform that gives IT and DevOps teams secure connectivity, single sign-on, access controls, and audit logging…

  • Network Services
  • Other
  • Security
  • Tools & Utilities
Teleport is an open-source access management platform that gives IT and DevOps teams secure connectivity, single sign-on, access controls, and audit logging for servers, Kubernetes clusters, databases, desktops, and web applications.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
94last commit 88 days ago
Popular
8621,055 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
21,055
Open issues
3245
Last commit
2026-08-25
Latest release
v18.10.0
License
AGPL-3.0
Activity
stale

Checked 21 days ago - source: GitHub (gravitational/teleport)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Configure Teleport before you start it After installing the `teleport` package, set your cluster's public proxy address (the cluster's public access point) with `teleport configure` or a `teleport.yaml` file; without it, Teleport can start but cannot join the cluster. source
  • Start and keep the service running Run `systemctl start teleport` to begin using it and `systemctl enable teleport` so it comes back automatically after a reboot; otherwise you'll need to start it by hand every time the machine boots. source
  • Keep the Teleport data folder safe Leave Teleport's files, settings, and backup in `/var/lib/teleport`, and leave its shortcut files (symlinks) in `/usr/local/bin` and `/usr/local/lib/systemd/system` alone; moving or deleting them can break the active Teleport install. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does self-hosted Teleport Enterprise require a license?

Yes, self-hosted Teleport Enterprise subscriptions require a valid license. The docs recommend contacting Teleport directly to plan the deployment.

What are the main getting-started steps for self-hosted Teleport?

Deploy a Teleport cluster, connect and protect your infrastructure, configure role-based access controls, set up SSO, and review the audit log.

Do Teleport agents need direct client connections to every resource?

No, Teleport agents run close to your resources and connect through an Auth Service and Proxy Service that enforce identity, access control, and auditing.

What deployment issues have self-hosters reported for Teleport?

Some self-hosters have reported that the Helm charts and documentation are insufficient for complex, IaC- or GitOps-based deployment environments.

Answers sourced from github.com, goteleport.com, goteleport.com, www.reddit.com

Community

Collected 48 days ago - public community threads