Teleport Reviews

Teleport serves as our centralized and secure SSH access management solution across our infrastructure. Instead of distributing static SSH keys to engineers, we integrated Teleport with our SSO provider, Okta, and implemented role-based access control.

In our day-to-day work, Teleport primarily supports secure access to infrastructure as part of operations, and we frequently access staging and production systems for debugging, deployments, and incident response.

Teleport changed our workflow by centralizing access control and reducing manual SSH key management. Previously, access provisioning involved sharing keys and updating access manually, which was not scalable.

Teleport helped us standardize access across environments. Instead of handling access differently for staging and production, we applied consistent role-based policies.

Centralized logging with Teleport significantly improved both our security audits and incident investigations. We previously had to correlate access logs from multiple systems, which was time-consuming and sometimes incomplete.

Teleport had a positive impact primarily by strengthening our security posture while simplifying operational processes.

Teleport has been a solid and secure access management solution, but there are a few areas that could be improved, particularly around the initial setup and RBAC configuration.

Beyond onboarding and RBAC complexity, there are areas that could be enhanced from an integration perspective. While SSO integration works well, deeper out-of-the-box integrations with SIEM and monitoring tools would be beneficial.

I have been using Teleport for the past one year and have been using it for managing secure access to infrastructure. I also evaluated Teleport for a few months as part of a proof of concept.

Teleport is stable.

Teleport scales well when designed appropriately. Its architecture allows you to support a growing number of users and nodes by distributing proxies and auth services across your environments.

I have interacted with the support team on a few occasions, mainly during the initial setup and when clarifying configuration details around RBAC and clustering. Overall, the experience was positive.

Negative

Before adopting Teleport, we primarily relied on traditional SSH key management. As our infrastructure scaled, that model became harder to manage and introduced operational overhead.

Our experience with pricing and licensing for Teleport was straightforward, as the licensing model is user-based.

The pricing and licensing experience was actually very straightforward. While it is not a lower-cost option, the security and audit features justify the investment, especially for teams focused on compliance and centralized access control.

Although we did not run a formal ROI study, we observed measurable improvements after adopting Teleport. For example, access provisioning time was reduced significantly.

We did not calculate a strict financial ROI in terms of direct dollar savings, but we did observe operational efficiency gains. We also saw fewer access-related support tickets.

We did not evaluate any other options, as we were just using traditional SSH keys.

My main advice would be to clearly define your access control requirements before implementation, since Teleport is powerful and its flexibility around RBAC and policy design means you will get the best results if you plan your role structure and identity integration carefully.

Teleport has been a solid addition to our access management strategy, as it helped us modernize how we handle infrastructure access by moving away from static credentials to an identity-driven approach. I would rate this product 9 out of 10.

Teleport is our main tool for our FedRAMP environment, serving as a primary proxy for accessing databases, Kubernetes clusters, EC2s, and web applications.

Our team operates as first responders on-call for Umbrella services. Whenever we receive an alert and need to debug or troubleshoot, the team uses Teleport to log into service teams and AWS resources to debug and troubleshoot first, and then we use that information to communicate with the team and troubleshoot together.

We also use Teleport in automation. Similar to other teams, we provide automation for all servicing teams by leveraging Jenkins to run automation, where Teleport is used through our Jenkins environments using Machine ID. This is heavily utilized by teams to gain certificates, keys, tokens, or sessions to run commands such as SSH or execute commands for Kubernetes, making it very useful for automation.

Teleport offers excellent proxying capabilities, where you add Teleport SSH proxy, as well as strong support for web applications. Since we are tunneling into a restricted environment, Teleport serves as the one essential point of access, and it is highly secure due to our utilization of Okta and VPN for entering the environment.

We use Teleport every day because the environment is restricted, and Teleport is the necessary access point. We are the sole team responsible for the production environment, which is a requirement from our sponsors. It does not take much to maintain it since the maintenance team handles it regularly, ensuring updates occur without disrupting progress. We, as the SRE team, coordinate to ensure Teleport remains operational so that we can troubleshoot and access systems.

While the setup for installation with Teleport Helm chart or on a Raspberry Pi is smooth, I believe they need to streamline the installation process further, especially on Kubernetes clusters or regular computers. Based on my experiences testing the product, I think more automation regarding configuration verification is needed as some specifications documented do not align with practical requirements. The learning curve is an area for improvement.

