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.
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.
Artificial Intelligence Engineer at Probus Insurance Broker Pvt
Real User
Top 5
Apr 30, 2026
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.
I used ngrok a couple of times during my internship approximately eight to ten months ago. My main use case for ngrok was during my first internship, where I worked as a data science trainee on a RAG chatbot, which is an AI chatbot that I was building. To showcase the developments to my team and team lead, scheduling everyone on Google Meet was a hassle, but ngrok allowed me to put these test projects on the internet so they could be accessible and shared with other team members. ngrok definitely changed my workflow during my internship because I had to collaborate with around three team members and one team manager. Initially, I had to schedule Google Meets to share my work, which was time-consuming. By the weekend, I had to schedule another meeting with the team manager and team members. This lengthy process consumed a lot of my time, which ngrok completely replaced, allowing me to just share my work in a five to ten-minute setup.
AI Engineer at a tech vendor with 10,001+ employees
Real User
Top 10
Apr 29, 2026
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.
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.
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.
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.
Senior Software Engineer at a computer software company with 201-500 employees
Real User
Top 10
Jan 23, 2026
My main use case in ngrok is serving my local things, as ngrok is mainly used for exposure to my local server. For example, if I am using some internet and want to make it publicly available, I can run my website on localhost 3000, and ngrok gives a public link so that others can access it online. I have recently used it in my simple internal project for an email management system. ngrok should also be used for webhooks, testing and demos, and sharing local APIs without deploying.
Senior Trust Operations Data Engineer at DIGICERT, INC
Real User
Top 5
Dec 4, 2025
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 is a powerful tool that allows developers to expose local servers to the internet securely, facilitating easy and secure development and testing of web hooks and APIs.Utilized primarily by developers, ngrok streamlines the process of connecting local environments to the internet, enhancing testing, demos, and collaboration. Its ability to generate secure tunnels with minimal setup makes it a go-to choice for seamless integration and real-time development workflows.What are ngrok's most...
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.
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.
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.
I used ngrok a couple of times during my internship approximately eight to ten months ago. My main use case for ngrok was during my first internship, where I worked as a data science trainee on a RAG chatbot, which is an AI chatbot that I was building. To showcase the developments to my team and team lead, scheduling everyone on Google Meet was a hassle, but ngrok allowed me to put these test projects on the internet so they could be accessible and shared with other team members. ngrok definitely changed my workflow during my internship because I had to collaborate with around three team members and one team manager. Initially, I had to schedule Google Meets to share my work, which was time-consuming. By the weekend, I had to schedule another meeting with the team manager and team members. This lengthy process consumed a lot of my time, which ngrok completely replaced, allowing me to just share my work in a five to ten-minute setup.
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.
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.
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.
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.
My main use case in ngrok is serving my local things, as ngrok is mainly used for exposure to my local server. For example, if I am using some internet and want to make it publicly available, I can run my website on localhost 3000, and ngrok gives a public link so that others can access it online. I have recently used it in my simple internal project for an email management system. ngrok should also be used for webhooks, testing and demos, and sharing local APIs without deploying.
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.