Traefik Enterprise Reviews

My main use case for Traefik Enterprise involves self-hosted infrastructure setup in my home lab, where I was searching for the best tool to manage a proxy manager for our services. I was planning to host media servers, such as the open-source Jellyfin project. The problem I encountered was the need to manage a reverse proxy manager and certificates, as I was planning to expose the media server to the internet, making security a concern. When searching for a solution, I discovered Traefik Enterprise as the best option. I used Jellyfin as a cloud application within a Docker container. In that Docker container, I integrated Traefik and SSL Let's Encrypt SSL certificate, which is also open source. I then set up Traefik and Let's Encrypt in a Docker container with a Docker Compose file, and subsequently deployed the Docker application on my Raspberry Pi machine. I then began using and streaming the media through Jellyfin.

Additionally, in my use case with a self-hosted media server, there were some issues. Initially, I was using Cloudflare DDNS and Cloudflare Tunnel. The problem with that existing setup was when using the media server on my local network, I had to always remember the IP address, port, and everything. It was always going through the Cloudflare Tunnel DDNS. That would consume most of the bandwidth because it would encrypt and decrypt, and then the media would buffer during streaming, which was unnecessary. When I use Traefik Enterprise on my local network, it can use a local port or a local fully qualified domain name. Externally, on the internet, it can expose it on a different domain. Traefik Enterprise helps me stream our media on my local network without any encryption or decryption. I can also use the proxy manager when exposing it to the internet. It balances both needs and will automatically manage the certificates and security. I can also see the dashboard. There are many good advantages to this approach. I am also aware I can accomplish many other things using Traefik Enterprise.

What made Traefik Enterprise the best option for my use case is that it is both user-friendly and open-source. It can integrate with many other tools, such as Let's Encrypt and Docker. In a Docker Compose file, I can easily add Traefik Enterprise configuration and Let's Encrypt. When I make changes, I can directly modify the Docker Compose file, and Traefik Enterprise will pick up the new configuration. It will even connect with Let's Encrypt and obtain the new certificate. I would say it has more features compared to other proxy managers, which is why I chose Traefik Enterprise.

The best features Traefik Enterprise offers in my experience include the fact that it does not have static config files like Nginx. Instead, I can manage the central configuration and restart it at any time. Traefik Enterprise natively watches my infrastructure and will spin up using a Docker daemon and socket. I can also configure Traefik Enterprise using labels, which are useful. I believe I can manage zero downtime, such as hot reloads, and many other things. Those are the main advantages when I spin up the open-source media server project.

Traefik Enterprise has positively impacted my organization by reducing a lot of time, especially when I configured Traefik Enterprise, Let's Encrypt, and Docker. Whenever I expose a website to the internet, I always have to ensure the SSL certificate is handled, which takes time. Regarding ports, whenever I use any of my services on the internet, I have to manage my ports. Traefik Enterprise always ensures port overlap does not happen; it will eliminate port overlap. Using Traefik Enterprise and Let's Encrypt provides dynamic certificate provisioning. Traefik Enterprise integrates directly with Let's Encrypt via a DNS provider, such as Cloudflare or AWS Route53. It can fulfill the ACME challenges, provide SSL certificates, and manage auto-renewals natively. It also manages automatic TLS upgrades. For example, if I want to upgrade from HTTP to HTTPS, it will do it immediately. Those are the significant advantages. I can even share my open-source GitHub links that demonstrate how I use Traefik Enterprise in my Docker Compose files.

I can quantify improvements while using Traefik Enterprise. For example, I was using 20 or more Docker applications. If I wanted to set up SSL certificates for each application, it might take three to four hours. Instead, I set up Traefik Enterprise one time, and it saved approximately 20 to 30 hours of maintenance per week. Additionally, any changes to one setup also saved more than 10 hours. Overall, it saved 20 to 30 hours per week.

I think Traefik Enterprise can be improved with native multi-cluster control plane syncing. For example, when using syncing similar to Kubernetes, Traefik Enterprise could also utilize multi-cluster control plane syncing. I believe it could improve some documentation context. Sometimes it supports many dynamic provider environments, but the documentation for each dynamic provider is not comprehensive. I think that can be improved. The dashboard could also be enhanced, such as managing any network operation or providing a toggle for a maintenance page. Those things can be improved in the UI dashboard.

