Gateways

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.

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.

Explore ngrok's request variables and Common Expression Language to create flexible, powerful HTTP traffic shaping rules for your API endpoints.

Deliver low-latency, resilient APIs without vendor lock-in or complex networking with ngrok’s global server load balancer, automatically deployed with your API.

Explore how ngrok's Traffic Policy feature helps developers filter traffic, without requiring help from ops, with raw connection variable data and CEL.

Mutual TLS (mTLS) with an API gateway can help you meet compliance requirements in industries that demand high security for data transmission.

Find out the difference between URL rewriting and redirection and how to utilize them to seamlessly migrate your API endpoints

Discover how GitOps and APIOps can revolutionize your API gateway workflow, offering version control, easy deployment, and developer sanity with ngrok.

With these 10 YAML-configured examples, you can mix-and-match your way to better security, availability, and observability of your freshest APIs.