ngrok Reviews

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.

I work as a software developer at ADP and I majorly work with a lot of AI tools. My day-to-day work involves coding, shipping code, and deploying applications. Apart from my work, I also have an agency wherein we develop websites for clients, and we use a lot of AI there as well. My entire day is accumulated with coding and AI work.

We develop a lot of APIs and webhooks for the tech systems that we build, and I use ngrok for web testing and webhook testing. I also share demos with my teammates by exposing local APIs during development. As a team, we validate all integrations without deploying them to production or staging. We make sure to deploy everything in lower environments, replicate things, and test them thoroughly before confidently deploying into production.

The scope is very broad. I use ngrok anywhere to expose a local app, and all my teammates use it as well. We majorly cover webhook testing, local API exposure, and we share demos with teammates and clients. I also use it for debugging integrations and temporary public access for front-end and back-end builds. It saves a lot of time across development and QA. Additionally, we use it for demos and integration work. If I say the scope is big, it is quite big because especially for all the developers and QA engineers building APIs, ngrok is majorly the go-to tool.

I use ngrok in the web agency that we have outside of work. In the web agency, we are a team of eight people and we use it rigorously.

The best feature of ngrok is how quickly it creates secure tunnels for local services. The one that I use the most, and that my team uses the most, is the public tunnel URL because it helps me to test webhooks, share demos, and expose local apps instantly. We often use it the most, and my favorite would be the public tunnel URL.

ngrok has a few advanced features like traffic inspection, reserved domains, and more detailed observability options that my team and I haven't used much yet. For my day-to-day work, the basic secure tunnel and public URL are the features that I rely on the most. There are pretty advanced features that we are trying to explore now and probably use them down the line.

ngrok has positively impacted the organization because it was able to reduce the time needed to expose local services for testing, demos, and webhook integrations. It has helped teams to move faster, collaborate more easily, and avoid the overhead of setting up temporary public environments. On a holistic note, ngrok has a very positive impact on our organization.

The biggest friction point I faced with ngrok was the limitation on the free plan and the occasional need to manage sessions or URLs again. For very heavy use, the advanced capabilities are very useful, but some of them feel quite restricted unless you are on a paid tier. ngrok works very well, but the main frustration is when you need the same tunnel setup repeatedly or want more advanced controls. In those cases, you start to feel the pain.

I wish ngrok had more flexibility in the free or low-tier plans, especially around persistent tunnels, reserved URLs, and usage limits. It would also be very useful to have even better traffic analytics and easier collaboration features for small teams.

If I could change one thing about ngrok, I would make persistent tunnels and reserved URLs more flexible in the lower plans. That would make my workflow smoother because I wouldn't need to keep redoing tunnel setup for repeated testing and demos. Making persistent tunnels and reserved URLs more flexible in the lower plans would change my workflow by reducing repeated setup and making webhook testing and demos faster while giving the team more consistent URLs for local services.

I have been familiar with ngrok for about one year now.

Before ngrok, I was using manual port forwarding and temporary deployment setups. After ngrok, it quite simply simplified that a lot by giving me a secure public URL in just a few minutes, which I was able to use to show demos for clients in the web agency that we are building right now. Before ngrok, I had to rely on manual workarounds, but ngrok replaced that with a much faster and easier workflow.

When I was evaluating options along with ngrok, I considered manual port forwarding, local tunnel, and Cloudflare Tunnel. When evaluating options, I considered manual port, local tunnel, and Cloudflare, but ngrok stood out because it was easier to set up, more reliable, and it was better suited for quick development and webhook testing. When I started using it, I felt it was quite easy for my team to adopt it. There was no second question; we went straight to ngrok.

When I first implemented ngrok, the implementation was very quick to start running. If I remember correctly, it was a few minutes to start running. The first time I implemented ngrok, it was just about a couple of minutes or three minutes to get it running. Once my local app was up, creating the tunnel and getting a public URL was very straightforward. Most of the time was spent checking the local app and choosing the correct port, not on ngrok itself.