I have been using Teleport for about four years.

Teleport is very stable.

Regarding scalability, I would say it is quite good, specifically when using EC2s, and it can be easily installed on Kubernetes.

Teleport customer support is really good. We have interacted with many people who provide us with a dedicated Slack channel, enabling us to reach out and quickly find solutions. When there is not an immediate solution, they provide us with timelines for when to expect resolution on bugs or features.

As far as I know, we did not use another solution prior to Teleport.

Teleport is easy to install, making it a tool that other teams would want to use, with a positive impact in terms of its simplicity for our team and the servicing team already having created documentation. In my previous team, we also collaborated with another team to deeply understand the product, enhancing visibility for its use across the company.

There are a few small issues that bug my team that I have not yet mentioned in terms of improvements.

I have mentioned everything regarding the features. I use all those features personally, and I particularly appreciate that Teleport is not limited to enterprise levels, as you can also install it on a Raspberry Pi, which is open-sourced. I do want to point out that the documentation could be improved.

I would definitely advise others looking into using Teleport to try it out if they are seeking a tunneling or proxying solution to streamline obtaining access without dealing with DNS or SSH, as it is straightforward to install, can be tested in various environments, and is a truly exceptional product that is easy to use. Teleport is simple to use, but sometimes it requires extra research for more unique tasks, which slightly detracts from its overall quality. I would rate this product an eight out of ten.

Teleport is for uplinking channels, which means uplink the channel with multiple feeds and the channel uplink for Teleport.

In my work with DTH, we are uplinking the channel in the Ku-band. We are uplinking approximately 750 channels and transmitting the signal with 24 transponders. In day-to-day operations, the work involves channel addition and deletion based on management requirements. The daily process includes additions, deletions, and any incidents that arise.

We already have two different satellite uplinking setups and 24 transponder setups.

With the help of Teleport, we are managing many channels. I find it easy to manage how to uplink the channels, and we are automating many things in our setups. We have an MCR, an automatic NMS, and a data center. We have managed it well to make life easier for my employees and colleagues.

Teleport has helped us minimize incidents and maintain our uplinking time and uptime. Our organization's uptime is 99.90%, which is almost 100%.

With Teleport, we can achieve this uptime by using the best equipment and best automation systems, such as alarms. We have applied DataMiner, Barco systems for alarming, and DataMiner for managing the RF things. We have applied many systems in Teleport.

Managing 700 to 800 services is not easy. Every day, we are facing many challenges. For example, sometimes we face multiple incidents on multiple channels. We are also working on how to improve major faults.

I have been using Teleport for the last 10 years.

Automation is the best way to improve our system. Automation is a must. We can implement automation in RF and on the compression side. With the help of automation, we can minimize errors or faults and the painful parts of daily life and make life easier.

They can use Teleport with the best equipment and the best systems, with the help of automation. We are a DTH operator.

I rate this product a nine because Teleport manages many things and makes life easier for the RF and compression teams.

My main use case for Teleport in day-to-day work is accessing Windows servers, Linux servers, and Kubernetes access plus databases, where it is secure for me as an end user to access the servers via a Teleport proxy. Once I'm logged in, I do not have to expose the username and password of the other Linux servers, Windows servers, or Kubernetes clusters.

A specific example of how Teleport recently made my workflow easier is when I wanted to access any AWS machines or on-premise machines. To do that, I would have had to get the username and password and then log in using either certificates, which could be a threat, as someone could access those usernames and passwords from my computer or from something shared over Teams channels or other chat channels, creating a security threat. Once I started using Teleport, I do not need a username, password, or certificate to access the servers; all I need is authentication to the Teleport portal, from where I can access any servers that are onboarded.

My main use case right now is accessing the servers, whether on-premise, AWS machines, or any Kubernetes access. Our company has to whitelist those URLs over some VPNs to access any servers. Once we started using Teleport, we do not have to explicitly whitelist any servers or URLs from the VPN; we can just onboard them in Teleport and access them directly.

The best features Teleport offers include the ability to easily download and upload files to the servers from my local system, and it also allows me to access servers from my local terminal, plus it provides a thick client. The client displays all the servers for access, which is excellent from a UI perspective compared to other tools.

