Overview
Unlock the power of Saas to deliver high performance applications and APIs with zero networking configuration and zero hardware. ngrok is a global delivery network that enables the following use cases:
- Ingress for dev/test environments
- Ingress for external networks - customer environments
- Ingress for external networks - devices and machines
Ingress for dev/test environments: ngrok equips developers to connect their localhost or dev/test/sandbox environments with just one command, making it easy to test apps and APIs. Developers can test integration with webhook providers and external APIs, preview websites and apps with fellow team members and validate mobile backends instantly. There is no need to spend time and effort tweaking network configurations on firewalls, proxies and gateways. ngrok reduces the time it takes to develop, test, and debug apps, boosting developer productivity by freeing them from having to navigate complex networking and firewall configurations. The platform comes with robust security and control capabilities such as SSO, mTLS, IP restrictions that enables SecOps and NetOps teams to apply and enforce security policies.
Ingress for external networks - customer environments:
Many Saas solutions require access to their customers' networks. Bring Your Own Cloud (BYOC) is an emerging architecture adopted by data management and analytics SaaS solutions such as Databricks wherein software is deployed in their customer's environment to process and analyze their data in their customer's environment. This addresses challenges such as data privacy, sovereignty, control, and data transfer costs.
However, securing network access to a customer's environment can be a time-consuming process, often spanning weeks to months. Enterprises often grapple with VPNs, VPC peering, PrivateLink and firewall configurations, which require extensive security reviews and approvals from multiple stakeholders, including the customer's NetOps and SecOps teams. VPC peering and PrivateLink can't be used across a multi-cloud environment. Furthermore, each customer's environment is unique, requiring bespoke network configurations preventing rapid scaling across thousands of customers. End customers are not able to realize time to value quickly resulting in poor experience, dissatisfaction, and churn.
ngrok equips you to deploy BYOC architectures in a frictionless manner that does not require any changes to network configurations. You can embed ngrok with your BYOC data plane and reach customer networks at scale without inbound ports, site-to-site VPNs, or change requests. Accelerate customer deployments by unblocking BYOC implementations and reduce time to value from months to days. You can even deploy a private edition of ngrok - a dedicated instance that operates in your own environment for added security.
Ingress for external networks - devices and machines:
Connecting to IoT devices that are not part of the corporate network using APIs is challenging. Each site has unique ISP, networking, port forwarding rules, and firewall setup. Custom programming and configurations are required, which is not scalable across millions of devices.
With ngrok, you can standardize connectivity into external networks hosting IoT devices without requiring any support from partners or changes to partner's network configurations. You can manage devices at scale by automating configurations for your entire fleet using APIs and accelerate service delivery by eliminating manual processes. Protect your devices by applying uniform policies such as mTLS, IP restrictions, OAuth/SAML/OIDC and more.
Highlights
- Connect localhost or your dev/test to the internet with just one command. Free developers from the complexities of ports and IPs, DNS and firewall configurations. Boost developer productivity by achieving time savings with development, testing and debugging.
- Access external networks you don't control. Bring secure connectivity to your customers' or partners' in a secure, predictable and reliable manner without any friction. Accelerate Bring Your Own Cloud (BYOC) deployments in customer's environments. Manage devices at scale with instant ingress.
- Always-On protection for your apps and APIs. Prevent DDoS attacks, apply consistent policies and monitor traffic flows. Block unauthorized requests before they even reach your network by enforcing authentication and authorization at the ngrok edge.
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Annual Commit | Annual commit for Ngrok product | $25,000.00 |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Description | Cost/unit |
|---|---|---|
consumption_unit | general consumption unit | $0.10 |
Monthly Active Enterprise Endpoint | An active enterprise endpoint is any endpoint with >1 byte data transmission within a give | $0.10 |
TP Advanced Action Executions | Monthly requests where traffic policies with advanced actions are applied. | $0.10 |
TP Basic Actions Executions | Monthly requests where traffic policies with basic actions are applied. | $0.10 |
Basic Account Governance | RBAC, Dashboard SSO. Measured by user per month. | $0.10 |
Advanced Account Governance | RBAC, Dashboard SSO, SCIM, Domain Controls, Audit Events, Advanced IP Restrictions. Measur | $0.10 |
Data Transfer Out | Data transmitted out of ngrok platform | $0.01 |
HTTPs Endpoint Request | Only HTTP requests sent to your upstream service are counted. | $0.10 |
TCP Endpoint Connections | Only TCP connections sent to your upstream service are counted. | $0.10 |
TLS Endpoint Connections | Only TLS Connections sent to your upstream service are counted. | $0.10 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
How can we make this page better?
Compliance
Compliance profile
- Source
- Drata Trust Center





Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
Refer to documentation at https://ngrok.com/docs . Reach out to support@ngrok.com for long term support.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
FedRAMP
GDPR
HIPAA
ISO/IEC 27001
PCI DSS
SOC 2 Type 2
Standard contract
Customer reviews
Simple tunnels have streamlined my local webhook testing and daily development workflow
What is our primary use case?
My main use case for ngrok is bringing my local server up so that I can connect it to any remote site.
A recent example from my work is that I use ngrok to create a tunnel for my local server, which runs on localhost, and connect it to our Paddle webhook connector so that my local server receives any events from Paddle.
I mostly use ngrok for this particular purpose.
How has it helped my organization?
Overall, ngrok has had a positive impact on my work because it is a useful tool that I can quickly trigger to instantly bring my local servers up and expose them so that I can connect them to any remote place.
It is a normal tool in my daily work life that is pretty useful to me, helps me a lot, and makes my work easier. I can't point to a specific organizational impact, but it has been useful in my day-to-day development life.
What is most valuable?
In my earlier days of using ngrok, there was a limit that allowed me to open only one tunnel at a time, but lately I have been able to open multiple tunnels locally, which has been really useful. I'm not sure whether ngrok loosened its limits or whether something else changed, but having the ability to open multiple tunnels is useful.
Having multiple tunnels open at once helps my workflow because I can open one tunnel to listen for the Paddle webhook and another one for other purposes. I can even open a Cloudflare tunnel as well. I didn't remember at first what I used multiple tunnels for, but I used them for things that had to happen at the same time.
I don't know much about the other features of ngrok, but I now remember what I used multiple tunnels for. We have a visibility service that connects to Bright Data, which is an AI model scraping platform. We send our queries there, and we receive the responses through a webhook. To listen to those webhooks, I open another tunnel along with the Paddle one that I already mentioned.
What needs improvement?
It's really simple. It's a command-line tool and doesn't irritate me. It does not give me pop-ups for updates or anything similar. It is really reliable, works well, and doesn't complain.
For how long have I used the solution?
I have been using ngrok almost since the start of my career. I use it to serve and test my local servers and connect them to tools such as Retool and Paddle, among others.
What other advice do I have?
I rate ngrok 9 out of 10 easily.
I chose 9 out of 10 because ngrok is simple, serves its intended purpose, is easy to use and easy to set up, and eases my day-to-day life.
It is a simple tool. I spend one second bringing up a local tunnel, I don't touch it again for the rest of the day, and I close it at the end of the day. I think it's fine. I don't know if there could be any other complications, but it seems fine to me.
ngrok is a great tool. Anyone who is a developer, plays around with code, works locally, and builds things should definitely give ngrok a try, because every now and then I have to connect my local servers and testing servers to a remote site or place in order to test things. It is great for this specific purpose.
Tunneling has enabled real-time mobile testing and has kept team progress fully visible
What is our primary use case?
My main use case for ngrok is to provide a public URL so that I could test the app on my phone and for others to see my progress.
I had a SaaS app on monday.com and I had to implement a mobile feature. I implemented it on the computer, but in order to view it on my phone, I had to use ngrok tunneling to have a public URL so that my phone has access to it.
I used ngrok tunneling so that others could see my progress as another use case.
What is most valuable?
I know that ngrok offers tunneling, which I think is very useful.
Since I mostly use the tunneling feature, I appreciate the dashboard. You can access it from localhost:4040 and you have all the information you need to work with it.
ngrok has positively impacted my organization by helping keep everything transparent. Others could see my progress, so I cannot hide anything. It keeps me accountable as well.
What needs improvement?
I have not used many other features from ngrok, so I cannot really say what could be improved. The ngrok tunneling is perfect.
For how long have I used the solution?
I have been using ngrok for two years since I started using it at the company.
How was the initial setup?
I thought everything was clear from the moment I installed ngrok and used it, including potential improvements in documentation or user interface.
What other advice do I have?
I appreciate your product. I would rate this review a 9 out of 10.
Seamlessly Gets Projects Online
Simple, Reliable Tunnels for Faster Local Development and Debugging
Both the UI and the CLI are straightforward, so even people who aren’t deeply experienced with networking can get things running quickly. The integrations with common development workflows are solid as well, especially when testing services like Stripe, GitHub webhooks, or mobile apps that require external callbacks.
In most cases, performance has been reliable, with stable tunnels and very little setup friction. The real-time request inspection feature is particularly useful for debugging API traffic. From a productivity standpoint, it saves a lot of time because there’s no need to manually configure complicated port forwarding or spin up temporary hosting environments. The onboarding experience is also excellent: the documentation is clear, and most setup steps feel beginner-friendly.
The UI is clean overall, although managing multiple tunnels or advanced configurations can sometimes feel less intuitive than expected.
Performance is generally good, but free tunnels occasionally experience slower speeds or connection instability depending on usage.
Another issue is that some corporate networks or security systems may block ngrok domains, which can create problems during demos or external testing.
While the platform is easy for developers, less technical users may still struggle to fully understand networking concepts during setup.
The AI or intelligent tooling side is still fairly limited compared to newer developer platforms that are adding more automation and debugging assistance
Before using it, testing webhooks, APIs, or mobile app integrations often required deploying temporary environments or configuring routers and firewalls manually.
With ngrok, we can instantly create secure public endpoints for local development, which speeds up testing and collaboration significantly.
It has been especially useful for debugging third-party integrations because external services can communicate directly with local applications in real time.
The request inspection tools also help identify API issues much faster, reducing debugging time during development.
Overall, it improves development speed, simplifies collaboration, and reduces the technical overhead involved in sharing or testing local applications
Remote project reviews have become smoother but recurring session limits still slow collaboration
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I am grateful I have not needed to contact customer support since ngrok's documentation has covered all the issues I encountered.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
