ngrok Reviews

My main use case for ngrok is TCP tunneling for database and SSH, and I typically use it for those purposes.

Specifically, I use TCP tunneling for my Probus portal, and it is very useful for me since I have been using it for the last two years.

I use ngrok on my local machine to share my projects with others.

ngrok has positively impacted my organization because it is usually very scalable and very useful for us, as it saved a lot of time. We made our project live in one day, so our team can use it and test it on their end.

We saved about one week or two weeks just because of using ngrok.

In my opinion, the best features of ngrok are that we can use it for TCP tunneling for the database, and it also allows HTTP and HTTPS tunneling, along with many other use cases like authentication and access control, custom domains, and more.

I mostly use TCP tunneling and HTTP and HTTPS tunneling.

ngrok is very good to use and very user-friendly, so I do not think anything needs to be improved about it.

I will add suggestions if I encounter any issues in the future.

I have been working in my current field for the last six years.

ngrok is stable.

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

I have not used customer support right now, but I will let you know if I do.

We did not use any other solution other than ngrok.

My experience with ngrok's pricing, setup cost, and licensing is that currently we are using a one-month plan, and we renew it every month, with plans to shift towards the one-year plan in no time.

We see a return on investment with ngrok; there are many benefits I can list down, such as very easy setup, no need for hosting, great for debugging, real-time request inspection, and many more.

My experience with ngrok's pricing, setup cost, and licensing is that currently we are using a one-month plan, and we renew it every month, with plans to shift towards the one-year plan in no time.

We are not looking for any other option; ngrok is good.

I suggest everyone use ngrok. I have rated this review 9.5 out of ten.

On-premises

I mainly use ngrok for testing APIs, first locally, and then directly making a URL out of it using ngrok and sharing it with my team members so that they can test it on their side. For example, if I have been making any API of a database, then I can give that to any team member or front-end developer, they can test it from their side and we can see whatever is missing.

Beside this development, I am keen about working in the domain of machine learning. I am just a beginner, but still I try my best to train the model and then make certain types of APIs from it, and I can share my ML models' demos, either in interviews or with any senior.

As I mentioned, I have started working in URLs and APIs from the past six to seven months. At first, it was hard to make any changes and then test it locally, but if any team member of mine needed it, we had to go through and upload it, checking in on AWS, Azure, or GitHub. Then we had to solve the merges and merge conflicts, and then my team member could check out from that and get the latest version of whatever I had built, and then they could test it. Since ngrok has come, it has been easier and faster to test APIs from one system to another system globally.

ngrok helped my team in both ways. It makes it a little easier as we don't have to make every build whenever the API has needed some changes or testing, and the work has been faster because I can just directly make it in the form of a URL and my team members can check it out.

One of the best features is that we don't need any type of deployment. ngrok can directly turn my local URL into a global URL, and any other teammate of mine can check it out. Another feature is that it's HTTPS by default, so there is no need of SSL and no headache of SSL. Besides that, it gives developers like me a debugging power, so we can fix API bugs and save our time.

Every URL should be HTTPS secured, so it's very much convenient for me that my local URLs are directly going to convert into a global URL with HTTPS secure. As far as the debugging power is concerned, I can exactly see the request-response, my team members can see it, and we can help each other to fix API bugs faster and save time.

Mainly it helps with working faster and teamwork.

As the technology evolves, I believe that ngrok will also evolve, and with evolvement, it can make their system even better. The URLs that change every time would be something I would like to see fixed in the future. Besides that, I don't have any problems.

I have been using ngrok since more than six months, as I have been developing multiple APIs in my company.

ngrok is definitely stable.

It handles growth well. The scalability is up to the mark.

I don't have any interaction with the customer support till now, but from the frequently asked questions, I have gotten my answers from them.

I haven't used any other solution till now. I have been very much satisfied with ngrok.

It was easy and great. We got all the help that we needed. The doubt questions were cleared.

The suggestion of ngrok was from one of my seniors. I first tested it, and I liked it. The result was satisfying. I haven't gone through any other alternatives.

Definitely, one of the main advantages is time saved and money saved.

The suggestion of ngrok was from one of my seniors. I first tested it, and I liked it. The result was satisfying. I haven't gone through any other alternatives.

I would say that ngrok is mainly for those who are working with APIs because it has been a time-saver and it increases your teamwork with other members. I would say whenever someone is in the beginner phase of building APIs and working within a team, they should definitely try ngrok. I would rate my overall experience with ngrok as a 9.

On-premises

Other

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

My main use case for ngrok is when we want to use any webhook with the frontend or Android app, we need a backend server where we can debug locally. At that time, we use ngrok for making a port and providing that to the webhook.

In a project where there's a webhook, we want to see why payment is not happening and consequently why the subscription is not happening. For that, we need to debug.

That is the main use case for ngrok, being useful for production and a little bit about the debugging with ngrok.

ngrok has positively impacted my organization because we can easily debug, which is very beneficial when we make any feature and we want to debug using ngrok. It is a great tool for the company.

ngrok offers me the capability to debug locally, which is very beneficial.

ngrok's local tunneling capability has helped me in terms of speed, convenience, and overall effectiveness in my work.

ngrok has made development easier for me, and I have used it and found it to work well. It's a great development tool.

I don't think ngrok needs any improvements. For now, it works well, and I don't have anything more to add about needed improvements.

I have been using ngrok for the last two years.

ngrok is stable.

ngrok's scalability is good, as it's scalable.

I haven't used ngrok's pricing, but I think the support team is very good for me.

I have not used a different solution before ngrok; previously, I didn't use anything else.

I can say that I have seen a return on investment with ngrok in terms of time saved, although the overall development is not that extensive.

Regarding pricing, I think we have used the free tier of ngrok.

I used ngrok only and did not evaluate other options before choosing it.

On-premises