Examples
Whether you need an API gateway, multicloud failover, or want to integrate ngrok with your stack, these examples help you compose endpoints and Traffic Policy to orchestrate traffic for common jobs to be done and problems to be solve. Wire it up, secure it, and ship it already.
Fundamentals
Implement the 'Front Door' Pattern
By using a Cloud Endpoint and internal Agent Endpoints together, you loosely couple your gateway and services for extra flexibility.
Deploy Custom Error Pages
Instead of a blank page or HTTP error code, ensure your services automatically failover to error pages with clear details and instructions.
Use ngrok with...
Accelerate and Secure Your Wordpress Installation
Improve your existing Wordpress installation with automatic TLS certificates, CDN acceleration/DDoS protection, and options to protect your admin dashboard.
Offload Analytics to a Secondary Service
Capture observability data from your gateway and send it to a self-hosted analytics service securely and without instrumenting your code.
Expose and Secure Your Self-Hosted Ollama API
Use ngrok to create a public endpoint for your local LLM, enabling remote access and integration, while also adding authentication and access control.
Expose and Secure Your Self-Hosted n8n Workflows
Get your n8n instance online to share with colleagues or receive webhook data with security measures desinged for production usage.
Traffic Control
Route to Endpoints by Geography
Show users content based on their region, comply with regulations, or ensure traffic hits the nearest endpoint for the lowest latency.
Deploy a Zero-Code Maintenance Mode for Your Services
Deploy a consistent maintenance message for your services without having to spin up new services or make changes to your network.
Authentication & Authorization
Lock Down Your Admin Dashboards
Add multiple layers of protection and authentication to your dashboards to prevent threat actors from even attempting attacks.
Authenticate and Route API vs. App Traffic Based on User Agent
Automatically enforce the right type of AuthN and route requests to the appropriate upstream service from the same hostname and path.
Route to Services Based on OIDC Authentication
Use the data returned by your OIDC provider to route authenticated requsets to specific upstream services.