The ngrok blog
Subscribe to our newsletter or follow our RSS feed for the latest news about unified ingress for development and production.
How can I geoblock with an API gateway?
Use geoblocking in your API gateway to control traffic by location, enhancing security, compliance, and performance
Manage traffic at critical connection points with Traffic Policy phases
Learn how ngrok's phase-based Traffic Policy gives you granular traffic control in more places, from TCP connect through HTTP response, to take decisive action.
Goodbye tunnels, hello agent endpoints
We've collapsed many flags into one for simplicity and unified naming conventions to flatten the learning curve. Join us in saying bye by updating your configs!
Debug traffic flows with cloud endpoints and custom responses
By using the custom-response Traffic Policy action and a public endpoint, you can quickly develop new policy rules without standing up a whole infrastructure.
Flexible and expressive traffic orchestration: introducing internal endpoints
Internal endpoints are secure, non-public endpoints that end with .internal, allowing you to route traffic based on headers, paths, subdomains, and more.
How we built the Traffic Policy module and its actions
Traffic Policy is now the one true (and final!) way to shape your requests and responses. Let’s explore why we built it, how, and what it means for you.
Drop-in API gateway policy examples for manipulating headers
With these ready-for-prod Traffic Policy rules, you can boost your security, give customers SLA metrics, and create geo-aware APIs in a few lines of YAML.
How nuanced rate limiting transforms your API and business
Master the dynamics of API rate limiting with ngrok’s gateway: a key to enhanced security, efficiency, and user satisfaction.
CliffsNotes your voicemails with WebSockets, Twilio, and OpenAI
Explore ngrok's WebSocket capabilities with a demo crafted for Office Hours, integrating with OpenAI’s API to create a secure phone call summarization app.
How we built ngrok's data platform
At ngrok, we manage a ~100TiB, 500+ table data lake, managed by a very small team. Here's a look at how we built it and what unique challenges we solved.
ngrok in production: Not just for testing anymore
Transform how you handle production traffic with ngrok, enhancing security and management for your applications beyond just testing.
AWS PrivateLink vs. VPC peering vs. ngrok
Explore the pros/cons of AWS PrivateLink vs VPC peering for connecting AWS clouds securely—and whether ngrok could be a simpler and more flexible alternative.
Deploy advanced HTTP traffic shaping with request variables and CEL
Explore ngrok's request variables and Common Expression Language to create flexible, powerful HTTP traffic shaping rules for your API endpoints.
Introducing Office Hours: Learn about and build on ngrok together
Join ngrok's Office Hours: A monthly livestream for developers to learn, ask questions, and explore ngrok's capabilities beyond secure tunneling.
Deploy a globally-distributed API gateway with DigitalOcean and ngrok
Deliver low-latency, resilient APIs without vendor lock-in or complex networking with ngrok’s global server load balancer, automatically deployed with your API.
Visibility and limits: Keep track of your ngrok usage
Track your ngrok usage effectively with our dashboard, offering visibility into metrics like traffic, endpoints, and data transfers.
Introducing Load Balancer support for ngrok Kubernetes Operator
Enhance Kubernetes operations with ngrok’s Load Balancer support, streamlining access and connectivity for services in your clusters.
Send ngrok Network Traffic Logs to Azure Monitor
Seamlessly integrate ngrok with Azure Monitor to forward network traffic logs for enhanced visibility and secure traffic management.
Set up a reverse proxy with AWS and ngrok
Discover what a reverse proxy is and why they're essential for public-facing services, apps, and APIs, and learn how to set up a reverse proxy on AWS with ngrok
Easier DNS configuration with subdomains and zones—and a switch
Using branded domains with ngrok? It’s never been easier or more error-proof to establish proper DNS zones for delegation and namespacing.
