head to head · open source
teleport vs ThreatMapper
teleport has 21,061 GitHub stars, 2,181 forks, 3,262 open issues and last shipped 14 days ago. ThreatMapper has 5,327 stars, 631 forks, 144 open issues and last shipped 5 months ago. teleport leads on adoption by 295% (21,061 vs 5,327 stars). teleport is written in Go under AGPL-3.0; ThreatMapper is written in TypeScript under Apache-2.0. teleport has attracted 10% as many forks as stars, ThreatMapper 12%. teleport 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.
← all 20902 open source comparisons
Side by side
| teleport | ThreatMapper | |
|---|---|---|
| GitHub stars | ★ 21K | ★ 5.3K |
| License | AGPL-3.0 | Apache-2.0 |
| Written in | Go | TypeScript |
| Last push | 2026-10-20 | 2026-06-01 |
| Forks | ⑂ 2.2K | ⑂ 631 |
| 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
pick ThreatMapper if
- You want the ThreatMapper feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and ThreatMapper fits your workflow better
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 ThreatMapper
ThreatMapper Runtime Threat Management and Attack Path Enumeration for Cloud Native [!NOTE] This project is maintained by Deepfence ThreatMapper hunts for threats in your production platforms, and ranks these threats based on their risk of exploit. It uncovers vulnerable software components, exposed secrets and deviations from good security practice. ThreatMapper uses a combination of agent based inspection and agent less monitoring to provide the widest possible coverage to detect threats. With ThreatMapper's ThreatGraph visualization, you can then identify the issues that present the greatest risk to the…
read the full ThreatMapper 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 ThreatMapper more popular?
teleport has 21,061 GitHub stars and ThreatMapper has 5,327. teleport has the larger community by that measure.
Are teleport and ThreatMapper free?
Both are open source. teleport is licensed under AGPL-3.0 and ThreatMapper under Apache-2.0. Neither carries a licence fee.
What is the difference between teleport and ThreatMapper?
teleport is written in Go and ThreatMapper in TypeScript. 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 ThreatMapper?
Choose teleport if you want the larger community (21,061 stars) or its AGPL-3.0 licence terms. Choose ThreatMapper if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.