Traefik Enterprise can be improved with things such as hard controller defenses for distributed rate limiting, high-capacity log streaming buffering, and implementing some asynchronous configurable non-blocking internal ring buffer mechanisms in log shipping. Additional improvements could include native blue-green canary automation, fragmented CLI engine management, such as using the control plane operation in Kubernetes, open API driver REST endpoints, removing unnecessary maintenance, and separating the operational libraries such as TCTL. Those kinds of small improvements could be made.

I have been using Traefik Enterprise for the last one and a half years.

Traefik Enterprise is stable in my experience and more stable than competitors such as Kong Enterprise or Apache Enterprise.

Traefik Enterprise's scalability is very good. I can use Traefik Enterprise for any number of applications. It is horizontally scalable and has high availability, which is very good for scalability.

I initially used Cloudflare Tunnel and Nginx Proxy Manager before Traefik Enterprise. Both had problems. Nginx Proxy Manager is not comparable to Traefik Enterprise. Traefik Enterprise can be integrated with Let's Encrypt and can be managed very easily. Cloudflare Tunnel was also not useful because when accessing a website, it uses an encryption-decryption method, which is not good for speed or internet traffic. That is why I switched to Traefik Enterprise. It does not have manual configuration like Nginx Proxy Manager. I think certificate management is easy in Traefik Enterprise, so that is why I chose it.

I have not used Traefik Enterprise; I use the free setup. I only use the free setup, so it does not cost much. The setup required some of my time, and for the infrastructure setup, I spent approximately 20,000 to 30,000 Indian Rupees for setup costs. However, there is no licensing because I am using Traefik Enterprise, not the enterprise version, just the open-source version.

In our setup, fewer employees are needed because I am the only person managing all these things. No additional employees are required for this setup. I am using this for open source and my local setup. Money is not saved much, but time is saved, and one person is sufficient to manage our self-hosted machine.

Before choosing Traefik Enterprise, I tried Nginx Proxy Manager. I used that one. Other than that, I did not try anything else.

My advice for others looking into using Traefik Enterprise is to first check other alternatives and compare Traefik Enterprise with other applications and look at your requirements first. If the requirements are a better suit for Traefik Enterprise, I recommend proceeding. Alternatively, you can try out other tools as well. Before using Traefik Enterprise for all applications, I think you first need to master the configuration setup skill and design your configuration. Then you can proceed with Traefik Enterprise if you find it to be a better fit for your requirements. I rate this product an eight out of ten.

On-premises

Other

I use Traefik Enterprise for my daily needs, including load balancing and centralizing my cloud-native applications.

At Hoichoi, we have been using Traefik Enterprise for the last two years. We implemented Traefik Enterprise for consolidating and orchestrating the network into a single endpoint. We use Traefik Enterprise to provide a single endpoint to reach all of our services.

In our company, Hoichoi, we use Traefik Enterprise for a single endpoint. We have api.hoichoi.tv, which we point to what is called a Traefik Enterprise endpoint. Inside Traefik Enterprise, we map it with another path such as /api/services to our services service and /plans to our plan service.

Apart from that, we use it for load balancing. All of our load balancing is pointed to multiple Traefik Enterprise instances, and then we divide the traffic among them. We also use it for observability to monitor how the load is spiking up or down.

I appreciate that Traefik Enterprise offers observability and load balancing features, especially the ability to orchestrate all endpoints. I love having only one domain to connect with, such as api.hoichoi.tv, and then adding only /subscription to reach my subscription service and /plans to reach the plan service.

With the observability feature in Traefik Enterprise, I get records of traffic patterns. For example, at three o'clock in the morning, I caught a traffic spike immediately, giving me proper data about when the traffic started spiking and when the load reached its peak. This allows me to reduce my bills and not keep all of my services scaled up all the time. I can scale down the services as needed.

I primarily use the observability feature and the single-pointing orchestration for all of the microservices. I appreciate these services because they help me maintain only one domain.

Traefik Enterprise is helping us tremendously because we do not need to manage multiple service domains. For example, we do not need to manage a subscription service domain and a plan service domain separately. We know that we have one domain, and if any service is down, I can go to Traefik Enterprise observability and see which domain is down, when it went down, and how it is impacting our operations.

I would appreciate improvements to the user interface because it currently appears generic. Please add more professional elements to the UI. I need this because when I open this site in public, everyone says it was built by a college student. I would love for the UI to be professional.

For other things, you should orchestrate the features list on the home page and add other things. You should not mention everything. You should mention on the home page which feature I last used so I can go there directly without navigating through settings and multiple menus. If I use any feature repeatedly, it should appear on the home page.

