I’ve been trying out Supabase for a few months, mainly as a solo developer building small personal apps. I subscribed to the Pro Plan for $25/month and canceled on July 29, thinking that was it.
To my surprise, I was still charged $22.85 later that night.
Support told me: “You were charged for compute hours from the previous billing cycle. We charge in hindsight.”
Here’s why this makes no sense to me:
- I had already paid for the Pro Plan. What did the $25 cover, then?
- My projects were idle. I barely used the service that month.
- There were no alerts or warnings about compute hours accumulating silently.
- Supabase only covers one project’s compute cost in the plan — the rest are charged separately even if unused.
- The support response was cold and dismissive, like it was my fault for not reading enough docs.
💸 What happened in the invoice?
- $25 Pro Plan → Refunded after cancellation ✔️
- Compute charges for 4 idle projects → $32.85
- Usage adjustment: -$10.00
- Final charge: $22.85 for projects I didn't touch.
💬 Here's the latest reply I received from support:
On our paid plans, there are no idle projects – each project is running 24/7 on dedicated servers independent of usage.
The compute usage fees are unfortunately non-refundable.
This was shocking. I didn’t know that “doing nothing” would still cost me money, and nowhere was it clearly emphasized during setup or in-app warnings.
🧭 Lesson learned
If you’re not actively monitoring usage and manually pausing unused projects, Supabase will keep charging you behind the scenes, even after cancellation.
This was one of the most frustrating and disappointing billing experiences I’ve had with a dev tool.
I won’t be using or recommending Supabase again.
Have you encountered unexpected charges from dev tools before? I’d love to hear your stories — maybe I’m not alone in this.
Top comments (0)