I prefer using my local terminal for more control over my copy-paste and other actions, but from a UI perspective, Teleport provides different options such as viewing different roles that are created, audit logs that are ongoing, and recordings that are easily accessible from the UI.

From the admin perspective, viewing the logs such as the audit logs, recordings, created roles, and integration with third parties for notifications or approving requests from those who raised server access requests is quite easy compared to other tools.

Teleport has positively impacted my organization by being very helpful for productivity and team collaboration, especially since the old tool we used took a lot of time to get approvals. In Teleport, we maintain a group of members or access list, so owners of the servers can approve requests quickly without relying on one single team, which made life very easy for developers or anyone accessing those servers.

Specific outcomes that I noticed include a reduction in the approval time, as it is very minimal compared to the old tool, which is due to having different owners for various access lists or groups of servers that can easily approve requests. This does not hamper daily BAU activities. From a security perspective, we are not exposing any secrets, certificates, or sensitive data, which also reduces security threats.

One frustrating aspect of Teleport is when I try to access the audit logs. The pagination process requires the data to download from the backend first before showing it. Instead, it would be better if the data could show by default without this download process. Additionally, the search function in the audit logs is not effective, as it only returns data present or downloaded locally for a limited time, and it does not search the entire database as expected. Another improvement could be clipboard access, as we found that there is no control over copy-pasting data from the server to my terminal in Linux, which poses a significant security threat.

I rate it a seven because, as I mentioned, there is a security threat regarding clipboard access. There is no control over copy-pasting from Linux servers to my local machine, which is unsuitable for our use cases. Moreover, I want to see who is trying to access which server, but that information is not easily available, making it difficult.

Teleport could improve in pagination, audit log reports, and providing easier solutions for admins trying to debug from the UI. Being able to download information on what user is attached to which role, and all the labels associated with those roles, could greatly help admins.

I have been using Teleport for two years to access the servers.

We experienced some hiccups with Teleport, but that is primarily due to our setup issues. Since we have not purchased the cloud solution and self-hosted it, we face occasional challenges. We also found issues related to accessing the WebLogic server in some cases.

In terms of scalability, since we are running on Kubernetes, whenever new requests come in, the pods automatically scale up, which looks fine so far, with no observed latency or performance issues as of now.

Customer support is currently managed through emails only as we do not have portal access. We do get responses for high-priority issues within a day, asking for more details. Overall, I would rate it a seven out of ten.

Positive

Previously, we used Arcos, which was similar to Teleport, but we switched because it was not user-friendly, and the approval time took too long. It also did not provide access to Kubernetes or application functionalities that we needed, which is why we moved to Teleport.

I can say that the metrics indicate time saved for approvals and that it is user-friendly for accessing servers and other functionalities.

Regarding pricing, setup cost, and licensing, since we are on a private cloud, we have active-active setups in both cases, currently consuming minimal resources. With about 2,000 servers onboarded, I do not have much comment on the licensing.

Before choosing Teleport, we did not evaluate many other options. We heard about Teleport on social media and conducted a POC, finding it suitable for our use cases.

My advice for others looking into using Teleport is that if you do not have many sensitive servers, it is better to purchase the cloud version of Teleport. You will get more frequent support, and Teleport manages it more efficiently from their side. I rate this product a seven out of ten overall.

My main use case for Teleport is to smoothly receive and transmit all audio video content and other data without any interference, without any distortion, and without any losses. It is my responsibility to ensure that it runs smoothly.

One specific example of how I use Teleport in my daily work is that when we lose audio video due to a link down, we can play emergency content in place of the lost audio video. Sometimes we have faced technical issues from the encoder or mux, and then we switch to a backup channel or backup devices.

I have more to add about my main use case for Teleport. Sometimes we experience a loss in the HPA, which is the high power amplifier. Due to this, we sometimes observe that in a TS we are getting CCR due to the modulator issue or RF interference, and then we coordinate with the satellite team and transponder team to resolve the issue. If we are getting interference on our end in a modulator, upconverter, or HV, we have to check the parameters. We have to check the connections of the devices because sometimes it occurs due to loose connections or faults in the cable. We resolve the issue quickly so that our viewers can receive content without any interference.

Teleport's best features, as it is a primary source, are that all DTH operators can get the audio video content. There are many DTH operators, and if we lose the audio video, then there will be a loss of audio video because they are relying on it. The best feature in Teleport is that we can transmit multiple channels on a single TS.

