← Back to journal
Behind the BuildMay 19, 2026·1 min read
Cutting Firebase Costs Without Sacrificing Speed
How Bizzi Cloud reduced Firestore read volume across listing, trash, proxy status, and dashboard paths — platform efficiency at scale.
Every Firestore read has a cost — and at scale, inefficient queries compound fast. We ran a systematic optimization pass across gallery, dashboard, trash, and proxy status paths to cut read volume without slowing down the UI.
Optimize what users touch most
Home bootstrap, gallery refetch loops, dashboard API traffic, and background polling were all targets. The goal: fewer redundant reads, smarter caching, and debounced refresh after mutations.
What shipped
- ✓Reduced Firestore read volume across listing, trash, and proxy paths
- ✓Fixed public gallery refetch loops
- ✓Reduced duplicate dashboard API traffic
- ✓Gallery drag selection with reduced background polling
- ✓Upload-visibility-repair Firestore pagination hardening
- ✓Stale subfolder item counts fixed with server metadata recompute
Efficiency enables ambition
Reducing Firestore read volume without slowing the product means more runway for features and healthier unit economics as subscriber count scales.