I have been working with this solution for almost two years in my current field.

I remember that last night at three o'clock in the morning, my senior called saying that the traffic was getting a 404 error in the plan service. I needed data on when it started and how this issue was impacting us. I went to Traefik Enterprise observability feature and checked that after our last code merge, we were getting this error. After that, we were getting the 404 error. I checked and then reverted the changes, which is why I love Traefik Enterprise observability feature.

Overall, I give Traefik Enterprise an 8 out of 10 because it is very nice to have on my production-grade server. I suggest that you improve your UI and the features, and then it will get a 10 out of 10.

I chose 8 out of 10 because I have been satisfied with all the features I use. I reduced two points because of the UI and the requirements I need. I have already suggested what I need, and I believe it will be great for me if you improve that.

We use public cloud and deploy on AWS ECS. In ECS, we deployed the Docker file. We purchased the solution from AWS Marketplace.

I suggest that everyone use this service because of its simplicity. It provides multiple features in a single product, and you only need one subscription to use it. I appreciate that service.

I am a customer from my company's side. In the future, we will connect with Traefik Enterprise business side to make a business relationship and refer our services. Currently, we are customers.

My main use case for Traefik Enterprise is to help route traffic from internal services to other services, and it also helps handle a lot of DNS resolution so that we do not have to worry about it.

A specific example of how I use Traefik Enterprise in my workflow is that we use it with a tool called Dokploy, which is built into the platform where it routes all DNS traffic and records through Traefik. We also use it for proxying; for example, if a website is not fully ready to launch, we use a temporary domain that Traefik or Dokploy can generate for us, allowing us to expose that publicly so we can use it either internally or show demo versions without having to configure DNS ourselves until we are ready.

The best features Traefik Enterprise offers, assuming that the temporary domain names are a feature of Traefik, would be that, as it has been really helpful to our workflow. Assuming that is not an actual feature of Traefik but of Dokploy instead, I also value the automatic Let's Encrypt validations and SSL certificates. We were trying to set it up manually ourselves or using automatic scripts with Let's Encrypt, and it was too much of a hassle. Traefik really automates a lot of the difficulties for us.

Traefik Enterprise has positively impacted my organization by making DNS and SSL management incredibly easy.

My experience with the automated SSL certificate management is that it has saved us a lot of time because typically, we run things through Docker containers with exposed ports, and the Let's Encrypt automatic certificate renewal has to be run on these HTTPS ports. Trying to run it and put it in a place where it expects to be has been more annoying and difficult, whereas Traefik just knows to automatically section and divide them.

Regarding the impact, it has definitely saved us time. I do not necessarily know if it has reduced errors, but not having to worry about renewing SSL certificates or setting up the automatic certificate renewal in our own time has definitely been very important to us being able to perform efficiently.

Traefik Enterprise can be improved because the documentation is not very easy to read and comb through. Luckily, a lot of it has been abstracted away from us through the various implementations we have used, but anytime I have had to read the Traefik logs or documentation itself, it has been a little more overwhelming and convoluted compared to other documentation out there.

If I had to mention any improvements needed for Traefik Enterprise, my biggest concern is that I wish the documentation was clearer. Documentation is really the biggest pitfall we have had.

I have been using Traefik Enterprise for about two or three years.

In my experience, Traefik Enterprise is stable.

Regarding Traefik Enterprise's scalability, I think it is fine, but I do not really know.

Previously, we were using cPanel and a couple of other solutions like CloudPanel, and the reason we switched was that they were very limited in what we wanted them to do aside from the DNS additional features. The current implementation we have right now is a lot more suitable for our workflow.

I have not seen a specific return on investment, but it has definitely been easier for us to get products out the door. The implementation we have is straightforward regarding how to connect everything, with dropdowns. This is a very specific implementation, but for people I used to work with, it was a lot easier for them to understand than configuring things through a firewall or command line, making it a lot more straightforward.

My experience with pricing, setup cost, and licensing has been fine since we usually go through a third-party implementation of Traefik. I have had no issues with it; it seems to be open source and has been pretty good for us.

Before choosing Traefik Enterprise, I did not evaluate other options much. If I had to go back, knowing what I know now, and if I was still working at this company or my previous employer, I might consider using a Caddy file instead. I do not know if I would choose Traefik Enterprise again unless it was through an implementation of another platform because I do not feel having to deal with the headache of learning it from scratch.