It was quite easy to pick up and my team didn't need formal training because ngrok was very easy to adopt and the setup was intuitive. We were able to start very quickly with the basic documentation that was available on the site.

For someone with a similar use case or for teams with a similar use case, I would recommend starting with a basic secure tunnel workflow using ngrok for quick testing and demos, and then moving to the paid plan if you need persistent URLs and more flexibility. I would ask them to start with the basic tunnel workflow and then once they are familiar with the workspace, they can move to a paid plan because they would get the persistent URL that they can use flexibly across the team.

One thing to know about ngrok is that it is excellent for quick, secure exposure of local services, but it is mainly a development and testing tool rather than a production hosting solution.

ngrok did change team collaboration because earlier it was quite a waterfall model. Everyone was developing and we were not given a chance to see the things that were built locally. Today, with ngrok, we were able to utilize the public URL and instantly demo the features that we develop. As a team, we held up the spirits because everybody is charged up to deliver quickly and to show the version that they have locally.

As a web agency with eight people on the team, ngrok has improved productivity for all eight people by reducing setup and debugging time. If each person saves just 30 minutes a week on webhook testing, local exposure, and demo setup, that adds about four hours saved per week across the team. Over a month, that is roughly around 16 hours saved, which is a very meaningful productivity gain. At a team holistic level, it was somewhere around 20 hours saved a week. That immensely boosts the productivity of the team.

The first thing that I would do is run a tunnel for the local port of the app that I am using. When opening the terminal, I would run something like ngrok http 8080 to expose the local service securely. That is the primary thing that I would do.

I would rate ngrok a 9 out of 10.

In my AI automation field, I have been working for around eight to twelve months.

The main use case where ngrok comes into the picture is when I create any development projects, which can be coded automations, websites, or any applications that I develop. I have to push it to the internet so that it can be accessible to the other team members or the managers who have to evaluate that. Instead of just running the coded project that I have in localhost, I push it to the internet using ngrok, which gives me temporary URLs for that, and I can share them with others so that they can access the project that I have built.

My use case with ngrok is mainly to push to the internet, and while I develop around two to three projects a month, I think ngrok could improve its free plan session limits so I could do more, though overall it has been a great experience.

I have used ngrok in my previous internships when I was in college, interning side-by-side in a data science internship, and that was where I was first introduced to ngrok.

The core objective of ngrok itself is very helpful and interesting for developers like me. Normally, one would either host completely from the get-go or go through a lengthy process of asking team members to join Google Meet sessions, sharing screens, and showing what one has been working on. But with ngrok, pushing it to the internet and generating a shareable URL improves the outputs from evaluations that others do since they can directly access the project instead of me screen recording and showing things one by one.

This is very useful for me to test, and not just for me, but for others concerned with the project or app developments that I have been working on, making changes based on evaluations that the others do using any project that I have pushed to the internet through ngrok.

One improvement I have noticed is when configuring integrations with external APIs like Slack. After a machine or session restart, I have to generate a new URL, forcing me to change the webhooks in Slack, which could be addressed for better functionality.

I have used ngrok in my previous internships as well. When I was in my college, was interning side by side and it was a data science internship that I have been interning for. And in that I started first, was introduced to a platform called ngrok.

ngrok has been stable since I started using it, although there are some restrictions due to the free tier. For my use, it is reliable enough as I do not develop many projects monthly.

ngrok is pretty scalable. While I have not done extensive usage, I have built from one project up to four projects on ngrok, and it has handled my needs well.

I am grateful I have not needed to contact customer support since ngrok's documentation has covered all the issues I encountered.

I did not use any platform before ngrok. Starting with ngrok during my internship was a revelation, as I had no prior knowledge of any such solution.

Initially, it was something very new to me, and I had not understood the complete idea behind it during my internship, but it was pretty easy. It takes hardly ten minutes to set the whole thing up. The documentation of ngrok is superb, so I did not have to waste time on YouTube videos to understand how to start. The setup is easy and secure, making it easier for me to onboard ngrok into my daily development life cycle.

