ngrok

Catch up on last week's ngrok.ai early access announcement with this quick walkthrough on getting started with our new unified gateway for LLM providers. In about 4 minutes, our devrel Joel Hans covers the setup (it's a one-line change—your existing SDK code stays the same) and shows how to configure automatic failover across providers like OpenAI, Anthropic, or local models. → https://ngrok.ai → https://lnkd.in/g99SNSQb

Yesterday we launched https://ngrok.ai into early access. Today we're bringing you a deep dive into LLM internals with beautiful visuals crafted by our very own Sam Rose. Discover exactly what gets cached to offer you 10x cheaper input tokens. https://lnkd.in/gddNe7ke

One gateway for every AI model. Now in early access today. We built this because we kept hearing the same stories of juggling multiple providers, writing custom retry logic, and scrambling when rate limits hit at the worst possible time. To use ngrok.ai, you change your baseURL to point at your public AI gateway endpoints and configure policies in rules-based YAML. We handle routing, failover, key rotation on our cloud. And throw in observability for good measure. This is true early access, so while we have tons of ideas on our roadmap, the path is truly open. We want to know what's missing and what would genuinely help—that's the road we'll take together. 📖 Read more: https://lnkd.in/gtKygx6A 🔗 Get started: https://ngrok.ai

"We've been running these WAF actions for more than six months on ngrok.com. In that time, they have run the CRS rules on every one of the 300M+ requests and responses. Of those, we've blocked ~1.2% (~3.6M) requests from reaching the upstream services of ngrok.com." At ngrok, we embedded the OWASP Core Rule Set and Coraza into ngrok's own Traffic Policy engine, and then dogfooded it across 300M+ requests to http://ngrok.com. 🛡️ In this post, Ben Chan walks you through how we built (and battle-tested) ngrok’s WAF! ⚔️ 🔗 https://lnkd.in/gK_fduvV

Let's kickstart this week with the many shapes of API gateways and how ngrok fits right into each one! ☝️ Starting off with Shape #1: The Database Gateway Gateways aren’t just for APIs. This one lives between your users and the database you need to (securely) put online, offering mTLS, rate limiting, query filtering, and secrets support, all at the edge. 🔍 "just IP restrict it" isn't a strategy anymore! 🔗 https://lnkd.in/ghJPidYW 1/5

If your secrets live on a platform like HashiCorp Vault, AWS Secrets Manager, or Google Secret Manager, you may want to sync them into ngrok Vaults via the External Secrets Operator so your Traffic Policies reference a single, rotated source of truth. 🔑 Read more about our dogfooding with the External Secrets Operator (ESO), a Kubernetes controller for synchronizing secrets with external stores and dabble effortlessly with ngrok Vaults and Secrets for Traffic Policy! 🚦 🔗 Check: https://lnkd.in/gq97U2vN

Last week’s AWS outage took down half the internet. ngrok stayed up, and a bunch of people asked "HOW?" 🤔 Our Senior Customer Engineer, Peter Y., covers just that in the latest on our blog. In a nutshell; “The simplest way to not be caught off-guard when us-east-1 falls over is to not use us-east-1 at all.” 🔗 Read more: https://lnkd.in/gZswn5qC

“The AI gold rush has led to a very modern problem: too many shovels, too little gold.” 🪏🪏🪏 AI gateways are how teams keep their models, costs, and chaos under control. 💸 Here’s a guide on how they work and whether you actually need one... 🔗 https://lnkd.in/gkvwMfDs

Start from scratch or skip straight to simple. 💯 In this blog post, Sam Rose helps you build up the moving parts of self-hosting your app first, then shows how ngrok makes it all effortless. 🔗 Read here: https://lnkd.in/gN_trmFE

Spin up n8n, Ollama, and ngrok in Docker Desktop and self‑host your AI workflows, sharing them securely, and skipping all the networking headaches. Very shrimple. 🦐 Here’s your guide to building local AI automations that actually scale! 🔗 https://lnkd.in/gP2_E8kF