I do not have anything specifically towards Traefik to add. The Dokploy implementation of it has really been the main driving point. I have found Traefik itself a little hard to use, at least regarding their documentation, but I have no problems with the service itself.

Once it has been implemented, especially in a tool where I do not have to think about it too much, I have really had no issues with it. One of the minor annoyances is whenever we add a DNS record on Dokploy with Traefik, the entire container has to restart so that those updates are there. I do not know if that is Traefik specific; I am assuming it is because of the Docker implementation, but aside from that, I have really had no issues with it.

My advice to others looking into using Traefik Enterprise is that if you are doing it through a third party, it is definitely worth understanding a little about it. However, if you are going to be setting it up from scratch and managing it through some other implementation, it might be easier to use something such as a Caddy file, unless you have people with networking experience on your team.

Traefik Enterprise is a fine platform, but I do not really have too much experience with actually using it directly. The third-party implementations we have been able to use at our job have been very straightforward and have had everything we needed and more. I cannot validate if that is a direct feature of Traefik that enables all of this or if it is something more nuanced to the platform we are using for deployments.

Regarding Traefik Enterprise's AI capabilities, I have never used any of it, so I cannot comment on its accuracy and reliability of output.

I would rate this product eight out of ten.

My main use case for Traefik Enterprise was as a reverse proxy and load balancer for Docker-based applications. I used it to manage routing between multiple services, handle HTTPS with Let's Encrypt, and simplify access to containerized applications during development.

Using Traefik Enterprise for reverse proxy and load balancing made managing containerized applications much easier instead of configuring each service manually. I could define routing rules through Docker labels, and Traefik Enterprise automatically detected new services. Automatic HTTPS with Let's Encrypt also saved time and reduced configuration errors.

Automatic service discovery and dynamic configuration specifically benefited my projects by saving me considerable time when working with Docker containers. Whenever I deployed a new service or updated an existing one, Traefik Enterprise could detect the changes automatically without requiring manual updates to proxy configuration. This reduced setup complexity and minimized configuration errors.

Traefik Enterprise had a positive impact by simplifying the management of containerized applications. It reduced the time spent configuring reverse proxy rules, automated HTTPS with Let's Encrypt, and made it easier to expose multiple services through a single entry point. It helped me collaborate better with my team, reduce downtime, and improve security.

Overall, my experience with Traefik Enterprise was positive, but I think the learning curve could be improved, especially for new users. The configuration options are very powerful, but understanding routing rules, middleware, and providers can be challenging at first. More beginner-friendly documentation and practical examples for common deployment scenarios would make adoption easier.

I would also like to see even better debugging and troubleshooting tools with clearer error messages and more detailed diagnostics when a route or service is misconfigured.

I have been using Traefik Enterprise for two or three years.

I do not have specific metrics to share because I mainly used Traefik Enterprise in university and personal projects rather than in a production environment. However, I did notice that setting up new services became much faster since I did not have to manually update reverse proxy configurations. It also reduced configuration errors and made deployment more consistent, especially when working with multiple Docker containers.

My advice to others looking into using Traefik Enterprise would be to start in a small project and take the time to understand the core concepts, especially routing, middleware, and service discovery. Once you become familiar with those, it is much easier to take advantage of Traefik Enterprise's flexibility. If you are using Docker or a microservices architecture, Traefik Enterprise integrates very well and can simplify services management significantly. I would also recommend following the official documentation and experimenting in a development environment before deploying to production. Overall, it is a powerful solution, but investing a little time in learning it pays off. I would rate this product nine out of ten.

On-premises

Other

I have been using Traefik Enterprise for three years, initially in my previous organization where I used it for hosting internal projects.

My main use case for Traefik Enterprise currently is to host an internal application in my organization where the applications are built as Docker services, and traffic labels are added to these Docker Compose files to allow the application to be hosted.

This setup helps my team day-to-day by making development very reliable and much more abstracted by Traefik Enterprise. The usual configuration setup that goes into these services is very tedious, so the traffic labels abstract these complexities and allow the developers to be much faster in development.

Traefik Enterprise has positively impacted my organization by definitely improving productivity in development and reducing the time to go to production, as it abstracts a lot of configuration-related complexities. It has brought benefits to the organization in terms of speed, quality, and maintainability, and it can be modularized and tested.

In my opinion, one of the best features that Traefik Enterprise offers is the Docker integration, where I do not have to maintain a large centralized configuration every time I deploy a new service. Whenever I spin up a new container, I simply add a few traffic labels to the existing Docker Compose, and the service is automatically available through reverse proxy, keeping everything modular and much easier to maintain as the number of services grows.

