head to head · open source

teleport vs kyverno

teleport has 21,061 GitHub stars, 2,181 forks, 3,262 open issues and last shipped 14 days ago. kyverno has 8,310 stars, 1,693 forks, 703 open issues and last shipped yesterday. teleport leads on adoption by 153% (21,061 vs 8,310 stars). teleport is written in Go under AGPL-3.0; kyverno is written in Go under Apache-2.0. teleport has attracted 10% as many forks as stars, kyverno 20%. kyverno was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (kubernetes), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

teleport ★ 21K kyverno ★ 8.3K category Business Software

← all 20902 open source comparisons

Side by side

teleport kyverno
GitHub stars ★ 21K ★ 8.3K
License AGPL-3.0 Apache-2.0
Written in Go Go
Last push 2026-10-20 2026-11-02
Forks ⑂ 2.2K ⑂ 1.7K
Self-hosting Yes Yes
Data ownership Your server Your server

pick teleport if

  • You weight community size — 21K stars and counting
  • You want the AGPL-3.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full teleport profile →

pick kyverno if

  • You want the kyverno feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Go
  • You evaluated both and kyverno fits your workflow better

full kyverno profile →

About teleport

Teleport provides connectivity, authentication, access controls and audit for infrastructure. You might use Teleport to: Set up single sign on (SSO) for all of your cloud and on prem infrastructure. Protect access to servers, Kubernetes clusters, databases, Windows desktops, web applications, and cloud APIs without long lived keys or passwords. Establish secure tunnels to reach resources behind NATs and firewalls without VPNs or bastion hosts. Record and audit activity across SSH, Kubernetes, database, RDP, and web sessions. Apply consistent Role Based and Attribute Based Access Control (RBAC/ABAC) across users…

read the full teleport overview →

About kyverno

Kyverno Cloud Native Policy Management 🎉 📑 Table of Contents About Kyverno Non Goals Documentation Demos & Tutorials Popular Use Cases Explore the Policy Library Getting Help Contributing Software Bill of Materials Contributors License About Kyverno Kyverno is a Kubernetes native policy engine designed for platform engineering teams. It enables security, compliance, automation, and governance through policy as code. Kyverno can: Validate, mutate, generate, and clean up resources using Kubernetes admission controls and background scans. Verify container image signatures for supply chain security. Operate with…

read the full kyverno overview →

More in Business Software

Related comparisons

More Compliance & Risk Management projects

Compare either of these against the rest of the Compliance & Risk Management field.

Frequently asked questions

Is teleport or kyverno more popular?

teleport has 21,061 GitHub stars and kyverno has 8,310. teleport has the larger community by that measure.

Are teleport and kyverno free?

Both are open source. teleport is licensed under AGPL-3.0 and kyverno under Apache-2.0. Neither carries a licence fee.

What is the difference between teleport and kyverno?

teleport is written in Go and kyverno in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, teleport or kyverno?

Choose teleport if you want the larger community (21,061 stars) or its AGPL-3.0 licence terms. Choose kyverno if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.