Regarding how Teleport has positively impacted my organization, I have learned a lot of things through it. I understand how to deliver and receive content, and I have learned many things related to RF signals where we lose packets. Regarding RF, I understand how to transmit and how the EM wave travels in air, and I am improving my knowledge day by day because I have experience with this. I try to make different types of projects where if we face these issues, we can resolve them quickly. Then we create a setup to check if the issue is related to our customer or our devices. We have established the whole process.

Regarding how Teleport can be improved, I believe we can improve by using more automation on all devices. Sometimes our devices do not reflect the error, and then we work on why it is not showing any alarm or issue, even though we experience distortion or issues on the TS. We work to resolve these issues by changing some devices and their alarms. Our development team consults with our R&D team regarding these types of issues to see why we are not getting device alerts. Then we upgrade the devices, firmwares, and fix bugs.

I have ten years of experience using Teleport.

Regarding whether Teleport is scalable, when we transmit channels, we need Teleport. It is a government guideline that to uplink any channels, we should transmit with the help of Teleport. Therefore, I can say that it is stable, and I also upgrade myself.

Teleport customer support is very responsible regarding any hardware, license issues, upgrades, and other matters.

Positive

I would advise others looking into using Teleport that it also provides OTT facilities through the internet. Teleport is now also upgrading by incorporating automation and involving OTT platforms. I rate this product an eight out of ten.

With the new company, I will move into an enterprise version of Teleport because the previous one is a community version, which is free with unlimited resources and reach to a multi-cloud environment. With this enterprise edition, it is more of a SaaS offering of Teleport wherein we provision our PAM for our engineers to connect to our AWS resources deployed in multiple AWS regions in Europe to manage our infrastructure.

It is cloud-native, and we are now working with Kubernetes containers. Managing our Kubernetes cluster is easy to access and transparent. We don't need any proxy; it is direct to the resource. As long as you define the policies and permissions for Kubernetes access for the SRE or DevOps team to manage the cluster, everything runs smoothly.

We love recording the commands they execute and also the video recording of it.

Teleport is more mature. They have been in this market for many years and provide granularity in terms of accessibility for engineers, end-users, and even on-premises resources. It is easy to deploy. For example, you create a permission, add the resource, and define the permission based on your IAM or the group of people based on the IAM. Then, connect to the IAM, and it will provision it for you easily.

From my experience, Teleport already aligns with granular access control, especially for a global resource group, with different cloud resources and different endpoints. Different teams, including human and non-human objects that need to access the resource, can be managed easily. We can create service accounts, and those service accounts can be ephemeral and can be rotated every three months.

It improves the visibility and audit. Even during incident management, we can track what has happened before and what the engineer did on the environment before the incident occurred. For example, doing something in the databases, and if they use some commands to drop a table or even the entire database, we can capture that. It helps us in attaining our compliance, such as for PCI DSS and SOC 2 reports, as part of our evidence.

Teleport definitely reduced the risks. We are no longer exposing root-level accounts for people that are meant to have an elevated account. For instance, if a team lead has management or should be a root, we eliminate those. We align according to our RBAC definition, determining who will be accessing what kind of resources and who, for example, during the on-call schedules, if they need an elevated account for six hours during on-call, we can provision them just-in-time without any approval. So we follow all the policies and procedures around that.

I think since nowadays it is more about AI, Teleport might need to improve or focus more on how to interact with MCP agents, provisioning access to non-human agents to connect to back-end resources such as databases or any data sources, for example, Snowflake. There should be some granularity on it because many threats right now, even advanced threats, are using AI. I haven't tried that part yet, but I look forward to Teleport improving access to the AI environment.

I have been working with Teleport for more than a year.

Teleport is superb in terms of support. They attended to any issue we had with them. Just opening a ticket resulted in quick resolution for us. They align with the support engineer available in their shift, and they will attend to it quickly.

Positive

It is not difficult, really. You can connect with IDP parameters or the SSO parameters. You can connect to Okta, you can connect to Active Directory, or even a database. As standard practice, we use our infrastructure-deployed identity. It is not a challenge for us.

