# Supabase bill spike: find what you’re paying for, then cut it
> Your Supabase invoice jumped. Find the line and project behind it: compute per project, egress, realtime or users, and why the Spend Cap missed it.
Canonical: https://app369.com/fix/supabase-bill-spike/
Last updated: 2026-11-13
The Supabase invoice is far higher than last month, or the upcoming invoice estimate keeps climbing. A paid plan is a fixed fee plus usage, and some usage keeps billing even with the Spend Cap on. Find which line grew and which project it came from, then the setting or code behind it. Here’s how, in Supabase’s words, or hand it over at a fixed price.
**Rather hand it over?** [App Fix Ticket](https://app369.com/fixed-price/flutter-firebase-bug-fix/): One reproducible bug in an existing mobile or web app, diagnosed and fixed.
[Pay $450 for a Diagnosis](https://buy.stripe.com/dRmdRa7K4bWz8CWdwagw003) [**Ask a question first**](https://app369.com/contact/?offer=offer1-diagnosis&ask=1)
Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. [Refund terms](https://app369.com/terms-of-service/#refunds).
- Simon does the work himself
- [5.0 from 127 Fiverr reviews, checked Oct 30, 2026](https://app369.com/reviews/)
**Short answer**
Open the organization’s Usage page and the Upcoming Invoice on the billing page, then pick each project from the dropdown to see which one grew. Compute is billed per project by the hour and is not covered by the Spend Cap, so an extra project, a bigger compute size, branches or read replicas add to the bill on their own. For usage lines such as egress or realtime messages, find the query or listener sending too much data and fix that first. Then delete projects you don’t use.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **Where the money goes, and the fix**
1. 01 ### **Find the line and the project**
> “The page shows the usage of all projects by default. To view the usage for a specific project, select it from the dropdown.” [**Supabase, Manage Compute usage**](https://supabase.com/docs/guides/platform/manage-your-usage/compute) Usage is summed across every project in the organization into one invoice, so start with the Usage page, then pick each project from the dropdown. The Upcoming Invoice section estimates the full cycle from usage so far.
2. 02 ### **Every project adds compute**
> “Each project you launch increases your monthly Compute costs.” [**Supabase, About billing on Supabase**](https://supabase.com/docs/guides/platform/billing-on-supabase) Each project runs on its own server, billed by the hour while the project is running, whether or not anyone uses it. The Compute Credits included in paid plans cover one project on the Micro or Nano size, so a second project, a staging copy or a bigger compute size is new spend. Read Replica and Branching compute are not covered by the credits either.
3. 03 ### **The Spend Cap doesn’t cover compute**
> “Compute Hours are not covered by the Spend Cap.” [**Supabase, Manage Compute usage**](https://supabase.com/docs/guides/platform/manage-your-usage/compute) With the Spend Cap on, covered usage items stop at the plan quota until the next billing cycle. Compute is not one of them, and neither are items you opted into yourself, so the cap can be on while the bill still grows.
4. 04 ### **The Spend Cap is off**
> “Any additional usage will be charged based on the item's cost per unit, as outlined on the pricing page.” [**Supabase, Cost control**](https://supabase.com/docs/guides/platform/cost-control) With the cap off, the app keeps running past the quota and each extra unit is billed. That keeps the app up, so watch the usage page.
5. 05 ### **Queries send too much data out**
> “Reduce the number of fields or entries selected when querying your database” [**Supabase, Manage Egress usage**](https://supabase.com/docs/guides/platform/manage-your-usage/egress) Egress is the data your project sends to the app, charged per gigabyte over the quota. A screen that loads whole tables or every column, or repeats the same call, grows it. Select only the fields and rows the screen shows, and cache what doesn’t change.
6. 06 ### **Realtime listeners multiply messages**
> “Each database change counts as one message per client that listens to the event.” [**Supabase, Manage Realtime Messages usage**](https://supabase.com/docs/guides/platform/manage-your-usage/realtime-messages) Realtime bills each message, and one database change is a message for every client listening to it.
Checked against the vendor’s docs on November 13, 2026: [Supabase docs: About billing on Supabase](https://supabase.com/docs/guides/platform/billing-on-supabase); [Supabase docs: Cost control](https://supabase.com/docs/guides/platform/cost-control); [Supabase docs: Manage Compute usage](https://supabase.com/docs/guides/platform/manage-your-usage/compute); [Supabase docs: Manage Egress usage](https://supabase.com/docs/guides/platform/manage-your-usage/egress); [Supabase docs: Manage Realtime Messages usage](https://supabase.com/docs/guides/platform/manage-your-usage/realtime-messages); [Supabase docs: Manage Monthly Active Users usage](https://supabase.com/docs/guides/platform/manage-your-usage/monthly-active-users).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
- [from $450**AI-Built App Rescue**A Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.****No issues worth fixing, no charge.**** If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.**See scope and start**](https://app369.com/fixed-price/ai-app-rescue/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**Supabase app slow**](https://app369.com/fix/supabase-app-slow/) · [**Supabase project paused**](https://app369.com/fix/supabase-project-paused/) · [**Firebase bill spike**](https://app369.com/fix/firebase-bill-spike/) · [**Supabase realtime not receiving changes**](https://app369.com/fix/supabase-realtime-not-receiving-changes/)
Questions
## **More on this error**
**Does the Spend Cap stop every charge? **+
No. Supabase says only certain usage items are covered. Compute hours are not, and usage you opted into yourself is excluded, so the plan fee and compute keep billing with the cap on.
**Why did a second project raise the bill? **+
Each project has its own server billed by the hour. The Compute Credits included in paid plans cover one project on the Micro or Nano size, so another project adds its own compute hours.
**How are users counted? **+
Monthly active users are the distinct users who sign in or refresh their token in the billing cycle. Each user counts once per cycle.
**Can you fix it for me? **+
If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.
A different error?
## **Describe it and get a written quote**
Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)