The latest articles on DEV Community by Kevin Bkt (@kevinbkt). https://dev.to/kevinbkt https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4191230%2F37bb5d1f-6edf-4728-a695-d93330ae01ec.jpg https://dev.to/kevinbkt en Kevin Bkt Sun, 18 Oct 2026 20:41:27 +0000 https://dev.to/kevinbkt/workers-ai-and-ai-gateway-using-ai-on-cloudflare-without-scattering-api-keys-23in https://dev.to/kevinbkt/workers-ai-and-ai-gateway-using-ai-on-cloudflare-without-scattering-api-keys-23in <p>If you run several small projects, API keys tend to pile up: one per provider, copied into env files, CI secrets and old branches. Every copy is one more place a key can leak.</p> <p>One way out is to keep inference inside Cloudflare. Workers AI runs models from a Worker binding, so there's no external key in the code at all, and AI Gateway sits in front of external providers so the provider key lives in one place, with caching, rate limits and logs on top.</p> <p>I wrote up how I set this up across my projects, with the trade-offs I hit along the way (in Portuguese):<br> <a href="https://kevinbk.com/blog/evitar-acumulo-de-chaves-api-em-projetos-ia" rel="noopener noreferrer">https://kevinbk.com/blog/evitar-acumulo-de-chaves-api-em-projetos-ia</a></p> cloudflare ai security webdev