The ngrok blog

Tired of spoofed headers? Use JA4 to fingerprint clients by their TLS handshake and take action with ngrok Traffic Policy.

Are search and AI bots invading your ngrok endpoints? Fight back with three developer-friendly traffic policies you can deploy in minutes.

Define lists, maps, and interpolated values inside your traffic management rules—then reference them anywhere—to make configs both simpler and more dynamic.

Simplify your Kubernetes ingress stack: global load balancing, DDoS protection, and flexible routing all built into ngrok’s Operator.

Deploy a Kubernetes cluster, install the ngrok Operator, and validate your Helm charts or deployments—all inside GitHub Actions. Fast, clean, and repeatable.

Run your service on localhost, interact with it from any of your clusters—or all of them at once. ngrok makes the K8s dev loop feel magical again.

Need custom certs? Want fast mTLS setup? ngrok’s terminate-tls action gives you complete TLS control from one declarative config.

This is how I help modern teams do site-to-site connectivity: no VPNs, no sprawl—just secure tunnels and full control.

Want remote access to your Kubernetes API without VPNs or other complicated networking? ngrok’s K8s Operator makes it secure, declarative, and RBAC-friendly.

You can't always control when your services crash, but with Traffic Policy and custom responses, you can build consistent and helpful error pages in a minutes.

Ditch complex SSH/RDP chains and VPNs—here's how I help folks use ngrok to create secure and dynamic access to remote services or sites with a single agent.

From Platform Engineering Day, to our booth at N611, to talks on Gateway API implementations and API gateway maturity, there are plenty of places to find us.

One ngrok agent per factory = secure IoT access, no open firewalls, no VPN pain. Learn how cloud endpoints simplify industrial connectivity.

Multicloud isn’t magic—it’s a mess of networking, configuration, security, and observability pain. API gateways can help—here’s how to fix it the easy way.

A composable API gateway means total flexibility. Learn how ngrok's endpoints and Traffic Policy make exposing, routing to, securing, and scaling APIs a cinch.

Have you ever wanted an ngrok endpoint that doesn’t go offline when you get disconnected from the internet? Now possible with always-on cloud endpoints.

Building LLM-fueled apps? See how one AI startup uses ngrok to develop locally against remote services and safely test LLM prompt changes without breaking prod.

Your simplest path to AI collaboration or development using ngrok and Deepseek with an assist from Ollama and a GPU-accelerated virtual machine.

Learn how ngrok's IP Intelligence gives you powerful tools to identify and block bots, scrapers, and malicious traffic at your API gateway.

Implement circuit breaking at your API gateway to prevent cascading failures and protect services, and without having to add more complexity to your APIs.

Secure your endpoints with ngrok’s Basic Auth Traffic Policy, compatible with both interactive and programmatic access to your APIs or apps, in a few minutes.

Simplify and scale complex traffic routing topologies by dynamically routing requests based on subdomains, headers, and other request attributes.

Deployment complexity, environment constraints, and poor debugging tools create more barriers to API gateway maturity than they do benefits.

By replacing highly typed configs with raw YAML/JSON, we’ve eliminated a major UX papercut and given you feature updates “for free.” Let’s see what’s changed.

ngrok lets you manipulate traffic at multiple moments in the request lifecycle, allowing API developers to compose, not compromise, powerful API gateway rules.

Build a region-aware API gateway with ngrok's Traffic Policy. Route requests, manage failover, and enforce regional compliance with simple YAML configs.

Ensure secure, verified webhook interactions with ngrok’s Traffic Policy Action, enhancing protection and reliability for your endpoints.

Use geoblocking in your API gateway to control traffic by location, enhancing security, compliance, and performance

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.

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!

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.

Internal endpoints are secure, non-public endpoints that end with .internal, allowing you to route traffic based on headers, paths, subdomains, and more.

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.

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.

Master the dynamics of API rate limiting with ngrok’s gateway: a key to enhanced security, efficiency, and user satisfaction.