I will give an example of the first project that I ever built where I had to use ngrok. In my internships, when I was building a RAG chatbot, RAG stands for Retrieval-Augmented Generation chatbot that I was building. I had to conduct two meetings each week with my team members and my manager or project lead. What I initially started doing was conducting certain developments in that project and then asking each team member when they were available, sharing the Google Meet URLs, and then screen sharing the whole project. Each team member joined in, looked at the project I was building, and shared their evaluations. That whole process was completely replaced when I got to know about ngrok. Instead of sharing Google Meet links, I pushed the project to the internet, generated a temporary URL, and shared it with the team members and the manager, which allowed for timely updates and better evaluations than just screen sharing in Google Meets.

Saved time is the most significant return on investment I have seen from ngrok. While I have not reduced the number of employees needed, I have saved time from sharing screens, taking screenshots, and creating presentations, which is now streamlined to just pushing projects to ngrok for access, saving me about eight to ten hours a month.

I would not say I have an accurate number, but if I had to estimate, sharing a website or project initially would take about forty to forty-five minutes, plus taking screenshots for documentation would add maybe eighty to ninety minutes, resulting in around one hundred eighty minutes or three hours a week and approximately twelve hours a month. By using ngrok, I have saved an estimated eight to ten hours monthly.

I primarily use ngrok in the free tier, which is superb. The setup is easy, and the documentation is outstanding, making it easy to resolve any issues I face without needing to contact customer support.

I did not evaluate other options. My team lead introduced ngrok to me during my internship, and I jumped right into it without exploring competitors, finding it to suit my needs perfectly.

A recent example is when I was creating a website for the company. I had to handle communication traditionally by asking team members to join Google Meets, share screens, show the website, or even take screenshots and compile them into a PDF or PowerPoint, which caused rushed feedback. However, since I knew about ngrok, I could push it to the internet and get temporary URLs for the team members and managers to access at their convenience, leading to better collaboration.

I recommend going through ngrok's documentation before seeking help or watching YouTube videos, as it usually resolves most problems. Start with the free tier to experience its functionality before considering the paid plans.

I believe I have covered all I know about ngrok and my experiences with it. 

I have been working here for about five months, and I used ngrok in the past for a specific use case. I do not use it anymore, but I used ngrok to serve my MCA project, which was a generative AI interior design system during my final year at college. I had two computers, one acting as the server hosting a stable diffusion AI model to generate interior design images and another Mac laptop serving as the front end. I created a front-end application on it and needed to bridge the gap, requiring the front-end API calls in Node.js to access the back-end API endpoints that I created on my other laptop acting as the server. ngrok was used for this purpose.

ngrok is only deployed on my local machine for my project.

The best features ngrok offers include real-time traffic inspection, which was very useful for debugging and trying to find out why certain calls were not working when routed from my front-end Mac laptop. Another useful feature is that the limits for the free tier are quite generous, as I needed to make many requests, and even then, I had enough requests to last me the rest of the month.

For debugging purposes, the feature of traffic inspection was helpful because I was making API calls and did not know if they failed due to issues with the front-end code, server code, or if the API call was simply not getting routed to the server code on my secondary laptop. To decipher these issues, traffic inspection was certainly useful. Although I do not remember using it frequently, it was definitely beneficial, and the free tier mostly met my expectations. I only remember one instance of reaching a limit, which happened because I was making API calls every ten seconds for a couple of minutes. Once I adjusted that to every thirty seconds, it became more than enough, and I was not hitting any limits.

ngrok positively impacts my organization in several ways. I was not technically working when I used this software; I was in college on my final year project. It definitely saved me a lot of time, and more than just time, it probably saved money because I would have otherwise had to pivot to paid software. Considering it was just a proof of concept, it was not something I planned to deploy and earn money from. For a simple college project, ngrok was more than enough and definitely met my needs.

