ngrok Reviews

My main use case for ngrok is for development and testing. In my company, we use automation of document processing, and whenever I have to test it, I use ngrok so that I can verify the code is working locally.

I believe the best features ngrok offers are the ease of download and the minimal space it occupies. The terminal-like interface is very helpful in my daily work. When I first heard of ngrok, I thought it would be something new that I would have to learn extensively, but that was not the case. It was very easy to use with a simple command-line interface.

ngrok has positively impacted my organization since everyone uses it for development and testing. Without it, I do not know how we would test locally. Since then, we can only test it on our local code editor. It has made our work considerably easier.

ngrok saves a lot of time for my team. Previously, if you wanted to do development using a normal local code editor and then test it, you could deploy it directly. However, in production code, there is literally nothing to show what is causing an error, which would cost much more time and resources. With the use of ngrok, you can easily debug it.

Currently, I do not think there is anything about the features. Perhaps if I could run multiple codes simultaneously, that would be an improvement, as that was a problem I faced.

I think if ngrok supports multiple ports at one time, it would be an improvement.

For the documentation part, ngrok should provide an easy transition for legacy users. I think because of that, many people prefer an open source alternative such as a local tool over ngrok.

I have been using ngrok for six months.

ngrok is stable.

I believe ngrok is pretty scalable, but since our company was not scaling that much, I have not explored much.

I did not face any problem contacting ngrok's customer support. However, I believe someone from our company did face a problem, and the customer support was pretty helpful for them.

I would rate customer support as a nine since I did not experience it myself, but my fellow employees were very much impressed with the customer support.

I did not know of other options, but if I think of some options now, I can consider some local tools such as Local Expose and local tunnel. I believe these are popular alternatives to ngrok.

ngrok is something which I use daily. It is the first thing I open after starting my laptop.

I believe ngrok provides a good return on investment. Since we were using the free tier, it was giving us very good savings on resources and time. Even if we were to pay for it, it would be a good investment.

I do not know much about pricing, setup cost, and licensing since we were using the free tier, so I have not used the paid model of ngrok.

I did not know of other options, but if I think of some options now, I can consider some local tools such as Local Expose and local tunnel. I believe these are popular alternatives to ngrok.

I believe if someone wants to use the free tier and a good tool for their coding, then ngrok is the best. I would rate this review as an eight overall.

On-premises

My main use for ngrok is authentication and access control. ngrok has been very useful for me. I recommended my company to purchase a subscription because it helps me with authentication for the project I created and for verifying that the person is truly human. ngrok is very scalable and useful for our needs. We also used ngrok for public exposure.

The best features I use are authentication. ngrok offers multiple valuable features including HTTP, HTTPS tunneling, authentication, webhooks, and testing support. I find myself relying on authentication and access control the most.

ngrok is very user-friendly, which is my first preference. The second advantage is that it is more scalable. The third benefit is that I can generate solutions very easily. It is very simple to generate the functionality I need.

ngrok is very useful for me since I use it to deploy my projects.

On the free account, the link changes every time I use it. The pricing is decent, but I would prefer it to be a little cheaper in India compared to US pricing.

I have been using ngrok for the last year.

ngrok is stable in my experience.

I can rate ngrok's scalability as nine out of ten.

My company does not have a business relationship with this vendor beyond being a customer.

I have not tried any other solution. ngrok was the best option, so I chose it.

The setup was very easy.

My team used my project on a single server.

We saved a lot of time. My team used my project on a single server, which allowed me to save considerable time.

I have not chosen any other solution.

I recommend that others use ngrok at least once so they can have an understanding of it. I gave this product a rating of 10 out of 10.

Public Cloud

Amazon Web Services (AWS)

My main use case for ngrok is that when I boot up a server and want to test it non-locally, I can use ngrok to do that.

I created a Flask application and I wanted to make sure that it was performing in the way that I wanted it to, so I used ngrok to test it without booting up everything in production or development.

That's the only use case I have with ngrok; it's just good for testing, making sure the application that I've developed works in a quick manner, rather than having resources to boot it up.

ngrok positively impacts my organization by making deploying a lot easier, catching problems sooner without costing resources, as you can deploy it externally without it being external and see the problems to fix them fast.

The best features ngrok offers include creating an anywhere IP that's localhost but not localhost at the same time, allowing you to boot it up and see what your application is doing.

That quick setup with ngrok saved me money by not having the resources to boot up a development server or production, making sure my code is working in a dev server that is exposed in a way.

ngrok saves weeks of development time, as I am able to catch problems and fix them without deploying resources in dev servers or production servers.

I cannot think of anything for ngrok improvements, but knowing that you are able to deploy something externally without it being external is just the main reason I use it, and that is a game changer for sure.

Everything seems pretty simple with ngrok, and I love the documentation since it is really easy to use.

I have been using ngrok for a year.

ngrok is stable.

I am not sure about ngrok's scalability, as I just use it locally, so I do not know if it scales well or not.

I have not reached out for customer support, but I have noticed the documentation is very well documented; I was able to find answers on their website with no issues.

I did not previously use a different solution for my needs.

I have seen a return on investment with ngrok, as I saved time and can spot problems faster instead of spending that time trying to get code to work.

I have not done any costs for ngrok; it is just locally.

ngrok was my first pick, as it was the only thing I could find that could do what I wanted it to do.

My advice for others looking into using ngrok is that if you want to develop something and be efficient, you should use ngrok to deploy and check for issues externally. I would rate my overall experience with ngrok as a 10.

On-premises

Other