Flexible and expressive traffic orchestration: introducing internal endpoints

Ngrok has introduced two new primitives, internal endpoints, and the forward-internal action, to enhance its traffic routing capabilities, enabling users to create flexible routing topologies based on various request attributes like headers, paths, and subdomains. Internal endpoints are secure, non-public endpoints that facilitate routing traffic through the forward-internal action, allowing users to manage traffic flows without exposing services to the public internet. This advancement addresses the challenges of traffic orchestration by allowing path-based, domain-based, header-based, and geolocation-based routing, which can be configured through ngrok's Traffic Policy module. These features are particularly beneficial for use cases such as self-service app delivery, centralized security management for developer environments, on-demand public addressability, and live traffic debugging. The new primitives are aimed at providing more security and flexibility in traffic management, and they are available through ngrok's pay-as-you-go plan, with detailed guidance provided in their developer documentation.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.