I am part of cloud security and am the one leading in our company to evaluate several PAMs, such as cloud-native PAM, that align with our DevSecOps initiative. Before, I also evaluated Brightive. Initially, I got in touch with Apono. Those are new players in PAM. Both Brightive and Apono are based in the US. We used to evaluate solutions that are locally deployed or have local support in the region, such as in Saudi Arabia or UAE. That is our priority.

Teleport is between nine and ten in terms of overall product quality and performance. They have not been perfected yet, but they are above nine, so I would rate them at nine. I would give Teleport an overall review rating of nine.

I use Teleport to connect to bare-metal servers. Our security system uses Teleport to collect actions performed on bare-metal servers.

All our actions are sent to an inner cloud where our system analyzes what we did on the server, so it is important for our security engineers to analyze our actions and consider security implications.

I have considered using Teleport to connect to some databases, but we have our inner systems for this purpose, so we use Teleport only to connect to bare-metal servers. This functions as a proxy server for SSH.

The best features include its main capabilities such as collecting actions and showing others what you did on the server, an easy way to connect to any bare-metal servers, and the ability to describe which servers you can use and who can connect to these servers. It provides an additional security layer to connect to other servers.

I believe it is more about security, and if someone in system administration makes a mistake on the servers, our security engineers can find it and communicate it to others.

We do not use any relevant metrics because it was important for us for security reasons. Our security engineers wanted to observe our actions, and Teleport gives us an easy way to send our actions to the inner cloud for security engineers.

I think it should have less complexity to set up on self-hosted because it is still a difficult process and I spend a lot of time using it on self-host. I think using it on other servers as a service is not a secure way, and it should be simple to install.

I think after a while we will not use Teleport because at version fifteen you must always pay for this. A big company cannot use it without paying, so we should find other products to use.

I have been using Teleport for about two years.

Teleport is stable, and I cannot remember any mistakes that we have experienced.

Teleport's scalability is easy for our organization, but we do not have a big inner system for this; I have only three hosts for this, and it is enough to operate without any mistakes.

We did not use any other solutions before Teleport.

I have already stated that we do not think about any other solutions; we considered creating something ourselves, but it could take more time than we have.

I do not know any specific positive impact. It is important to us, but how it can positively impact us is still unclear.

Out of ten, I think eight is a fair number.

I choose eight out of ten because I do not know any perfect applications, so there is always room for improvement. I have already mentioned that you must pay for it always if you do not use any special features in Teleport, and if you work in a big company, I need only basic features without any others, which I think is impossible for us at this moment.

You should think about what is important to you because if you use only the free version, you should know that SSO does not work, and you cannot create a simple way to scale.

I give Teleport a rating of eight out of ten.

I use Teleport to replace the normal authentication mechanism as part of a zero-trust architecture. It is particularly useful because, in a remote environment, I cannot trust any devices. I can share access remotely with anyone via a browser for more secure tracking of data.

Teleport has replaced earlier methods like a bastion server or a jump server, which required connecting to physical servers. It integrates well with single sign-on (SSO) and Ansible Playbooks, allowing me to manage inventories easily. 

Teleport provides a straightforward setup process with a single command line, making it easier to manage the onboarding and offboarding of team members.

I cannot download or share session recordings directly with others, which would be useful for documentation or reviews. 

Additionally, while the backend worker can be upgraded, there is a limitation with scaling, as it supports only a single node even in Kubernetes.

I have been using Teleport for two years.

Initially, there were stability issues when integrating with single sign-on and storing sessions. After resolving them, Teleport has been stable.

Teleport supports only a single node in the Kubernetes environment, which limits its scalability. It is straightforward for single standalone components, however, the UI component cannot be upgraded directly.

Previously, I used a jump server and accessed systems with an SSH key and a normal VM login. 

I switched to Teleport since colleagues and friends recommended it, highlighting its enterprise-level capabilities.

The initial setup was straightforward due to my expertise in Linux, particularly Red Hat and Ubuntu operating systems. I found the setup to be very easy.

With Teleport, my time spent on onboarding and offboarding has reduced significantly. I no longer need to manually manage access, which saves time and effort.

Another option I considered was HashiCorp's Boundary, however, it had a complex setup that was difficult for beginners. Teleport's straightforward setup was more appealing.

I rate Teleport nine out of ten. 

Security-wise, it is very secure and easy to use for remote access. I recommend it for its straightforward setup and strong security features.