Docker integration with Traefik Enterprise has made scaling or troubleshooting much easier by abstracting many aspects in my development, especially the TLS certificate management. Setting up HTTPS usually involves multiple steps where things can go wrong easily, but Traefik Enterprise abstracts it in a much better way, saving significant time and reducing configuration mistakes. This has helped the team focus on the actual application development rather than worrying about certificate renewals and web service configuration.

The unique feature of Traefik Enterprise that I appreciate the most is the integration with Docker and the level of abstraction it gives for TLS and service discovery, as all these configuration-related tasks have been abstracted in Traefik Enterprise, making it much more helpful for developers.

For the TLS feature in any web application, it used to take us a lot of time, around two weeks for setting up TLS certificates and getting it approved, but things have become much easier with Traefik Enterprise. Now, the development team takes only probably two to three days to configure the TLS, allowing them to focus on the actual application development.

If I have one suggestion for the Traefik team to improve Traefik Enterprise, it would be to make the documentation even more interactive, perhaps by integrating an AI-powered assistant. The documentation is already excellent, but as it continues to grow, an AI-assisted tool specifically trained on the official document could help answer configuration-related questions much more instantly.

I have been working in my current field for seven years.

In my experience, Traefik Enterprise is stable for my use cases.

The customer support for Traefik Enterprise is very responsive, and I have used it a couple of times with a good experience, as they supported me and I found the solution pretty quickly after contacting them.

I have not used any different solution before Traefik Enterprise; I started in my previous organization with Traefik Enterprise.

Before choosing Traefik Enterprise, the team considered Nginx as one of the options, but the level of abstraction that Traefik Enterprise provides, along with its ease of use, great documentation, and less steep learning curve, made the team choose Traefik Enterprise over other solutions available in the market.

My advice to others looking into using Traefik Enterprise is to proceed with it, especially if the team is deploying applications using Docker, Docker Compose, or anything that deals with Docker or Kubernetes, as it has good integration and support from the Traefik team.

I suggest any fellow developers use Traefik Enterprise if their projects deal with Kubernetes or Docker, as most of the configuration complexities are easily abstracted, it has good documentation, and the learning curve is not steep. I would rate my overall experience with Traefik Enterprise as an eight.

On-premises

Our main use case for Traefik Enterprise involves our IT team being lean, so the rework of certificate configuration, especially in the case of Let's Encrypt, leaves something to be desired. What we needed was a solution that centralized certificate control and also made it easier to maintain services and access. That is basically our main use case.

Besides that, we also needed a way to expose application metrics, looking at it from the HTTP side, specifically how many requests were successful, and how many had issues. The access log solution also met this need very effectively.

I would add that the metrics part of Traefik Enterprise, which I found very interesting, helps us know how much we are really serving the internal customer. We currently use it for the company's internal applications.

This visibility has impacted the IT team's routine mainly by improving certificate management, helping us avoid having to configure the certificate on each server. We are doing TLS termination at the edge, and the rest of the traffic is all private with the applications we have internally, making it much more secure and centralized.

Traefik Enterprise offers excellent features mainly including the exposure of metrics, which I have already mentioned. The fact that the tracing part can also be enabled is a very positive point, especially because when you have distributed systems or when you have a proxy itself, you need to understand where the bottleneck is. Traefik Enterprise makes these small modules very clear for you to enable: the access part, which is the access log; the metrics part; and the distributed tracing part.

Traefik Enterprise has a positive impact on my organization mainly by providing visibility and data governance. Knowing whether something is being accessed or not and whether the service is healthy or not is much more straightforward when you have a proxy in the same format as Traefik Enterprise.

Traefik Enterprise could be improved in some ways. For example, dynamic.conf is a way for you not to have to keep restarting the service. It would also be interesting to have another option for us to add entry ports to the service. Today we are using it with Docker, so we need to be careful with service maintenance to avoid any type of downtime. Something along those lines would be interesting, or perhaps some way to validate a rule before it could cause any issues.

The middlewares are very good, but I would like to mention one point. The problem I see today with the middlewares is that they do not add rules. If I configure, for example, one that will ensure access is only allowed from three IPs, and then I create another one where I would like to add more IPs to this rule, when I attach both to some router, what it does today is reach the last router, see that it does not have any of the other IPs that were added in the other middleware, and it drops the connection, returning a 403. It would be interesting if it were able to understand that these are additions of IPs to an allowlist instead of performing explicit denial based on the last middleware.

