Sources
- Airbnb Engineering
- Amazon AWS AI Blog
- AWS Architecture Blog
- AWS Open Source Blog
- BrettTerpstra.com
- ByteByteGo
- CloudFlare
- Dropbox Tech Blog
- Facebook Code
- GitHub Engineering
- Google AI Blog
- Google DeepMind
- Google Open Source Blog
- HashiCorp Blog
- InfoQ
- Spotify Engineering
- Microsoft Research
- Mozilla Hacks
- Netflix Tech Blog
- NVIDIA Blog
- O'Reilly Radar
- OpenAI Blog
- SoundCloud Backstage Blog
- Stripe Blog
- The Batch | DeepLearning.AI | AI News & Insights
- The Dropbox Blog
- The GitHub Blog
- The Netflix Tech Blog
- The Official Microsoft Blog
- Vercel Blog
- Yelp Engineering and Product Blog
Engineering @ Scale — 2026-06-05#
Signal of the Day#
The single most instructive insight this period comes from Cloudflare’s AI Gateway deployment: you cannot control enterprise AI costs without tying every inference request to a verifiable identity. Passing shared API keys around creates untrackable financial black holes; engineering organizations must use OIDC or JSON Web Tokens (JWTs) to attach specific user or service identities to the network layer, enabling dynamic routing and hard budgets based on the requestor’s profile.