amara_v git.example.com/amara-okoye/volunteer-scheduler ↗
We have 60 volunteers now, 500 next year across five chapters. Bolt built it on Supabase free tier. Where will this start costing money, and what should I change now while it's small?
At 500 users you're still within Supabase Pro (€25). The thing that will bite you is the shifts page: it loads every shift ever, then filters in the browser. That's bandwidth, not database. Add a where date >= today server-side and paginate. Do it now while the table is small enough to test quickly.
Jonas is right that the database isn't where the money goes. Two other things to watch at 500 users across five chapters.
Email. If Bolt left auth on Supabase's built-in SMTP for sign-up and magic links, that's rate-limited to a handful per hour and meant for testing. The first chapter onboarding evening will hit it. Put a real email provider behind auth before chapter two; the free tiers cover your volume.
Storage egress, if volunteers upload photos or documents. Serve resized images, not the originals.
When you move to Pro, leave the spend cap on. At your size the realistic risk isn't a huge bill, it's a surprise one.
amara_v 