I really had to think about any potential improvements to ngrok, but I do not think there was anything that frustrated me. When I hit the limit for the first time, I was taken aback as I was not paying attention, and at that moment, I wished the limits were a little higher. All I had to do was wait for the limit to reset the next month, and I even created another account for a free tier initially. Eventually, I decided to stick with one account and wait for the month to reset. I never reached a point where I needed to spend money, as this project was not meant to last very long, so honestly, I do not have any complaints.

Setting up ngrok on my laptop was straightforward. It has been about one and a half years now since I set it up.

ngrok has been stable for the amount of time I have used it. It has been one and a half years now, and I find it reliable.

ngrok's scalability is decent, but I do not remember paying too much attention to these details as I did not use it very much.

I am sure customer support is good, but I never had to reach out. I found everything I needed from online resources.

I did not previously use a different solution for this kind of task; ngrok was the first one I came across.

Setting up ngrok on my laptop involved several steps. I was looking into various services to achieve this goal and asked ChatGPT, which first suggested ngrok. It guided me through setting up ngrok on my Windows laptop acting as a server. I had to log into the website, create an account, and go through a bunch of setup steps. I remember downloading some software, running a variety of commands in the terminal, and eventually created a Node.js script in Visual Studio Code. Somehow, everything worked together, and I could access this remote server from my other laptop.

As for setup, it was quite simple and did not take me long; I just followed a set of instructions from ChatGPT and was done.

If I had to estimate the amount of money I saved by using ngrok, I would say maybe around twenty dollars. As for time, I saved at least seven or eight hours that I would have spent trying to find a solution to the API gateway connectivity issue I faced.

I did not really save any money apart from what I would have saved if I had to pay for a paid tier of ngrok since it was a college project and I did not use it in production or development.

I did not evaluate other options before choosing ngrok; I just went with it because ChatGPT suggested it and it seemed to fit my needs.

Besides what I have already said, I can say that I used only the free tier and it was very useful. It did not surpass my expectations, but it definitely met them, doing a good job in that regard, and I had a good experience with this software.

ngrok is only deployed on my local machine for my project.

My advice to others looking into using ngrok is to not overthink it and just go for it since it is going to serve most of your needs. If more credits are needed, you can always purchase them. Apart from that, I do not think I have anything more to say.

I have covered almost everything I wanted to say about ngrok in this interview. I would rate my overall experience with ngrok an eight out of ten.

As a full stack developer, I utilize ngrok for running my local development server to the internet so that I can get a public URL, which could be utilized for testing, debugging, or sharing with clients.

In my current project for an application, we had to rely on webhooks, such as payment gateways or external services, so I used ngrok to expose my local server to those services that can send real-time data to my machine.

It is also helpful when I need to quickly share a work-in-progress feature with clients or teammates without having it deployed on the environment. This bypasses the testing and helps me prevent merging the in-progress code onto the environment while still allowing visualization through a public internet URL. Another use case is for Apple Pay integration, which does not work on localhost, so for that, I used ngrok to get an HTTPS URL.

ngrok has helped in many ways, specifically providing development support for features related to payment, such as Apple Pay, which cannot be tested on localhost. It allows us to share our localhost with team members, such as front-end developers, so they can utilize the API and integrate during the development flow, aiding in collaboration between back-end and front-end developers.

ngrok has helped in faster development and collaboration, allowing both teams to work in parallel without blocking the development flow. It provides benefits such as sharing public URLs for sensitive integrations, allowing clients to check in real-time, and is beneficial for performance testing with temporary URLs to identify challenges early on.

There are many features with ngrok that I have utilized during development, such as temporary public URLs, secure tunnels, request inspection, support for custom domains, and authentication, which makes it secure to utilize. In sensitive cases, such as integrating payment gateways, we need to ensure we are not exposing unnecessary things on the internet, and it goes through a secure tunnel.

There is a specific feature for request replay that makes it very useful for debugging and testing whenever a request has been hit with ngrok. This request replay feature is amazing.

ngrok is already a great tool with various tiers for free users and paid subscriptions, so I do not see any caveats as such.

In terms of features, ngrok is very feature-rich and reliable, but with heavy usage, the costs can increase based on the usage plan, which could be improved to be a little cheaper.

