ngrok
ngrokExternal reviews
External reviews are not included in the AWS star rating for the product.
Authentication and access control have improved project deployment and human verification
What is our primary use case?
What is most valuable?
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.
What needs improvement?
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
How was the initial setup?
What about the implementation team?
What was our ROI?
Which other solutions did I evaluate?
What other advice do I have?
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Generating secure test links has streamlined client feedback and has improved project debugging
What is our primary use case?
What is most valuable?
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.
What needs improvement?
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
The product is scalable and stands out for me as a 10.
How are customer service and support?
Which solution did I use previously and why did I switch?
Which other solutions did I evaluate?
What other advice do I have?
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.
Easy to Implement, and the Free Plan Covers Everything I Need
Streamlined development has accelerated webhook testing and real-time client collaboration
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using ngrok for the last two years.
What do I think about the stability of the solution?
ngrok is very stable, as we have not faced issues while running multiple servers and APIs, and it is fast and scalable.
What do I think about the scalability of the solution?
ngrok is highly scalable, allowing multiple servers or URLs created within the same account, facilitating smooth collaboration among multiple teams and developers.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
We have not been utilizing any older solution, as we actually started with ngrok only.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Testing web apps externally has become faster and saves time and resources
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using ngrok for a year.
What do I think about the stability of the solution?
ngrok is stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
I did not previously use a different solution for my needs.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
I have not done any costs for ngrok; it is just locally.
Which other solutions did I evaluate?
ngrok was my first pick, as it was the only thing I could find that could do what I wanted it to do.
What other advice do I have?
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.
Best solution for POC
Great Tool For Local Hosting
Networking