Cache for the Future
Dramatically reduce your Supabase Storage egress with smart caching through Cloudflare R2. One-line change, massive impact.
Join the waitlist — be first to know when we launch.
Get the Most Out
of Your Storage
Egress Fees Add Up Fast
Every file your users download from Supabase Storage incurs egress charges. At scale, bandwidth becomes the biggest line item on your bill.
Smart Caching via R2
Zerogress caches files on Cloudflare R2 at the edge. Repeat requests skip the origin entirely - dramatically reducing egress.
Advantages
We built Zerogress to solve the egress problem every Supabase developer faces at scale.
One-Line Setup
Swap a single URL. No SDK, no migration, no config files to maintain.
S3 Compatible
Same protocol your app already uses. Existing code works without modification.
No Vendor Lock-In
Remove Zerogress anytime. You're back to standard Supabase Storage instantly.
Global Edge Delivery
Cached files served from Cloudflare's 300+ data centers worldwide. Faster for your users.
One URL Change.
That's It.
Replace your Supabase Storage URL with Zerogress and your files start caching automatically on Cloudflare R2. No SDK, no migration, no config. Every cached request skips the origin — and your egress bill drops dramatically.
Swap the URL
Replace your Supabase Storage URL with your Zerogress endpoint.
Files Cache Automatically
First request fetches from Supabase and caches on Cloudflare R2.
Egress Drops Dramatically
Cached files skip the origin. Your bandwidth bill shrinks with every hit.
Sunith VS
Builder & Developer
Built from a
Real Problem
My media-heavy project was hitting 300% egress on Supabase's free tier. I love Supabase — the RLS, the upload API, the auth — but couldn't scale without solving egress. So I built the fix.
Frequently
Asked Questions
Supabase's Smart CDN still incurs egress charges beyond your included quota. Zerogress routes through Cloudflare R2 which has significantly lower bandwidth overhead. The benefits compound as your traffic grows.
No. Keep your buckets, RLS policies, and auth — everything stays the same. You only change the URL your frontend uses to fetch files.
Uploads go directly to Supabase. Zerogress only caches reads/downloads. Your upload flow, authentication, and storage policies are completely untouched.
Yes. Signed URL authentication is passed through to Supabase on cache miss. Files protected by RLS remain protected.
You fall back to serving directly from Supabase Storage. Since Zerogress is a proxy layer, removing it means requests resolve to your original Supabase URLs. No data loss, no lock-in.
We're building fast. Join the waitlist to get early access as soon as we launch. Early members will get priority onboarding and direct support from the team.
Start Saving on
Egress Today
Join the waitlist and be the first to cache Supabase Storage through Cloudflare R2.
No spam. Unsubscribe anytime.