I have been using Traefik Enterprise for a short time, actually, as we have been using it for about two weeks.

Traefik Enterprise is very stable. The memory consumption is not lower than HAProxy, but it is stable and low in our opinion. It works well.

Traefik Enterprise scales effectively as I barely noticed any peak in memory and CPU, so I think it is handling the load very effectively.

I have not needed to contact Traefik Enterprise support yet.

I did not previously use a different solution.

Since this is a proof of concept, I do not have a return on investment yet. We have been using it for too short a time to say that it has paid back everything that was invested. In fact, we are in the process of implementing it on some services. However, I would say that improving the security of application access is already something positive because there were at least two or three applications that were previously accessed via IP that we moved to DNS, and the certificate is now managed by Traefik Enterprise.

On a scale of one to ten, I would rate Traefik Enterprise a nine.

Since this is a proof of concept, I do not have a return on investment yet. We have been using it for too short a time to say that it has paid back everything that was invested.

I have to leave out the pricing part because since I am in a proof of concept, I still do not have complete information on that. However, I saw that there is the Traefik Hub option, and we are evaluating it to see if it makes sense.

Before choosing Traefik Enterprise, I evaluated another option, which was HAProxy.

My advice for others considering using Traefik Enterprise is to proceed without fear and run a proof of concept while taking advantage of the benefits of a metrics exporter such as Prometheus, which is also integrated, and the access log, which helps considerably with environment visibility. I would rate this product a nine overall.

Public Cloud

Amazon Web Services (AWS)

My main use case for Traefik Enterprise is using it as an Ingress Controller with Kubernetes. A quick and specific example of how we use Traefik Enterprise together with Kubernetes is that we are using it inside our clusters to expose our .NET APIs and microservices externally in a secure way.

One of the best features that Traefik Enterprise offers, without a doubt, is the advanced control; we are able to have native protection directly at the entry point, with the OWASP Top 10 and the WAF. We can apply advanced centralized authentication, and we also have multi-cluster SSL and traffic splitting.

Traefik Enterprise has had a positive impact on our organization because we did the migration and even tried using other tools for Ingress, but at the time, Traefik performed better because we could have greater control, and it also had dashboards; the way of managing it ended up pleasing the infrastructure people and the developers as well. The team here moved away from a more manual mindset of constantly monitoring to a more strategic view. Traefik Enterprise gave us that with the dashboards. In terms of the tools, it practically never caused problems. Our infrastructure team had been doing load balancing manually, and Traefik Enterprise solved and eliminated that. We gained more time; the team can focus more on complex tasks and more functionality.

I do not see many points for improvement in Traefik Enterprise at the moment; the only point might be the documentation—making it available in more languages and a bit more friendly for those who are just starting out, because we had some difficulty at the beginning and had to look for some information and courses elsewhere. Documentation in Portuguese and much more friendly, more comprehensible content would be interesting.

I have been using Traefik Enterprise for two years.

Traefik Enterprise is stable.

In terms of scalability, one of the best things is that we can separate the control plane from the data plane.

We have never needed to contact customer support for Traefik Enterprise.

We were not previously using a different solution because it was the first time we made this migration from an on-premises system to microservices, so we were not using anything at that point because the application and other things were legacy, so it was not possible to use one.

After we acquired and started using Traefik Enterprise, we saw an improvement in terms of time, a reduction in people doing more basic tasks; Traefik Enterprise manages that well. There was time saving; developers or the infrastructure team worry less about those tasks.

I did not have that experience with pricing, setup costs, and licensing because governance handled that part more; I basically studied, understood the tool, and recommended that it would be the best purchase or the best decision to be made for the company.

Before choosing Traefik Enterprise, we evaluated other options. When we started the project idea, some people told us about Nginx. We were even already using Nginx on WordPress; it was totally separate, and it was actually a third party that managed it. They told us about Envoy as well, but we were between Nginx and Traefik Enterprise. In the end, we ended up using Traefik Enterprise because it is more dynamic and better; it has route discovery and is a bit easier to deal with and requires less work.

My advice to others who are considering using Traefik Enterprise is to focus on the basics, on understanding the infrastructure and how it works, so you can always get the best out of the tool. I have no other comments about Traefik Enterprise before we finish. I give this review a rating of ten out of ten.

Private Cloud

Other

