API gateway

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.

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

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.

Transform how you handle production traffic with ngrok, enhancing security and management for your applications beyond just testing.

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.

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.

Ingress controllers and API gateways have some overlapping functionality, and this post helps you know when to use one over the other—or both!

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

Secure your APIs with JWT authentication using ngrok’s developer-defined API Gateway for enhanced security and seamless integration.

Discover the simplicity of ngrok's API gateway and compare it to Kong for enabling developer productivity, ease of use, and rapid deployment capabilities.

Reverse proxies and API gateways share many similarities. This post helps you understand how these technologies differ and when to use each one.

Learn how ngrok redefines digital transformation, offering strategic advantages in security, efficiency, and innovation for modern enterprises.

ngrok's developer-defined API gateway introduces support for JWT validation. Learn about ngrok's implementation and how to add JWT validation to your API endpoints.

ngrok's API gateway includes traffic routing, JWT authentication and authorization for API security, rate limiting for ensuring fairness, preventing resource exhaustion of origin services, and flexible request/response manipulation - all powered by our new traffic policy engine.