I have been using ngrok for the last two years.

ngrok is very stable, as we have not faced issues while running multiple servers and APIs, and it is fast and scalable.

ngrok is highly scalable, allowing multiple servers or URLs created within the same account, facilitating smooth collaboration among multiple teams and developers.

The customer support was really amazing, as they have always been proactive in responding to our queries or issues related to access.

We purchased ngrok directly by contacting their sales team because we are a large organization, and they offered us a bundled package.

We have not been utilizing any older solution, as we actually started with ngrok only.

The pricing is quite good, especially for the features it provides, and the sales and customer support teams are always supportive, making it very smooth to onboard our developers with ngrok, leading to a great overall experience.

We evaluated Cloudflare Tunnel as an alternative, but we found that ngrok is generally more reliable and feature-rich, which best suited our use case, leading us to choose ngrok.

Overall, ngrok is a very useful tool for developers, simplifying local testing, especially for APIs and integrations, which helps speed up the development workflow and identify issues early on.

Overall, I think ngrok is a great tool that will definitely help any organization, whether mid-scale, small, or large, by enabling dynamic collaboration early in the deployment stage and allowing teams to see their APIs live as they would behave in a real environment. It provides a glimpse of that, making it definitely a tool worth trying. I gave this review a rating of ten out of ten.

I have been using ngrok for almost a year. My main use case for ngrok was in a project I was working on where I used a webhook for a WhatsApp bot, and I needed ngrok. In my WhatsApp bot project, I needed a public URL to link my WhatsApp bot to Gupshup so any user or myself for testing or development could message on it, and the bot could work on the local machine. For that I needed a public URL, and ngrok provides it very quickly.

In another project, I used ngrok to create a public URL for our company's website to test it on mobile, as none of the servers were free for testing.

ngrok offers excellent features including how quickly it operates, how easy it is to set up, and it is free for use for a limited time, though it does have a good amount of latency which I consider a drawback.

The setup was easy because there was a simple one command, ngrok http and the port number. As for latency, it was generally fast except for some issues such as in a document uploading process for a WhatsApp bot, which took more time than on a server, increasing latency.

ngrok has positively impacted my organization for development and testing purposes, making it very easy for my teammate to check a website or my local machine code for review.

ngrok could be improved by reducing small latency issues. For pricing, it would be helpful to list the pricing structure at the start since a free user might not know it has only one URL for the free plan. Security could be improved in ngrok because it is mainly for development and testing purposes, not production environments, and improving security would have a huge base to cover.

I have been working in my current field for more than a year.

ngrok is very stable.

I did not have to contact customer support because it was that good to use. I only faced the latency issue, but I understand you cannot provide everything in the free tier or people will not use the pricing.

Since I mainly used the free version, I would not have specific metrics to share regarding return on investment.

The setup was easy because there was a simple one command, ngrok http and the port number. As for latency, it was generally fast except for some issues such as in a document uploading process for a WhatsApp bot, which took more time than on a server, increasing latency.

I mainly used the free version for my personal and company needs as the main user, so I did not have to pay for anything.

Regarding pricing, setup cost, and licensing, I mainly used the free version for my personal and company needs as the main user, so I did not have to pay for anything.

Before choosing ngrok, I heard of the Cloudflare option, but ngrok was quick to set up and easy to use, making it my first choice.

The specific outcome my team experienced is easier collaboration. I have been fortunate enough to use ngrok as my first solution, and it was so good that I did not need to switch to anything else. My advice to others looking into using ngrok is that if you want easy collaboration, testing environments, and development between teams, it is surely the way to go. I would rate this product an 8 out of 10.

I used ngrok when I integrated with the payment Amazon payment web service to handle HTTPS during development, not in production. When I worked locally, I did not have HTTPS, so I used ngrok to make the connection easy with the webhook. I also used it when I integrated with Fireblocks and Circle for cryptocurrency. Additionally, with my team, sometimes we needed to test something on my local machine. For example, a front-end developer would ask me to act as a back-end. I would give them the ngrok URL of my local machine, and they could connect and test or establish our API contract to ensure it worked before we uploaded it or pushed it to the cloud or the branch.

