Why not use the AGPL version?
(Announcement for those who haven’t seen it: https://goteleport.com/blog/teleport-community-license/)
replies(2):
Unfortunately, the Teleport open-source version has been discontinued and the free version doesn't allow companies above 100 employees or with more than 10 million dollars of revenue per year. Fair enough, everyone should live well.
But Teleport Enterprise is very expensive and I have been priced out. I don't know if I can share the price behind the "contact sales" but if you wonder about the price, you probably are too poor. In my case, it's quite a few orders of magnitude more than the time Teleport saves me.
So, I have been looking for a replacement that is open-source and likely to stay open-source for a while. I can pay for it, but I don't have a "contact us" budget.
For HTTPS, I never used Teleport and will stay with oauth2-proxy. For SSH, I found warpgate and sshportal, which may work but it looks a bit experimental. For Kubernetes, it's a mess but perhaps kubelogin could do.
If you replaced Teleport, how did you do it?
(Announcement for those who haven’t seen it: https://goteleport.com/blog/teleport-community-license/)
Compiling and distributing binaries for all users and systems doesn't sound trivial. Only taking care of the teleport `tsh` client between windows, mac, and linux, for arm64 and amd64, sounds like a lot of boring work. Add that some users will likely download the forbidden tsh binary, that may call home and bring some unexpected bills, à la Oracle or Mirantis, it's not very appealing.