Like a lot of you, I've been reading posts about surprise bills here and there, also from other cloud providers, and to be honest it kinda scared me to link my payment method.

I've been building something for a while, and now that I'm at a point where I want to open it to the public, I don't want to take the risk of growing a huge bill overnight because of a mistake or a malicious actor. No one is immune to that.

I really like the Cloudflare ecosystem, but I'm really frustrated that they don't give us a solution to control spending. They already have limits for free plans, spend caps per resource on paid plans doesn't seem like a huge leap.

So I searched and didn't find any solution that fit my needs:

• Per-resource thresholds: set a limit on KV writes independently from D1 rows or R2 mutations
• Global & per resource budget cap in dollars: being able to say "I don't want to spend more than $10 a month in overage" or "I don't want to spend more than 5$ a day on neurons".
• Actual active protection: CF gives us spending alerts, but what if I'm sleeping or I just don't see the notification? Even if I see it I should rush to my computer to manually cut everything ? I want to stop spending automatically (of course best-effort from what CF gives us from their API)

So I built my own. It's a TypeScript library you plug into your Workers, it polls the Cloudflare Analytics API on a cron schedule, tracks your actual usage across resources (Workers, KV, D1, R2, Queues, Durable Objects, Workers AI, Vectorize), and automatically trips a circuit breaker when you cross the thresholds you define. You can wrap your env bindings in one line and calls get blocked when the guard is tripped. It's also fully customizable and allows you to define your limits, what you want to do when those limits are reached etc..

It's MIT licensed, zero dependencies, and works with any Workers project, only require a KV binding: https://github.com/tristanwagner/cf-usage-guard (feature requests/contributions are welcome)

It won't protect you from a bug that burns $5,000 in 10 seconds (the analytics data lags a few minutes), but it will catch the much more common scenario of a worker silently grinding through resources for hours or days before anyone notices. It's still new and not perfect, but it's here if anyone wants to try it, until Cloudflare properly gives us a solution (hopefully).

Special mentions to 2 sources that greatly inspired and helped this project:

• https://yingjiezhao.com/en/articles/Usage-Circuit-Breaker-for-Cloudflare-Workers/
• https://pizzaconsole.com/blog/posts/programming/cf-overage

Happy to answer questions or take feedback. If you've built something similar or have a different approach to cost protection on CF, I'd also love to hear about it.

🚀 ¡VasakOS Alpha 3 ya está aquí! (Y sí, seguimos más vivos que nunca)

Primero que nada: perdón por el silencio de radio. 📻💨

Sabemos que estuvimos un poco desaparecidos en las redes, pero no fue por falta de ganas, sino porque estábamos en modo "deep work". El desarrollo se mantiene súper activo y hoy por fin podemos mostrarles en qué estuvimos quemando pestañas.

¿Qué hay de nuevo en esta Alpha 3?

🛠 Hemos pulido detalles que hacen la diferencia entre una "distro más" y una herramienta de productividad real:

• Instalador optimizado
• Estética impecable: Los esquemas de colores y los design tokens ahora fluyen mejor que nunca.
• Bajo el capó: Mejoras de estabilidad y rendimiento que preparan el terreno para lo que viene.

No solo estamos construyendo un sistema operativo; estamos armando el entorno que nosotros mismos queremos usar todos los días. 🐧✨

Leé todos los detalles del lanzamiento en nuestro blog: 👉 https://os.vasak.net.ar/blog/2026/04/alpha-3-de-vasakos/

Gracias por la paciencia y por seguir ahí. ¡El feedback de ustedes es nuestro combustible! ⚡️

VasakOS #Linux #OpenSource #Alpha3 #TechUpdate #Rust #Tauri