ngrok

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 )

What do you like best about the product?

I use ngrok to expose my local apps to the internet for testing, sharing, and handling webhooks without deploying them. Ngrok solves the problem of accessing my local development environment from the internet. It lets me test APIs, webhooks, or share my app with others instantly without deploying it to a live server. What I like most about ngrok is its simplicity and speed; it instantly gives a secure public URL for my local app so I can test and share it without any complicated setup or deployment. I value how its key features make development fast and efficient. The ability to generate an instant public URL allows me to quickly share or test my local app without deployment. The webhook support helps me handle real-time responses from external services without deploying the app, and the request inspector allows me to easily monitor and debug incoming traffic. These features save time and make the whole workflow much smoother.

What do you dislike about the product?

Ngrok could be improved with stable URLs in the free plan, better connection reliability, and fewer restrictions on advanced features. It can also feel limited for long-term use since sessions expire quickly, and managing multiple tunnels isn't very smooth. Adding more flexibility and reducing dependencies on upgrades would make it more convenient for developers.

What problems is the product solving and how is that benefiting you?

I use ngrok to access my local development from the internet, allowing me to test and share apps without deploying them. It gives a secure public URL quickly, letting me handle webhooks and debug easily, which saves time and streamlines development.

My main use for ngrok  is to generate a URL. I made a project recently and I generated a link for it so I can use it and share that with anyone so they can use it.

I was building an HTML to PDF and PDF to Base64 converter. The project was a bit complicated and took one or two days to complete. It was handling our main server, the Probus main server. We get a response in HTML, convert it into PDF, and then save the PDF as Base64 in our database. The project converts two HTMLs to PDF, or one HTML plus one PDF to Base64, and two PDFs to Base64. This bot combines them and ensures they are saved in Base64.

Sharing the ngrok  link helped in my workflow because my colleagues were able to use it to test it for our server. The project was handling around 5,000 to 10,000 customers every day, so we had to test it to ensure it would work properly in production.

My main use of ngrok in my daily work is to make a public URL for my projects. I am working on my voice agent, similar to Samantha, and it was fun doing it. The top three features I use every day are sharing local links and testing new features of ngrok, such as a payment gateway webhook. Since we don't have our own payment webhook in Probus, we are testing it. I thought ngrok would be the best option.

ngrok has positively impacted my organization by making development easier because we can check and generate our public URL. It is saving more time, reducing stress, and allowing us to work faster. We can share a link with our teammates so we can check it and do everything we need.

After using ngrok for our first project, which was HTML to Base64, HTML to PDF, and PDF to Base64, it worked on the first attempt, so we saved a lot of time. Then we generated our main server, uploaded it to our server, and generated its API. Because of ngrok, we saved two or three days on that project.

The best feature of ngrok is the instant public URL. We can use it for a secure URL with HTTPS by default. It works as a web inspector and is very useful for debugging webhooks and APIs. Additionally, custom subdomains are a valuable feature. I generated my custom subdomain for fun. My name is Suraj, so I generated suraj.ngrok.something. It was very fun doing it.

I don't think there's anything to improve in ngrok right now.

I have been using ngrok for one year.

ngrok is stable.

The scalability of ngrok is huge, and we can use it in many ways.

Customer support for ngrok was good, but I have not used it recently.

I did not previously use a different solution. I searched on ChatGPT and it suggested ngrok. I used ngrok, and it was the better option I could have chosen.

Setting up the tunnel and generating the public URL with ngrok was very easy. I even suggested my company subscribe to or get a paid plan for it. The company was paying for it, and currently it was paying for one month. I will make sure to have them purchase it for a year so I can use it precisely and perfectly.

We have seen a return on investment. I purchased it for seven or eight dollars, though I don't know the exact amount. It was a great purchase.

The pricing was decent and not much. However, it could be cheaper in India.

I don't think I will choose anything else right now because I purchased a monthly plan. I will not switch right now, but if I do, I will let the ngrok team know.

I would advise others looking into using ngrok to purchase it because it is more reliable and it saves us a lot of time. We should purchase it.

We are using ngrok right now as a private cloud and on our local computer.

I have nothing much to add before we wrap up. I would rate my overall experience with ngrok as a 9 out of 10.

Private Cloud

Amazon Web Services  (AWS )