My main use case for Traefik Enterprise is as a reverse proxy, doing IP isolation. The main idea was that when clients make a request to an application, the servers cannot see the final client's application and vice versa.

I can go deeper into how I configured the isolation in Traefik Enterprise. Isolation is normally achieved by separating traffic through entry points, routers, middlewares, and namespaces. I did it in Kubernetes or sometimes in Docker. The advantages of the isolation were greater security, as one application cannot directly access another application's traffic, less impact from failures if an application has issues or there is a failover. It does round-robin directly so that it continues working on another server, there was better administration, and there was also better control compliance.

All of the documentation is available on the internet and it is very good.

I consider the best features that Traefik Enterprise offers to be the Dynamic Configuration. Traefik Enterprise automatically detects our services in Docker or in other applications without needing to restart it. It has intelligent load balancing, so it distributes traffic between several instances of an application, doing round-robin. It is essentially a reverse proxy and routes the traffic. It has very good integration with Docker and with Kubernetes and offers the security of TLS termination.

A function of Traefik Enterprise that pleasantly surprised me in my experience could be the integration with Kubernetes, which is probably the strongest integration because it automatically discovers new services, updates the route without restarting, integrates with Ingress and CRDs, it works very well in microservices environments, and also with Docker, it automatically detects new containers.

Traefik Enterprise has positively impacted my organization because it automates the integration of new services, especially the ones I already mentioned. It reduces manual configuration since it automatically detects services, centralizes routing, makes deployments easier without affecting users, and it has resulted in a lot of cost reduction because the licenses, for example, compared to other technologies such as F5 proxy, are more expensive.

Although the documentation of Traefik Enterprise is good, for advanced functions it can be complex for those who are starting. The learning curve is sometimes a bit difficult to understand how they are related. The graphical interface is also a little complicated at times, and some integration examples could be improved.

I have been working in my current field for approximately three and a half years.

I consider Traefik Enterprise to be stable in my experience.

I find the scalability of Traefik Enterprise to be highly effective. It can run in multiple instances, distributes traffic among several servers, integrates very well with other applications, and can handle dynamic changes.

I have not used the customer support of Traefik Enterprise.

I was not using any other solution before implementing Traefik Enterprise. It was directly Traefik.

There was an issue to do the deployments with Docker, but everything worked correctly. After that, everything is automatic and it quickly recognizes the containers. This was not in my current organization but in a previous one, and in this one I do not use Traefik Enterprise.

My advice to other professionals considering using Traefik Enterprise would be to start with a test environment before implementing Traefik Enterprise in production. It is important to understand concepts of routers, services, middlewares, endpoints, and load balancing. If you work with Kubernetes or Docker, it is worth learning how Traefik Enterprise integrates with these platforms since that is where it shows many of its advantages. I would also recommend reviewing the official documentation and performing tests to become familiar with the configuration and best practices before deploying it in an enterprise environment.

I can give you a specific example of how the cost reduction or automation was reflected in metrics or tangible results. It greatly reduced administration since there were no longer people who had to be routing services and discovering information all the time. There was better use of the infrastructure and deployments were faster, which had a huge impact on the collaborators and cost reduction.

Traefik Enterprise has positively impacted my organization because it automates the integration of new services. It reduces manual configuration since it automatically detects services, centralizes routing, and makes deployments easier without affecting users. It has resulted in a lot of cost reduction because the licenses, compared to other technologies such as F5 proxy, are more expensive.

I did not evaluate other options before choosing Traefik Enterprise. I only chose Traefik.

I have been using Traefik Enterprise for about a year, and I was using it for routing for some external applications. On a scale from one to ten, I would rate Traefik Enterprise an eight.

The factors that influenced my decision to give it that rating of eight include that the learning curve and the initial complexity can be an obstacle for some teams, and in practice, it is sometimes a bit complex to understand in the documentation.

Everything works well with Traefik Enterprise.

On-premises

I have been using Traefik Enterprise for the last six months. Nginx Ingress for Kubernetes has expired and nobody is supporting it anymore, but we have another alternative in Traefik Enterprise.

I am using Traefik Enterprise for Ingress Kubernetes to proxy our applications from clients to our services. I work just with clouds, so all of them are installed on the cloud. I have an on-premise private server where I installed Traefik in Kubernetes, and one on-premise from my client where we are using Traefik as well.

Traefik Enterprise helps with proxying our applications because otherwise, you need to install something heavy like Ingress Kubernetes or Istio service mesh. However, not every client needs to have a heavy installation of a service mesh. Most clients only work with HTTP, and for them, Traefik is enough for my needs.