I used ngrok when I wanted the webhook of the Amazon payment service to call me when the payment was completed successfully, when the user made a purchase, or when a refund happened. This was because I wanted to depend on the webhook, not on the user interface, to ensure that the payment had already happened or the payment was refunded successfully, or if there was an issue.

When I integrated with Amazon payment, I worked on it first on my local machine and wanted to test the webhook before I pushed my code to the development server. I sometimes edited much of my code to ensure everything was working correctly. This made my productivity very quick and allowed me to finish my task very fast. This was because I could call the Amazon payment via an HTTPS link locally without having to push every time to the development server and wait for the deployment or pipeline to finish before starting. When I push my code, have a code review, and then test, it might take fifty minutes or twenty minutes, which would waste my time. When I worked on it locally and tried to fix the errors by using ngrok to ensure the task was clear and the integration was completed successfully, then I pushed my code to the development server. That did not waste my time; it saved my time. I save one or two hours. That is great for me, and it does not create a bottleneck for my colleague to review my code.

It is easy to install ngrok on my local machine. It is also very quick. I can install it and enter the port I want to generate the HTTPS for, and it works. That is very helpful and a great thing. It is easy.

Because I am using Linux, I just enter the installation command and use ngrok. It is very quick for me.

Because I think maybe some other people will have suggestions for improvement that I do not have, I give it a nine, but for me, it is a ten. To make it a very easy and user-friendly experience, I will give it a nine.

I have been using ngrok since 2020.

I give this product a rating of nine.

I preferably work in Python backend use cases. As a Data Engineer, I use FastAPI and build my code in Python. To create an API for front-end developers, I use ngrok.

I made an automation platform for the finance team in our office, where I serve as a backend engineer. Since I work in the data field, I use backend technologies. The backend code is entirely written in FastAPI. I need to give the API to front-end developers to embed in their code. Since the project is completely developed locally, I used ngrok for obtaining the APIs.

I used ngrok to get APIs. I built three modules: the user module, customer module, and finance module. For each module, I used separate APIs. Taking the ngrok URL as a constant and adding the other methods like POST and GET and whatever API I need to call, I used ngrok for my end-to-end backend.

The free tier of ngrok is one of the best features it offers. Initially, I used the free tier, and it gave me more tokens. Even when my API received many hits from the front end, I was able to use this ngrok backend API without any problems.

ngrok is very reliable.

When building our internal automation forms, we use ngrok for the backend part. It provides an easy step and is beginner-friendly, allowing us to integrate easily and test. Testing it in Postman and other tools is also very easy.

I was able to easily give my ngrok URL to the front-end developer. Development of APIs using ngrok is very fast.

Before going into the production environment, this ngrok free tier was actually saving our time and benefiting employees.

ngrok can be improved in the following way: when we unexpectedly close the laptop or sometimes close the page where we are running ngrok, that can be improved. The time limit for this can be extended.

I have been using ngrok for more than a year.

ngrok is stable.

ngrok is also scalable. I was able to use it in many other use cases as well. It is good for scalability.

The customer support is friendly and we were able to get our solution.

Positive

The pricing was reasonable and the initial setup and licensing were also good.

The pricing was reasonable and the initial setup and licensing were also good.

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.

I use ngrok to make a random link and then share that link with my client or my users so that they can use my project.

ngrok has saved a lot of time for my organization, and it is more scalable than the website or any other application.

Our team saved a lot of time using ngrok, which is why we recommend it.

We have saved a lot of time and teamwork thanks to ngrok.

ngrok is very stable and scalable.

The product is scalable and stands out for me as a 10.

We are using ngrok locally right now.

We are using the free version of ngrok and will shift to a one-month plan in no time.

I would suggest trying the ngrok plan first.

I don't have any additional thoughts about ngrok before we wrap up.

I am providing this review a rating of 10.