Urgent.News

What's breaking now, across thousands of outlets.

Tech

How I Run 114 Posts, 98 Tools and 32 Games on Firebase Blaze for $0 a Month

Firebase's Blaze plan has a reputation problem. People hear "pay as you go", picture the horror stories — the recursive Cloud Function that wrote back into the collection that triggered it, the forgotten listener on a 400,000-document collection — and stay on Spark until Spark isn't enough. Then they upgrade and quietly brace for the email. My portfolio site has been on Blaze for months. It…

Firebase's Blaze plan often carries a negative reputation due to concerns about unexpected costs. Many users stay on the Spark plan, only upgrading once the limitations become apparent. This reporter's portfolio site runs on Blaze, serving 114 blog posts, 98 interactive tools, and 32 games, powered by Firestore and Cloud Storage. Despite its size and complexity, the site's monthly bill has consistently been $0.00. This article explains the six key decisions that enabled this cost-effective setup.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Hitting an image size ceiling with Rust and WebAssembly

Many image tools expose a quality slider. Forms and government portals usually expose a different requirement: “the file must be under 100 KB.” Those are not the same problem.

  • Implement HEIC converter in browser using Rust compiled to WebAssembly
  • Outputbytes = targetkb 1024 invariant for image size control
  • Separate conversion path from compression for clean implementation

Moving image work into the browser took that bill to zero

For about two months last year I had a habit: check the API usage graph before anything else in the morning. Not because traffic was flattering — because every time that line went up I had to work out…

  • Moved image processing to users' browsers to eliminate API costs
  • Services like background removal, AI upscaling, and PDF processing ran locally
  • Site became free, unmetered, but limited by free service constraints

I sell social media automation. My survey says people want the opposite.

I work at Publora — an API and MCP for publishing to social networks from one place, including through an AI agent. So, in a sense, my job is selling automation for posting.

  • Survey reveals people want control over final posting step in social media automation
  • AI use limited to ideation or time constraints, not for publishing
  • Human involvement valued for security, personal touch, and content approval

More from Thursday 3 September →