I am using the free version, and the best feature is that it is easy to use. Traefik Enterprise brought us an easier way because we faced a problem with Ingress Nginx. In this case, we needed another tool which could replace our current stack. We found Traefik easily and discovered how it is installed. When you have some more specific cases on Ingress, Traefik may not be enough, but in most cases, it is easy to work with it.

I am still exploring Traefik Enterprise and reading the documentation. I need a little bit more expertise on it.

With Traefik, there are a lot of files that should be specified for Traefik. With Nginx, we have one file, which is Ingress Nginx, but with Traefik, there is more than one file you need to configure to work it as well. For example, when you are working with CORS policies or any kind of specific configurations.

It saved a lot of time when we faced replacing Nginx, and it saved maybe weeks of work for our DevOps department.

I have been doing this for over six years. I started my work as a software engineer, and right now I am working as a DevOps engineer.

Traefik is working well. The accuracy and reliability of the output is working fine for me. I do not care about Ingress too much, and Traefik is closing my tasks shortly. I love it.

Traefik in the free version supported all security patches, and it is maintainable. In this case, I feel it is secure, but you need to configure a little more about CORS policies, rate limits, and others by yourself. All about the security patches are coming and working well, so I do not have any issue.

It works well. It is deploying one pod and working as well. I do not have any issue with it. I have B2B clients who have B2C clients, not more than one thousand or two thousand, and it works as well.

I have worked with the service mesh Istio, and it was kind of heavy for clients which do not have true heavy products. In this case, I changed back to Traefik and it works.

I did not switch from Traefik to any others. I tried before service mesh, Gateway API, and Ingress Nginx, but the most reliable for me right now is Traefik.

Traefik Enterprise brought us an easier way because we faced a problem with Ingress Nginx. In this case, we needed another tool which could replace our current stack. We found Traefik easily and discovered how it is installed. When you have some more specific cases on Ingress, Traefik may not be enough, but in most cases, it is easy to work with it.

With AI, I spent maybe twenty minutes on the initial setup.

It saved a lot of time when we faced replacing Nginx, and it saved maybe weeks of work for our DevOps department.

I cannot say clearly because I did not check it.

Because it is easy to use. As I said before, it is easy to replace our current Nginx. We need to add some additional configuration files in some cases, depending on the clients, for CORS policies and others, but it supports the same implementations as Nginx. I love it.

I have worked with the service mesh Istio, and it was kind of heavy for clients which do not have true heavy products. In this case, I changed back to Traefik and it works.

I mean about the configuration. That is all that I know for now. My review rating for Traefik Enterprise is ten out of ten.

On-premises

Other

Traefik Enterprise serves as an ingress controller for Kubernetes infrastructure and virtual machines.

I appreciate Traefik Enterprise's automatic service discovery feature because it truly helps with deploying containers for our Kubernetes workloads.

The best features Traefik Enterprise offers include automatic service discovery and excellent integration with GitOps. The automatic service discovery helps us with automation, meaning we don't have to perform any manual work when deploying workloads; this goes a long way in making developers and engineers more efficient at their work, allowing them to focus their attention on other tasks. Regarding the GitOps aspect, it integrates very well with Argo CD, but I cannot give more details due to some NDAs.

Traefik Enterprise has positively impacted my organization by making myself and my colleagues more efficient, allowing us to invest more time in other tasks because we are comfortable knowing how Traefik Enterprise operates and the automation we implemented with it.

Traefik Enterprise could improve with support for other products, but it's fairly complete. I don't have any specific improvements to mention because we have everything we need.

I have been using Traefik Enterprise for almost six years.

Traefik Enterprise is stable.

Traefik Enterprise is scalable, and we didn't have any issues with uptime.

Traefik Enterprise's customer support is very good. I would rate the customer support 10 out of 10.

Positive

We previously used Nginx Proxy Manager, but we evaluated Traefik Enterprise and saw that it had more features and was better suited for more customers.

We have seen a return on investment with Traefik Enterprise because we saved time.

Before choosing Traefik Enterprise, we evaluated Nginx Proxy Manager among other options.

My advice for others looking into using Traefik Enterprise is to be patient; although the initial onboarding is somewhat complex depending on the environment, once Traefik Enterprise is set up, it will be easy to manage, and the automation itself is worth it. I have no additional thoughts about Traefik Enterprise. I rate this review 10 out of 10.

Hybrid Cloud

Microsoft Azure