My Bubble workload units keep going up. How do I cut the bill, and should I leave Bubble?

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: Bubble, a no-code tool for building web apps by dragging and dropping, charges for the work its servers do, counted in workload units. Open the App Metrics chart in your app, find the one or two activity types that dominate, and fix those first: usually a page that runs heavy searches every time it loads, a workflow that repeats itself, or a scheduled job that runs more often than it needs to. Leave Bubble only if the bill stays high after that clean-up and the monthly saving beats the one-off cost of a rebuild.

Ranjit Bhinge

Your Bubble bill is rising faster than your user count, and you want to know what is eating the units before you decide anything.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Bubble counts every bit of work its servers do for your app and bills you for the total. The unit is called a workload unit, or WU. A page opening, a search of your database, a workflow saving a record and a call to another service all add to the count. If your plan runs out, extra use is billed as overages, which are pay-as-you-go charges on top of your plan.

A rising bill is not always a bug. Bubble's own guide says that as an app grows and is used more, higher workload is expected. The problem is when usage rises faster than your business does. That is what this page helps you find. It is written for owners, so I use plain words and keep the builder jargon to a minimum.

What you actually pay for

As of November 2026, Bubble's web-only plans on its manual's pricing table are Starter at $32 a month billed annually ($39 monthly), Growth at $119 annually ($134 monthly) and Team at $349 annually ($399 monthly). Each plan includes a number of workload units a month. Check Bubble's pricing page for the amount on your plan, because it changes.

If you use more than your plan includes, you have two options. You can buy a workload tier, which is a block of extra units at a volume discount. Or you can let overages run. Bubble's pricing FAQ says that without a workload tier the overage rate is $0.30 per 1,000 workload units. You can also switch overages off. If you do and the app hits its limit, Bubble takes the app offline until you turn overages back on, buy a tier, or reach the next billing period. Do not switch them off on a live business app without a plan, because your customers see a dead app.

Bubble emails you at 75 percent and at 100 percent of your monthly allowance, and sends spike alerts when daily use is well above your recent average. Turn those emails on and read them. You can also set custom alerts for any amount over 1,000 WU.

Step 1: find what is eating the units

Do not guess. Bubble gives you a chart for this. Open your app's Logs area and find the App Metrics view. It shows a bar for each day over the last 30 days, and a pie chart that splits the work by activity type: page loads, searches, scheduled workflows, outbound API calls, data exports, file uploads and so on.

  1. Look for the spike day. Click the tall bar. Then click into the hours inside it. A jump at 3am usually means a scheduled job. A jump after you shared a link means traffic.
  2. Read the pie chart. One or two slices will be most of the pie. Those are your targets. Ignore the small slices.
  3. Drill down. Click the big slice to see which workflow, page or search is behind it. Bubble lets you go from the chart straight to the search or workflow in the editor.

Write down the top three offenders and their share of the total. If your top offender is 40 percent of the bill, fixing it alone could cut the bill by a large chunk. Fixing a 2 percent item changes nothing.

The usual suspects, in order of payoff

Bubble's optimization guide judges work on three things: complexity (is there a simpler way to do this), volume (how much data comes back) and repetition (how often it runs). The usual culprits map to those three words. Bubble's metrics list activities such as page loads, searches, scheduled workflows and data exports.

1. A runaway or repeating workflow

A recursive workflow is one that schedules itself to run again, often to step through a list of records. If the stopping condition is wrong, it never stops, and the units pile up quickly. Bubble has a safety feature called infinite recursion protection. You set a maximum depth for the whole app, and any workflow chain that goes deeper is stopped and logged. Bubble says new apps since July 1, 2024 have it on with a default limit of 10, and older apps can switch it on in the API tab of Settings. If your app was created before that date, check it today. It takes a minute and it is a backstop against the worst surprise bill.

2. Heavy searches that run on page load

Bubble's page-load guide says everything on a page runs each time a visitor opens or refreshes it: the page itself, the data it needs and any workflows set to run on page load. A dashboard that runs five big searches and a total on every visit will cost you each time. The fixes are simple to say. Show only what the user needs first. Put reports behind a button the user clicks. Load 20 rows, not 500. Stop showing long text fields in a list when only the title is needed. Bubble's searches guide names the same three levers: how much data comes back, how complex the filters are, and how often it repeats.

One trap: the Go to page action (the step that sends a user to a page or updates a web address parameter), even when it points at the same page, re-runs the page-load events. An app that uses it to update a web address parameter can trigger a full reload of work each time.

3. Scheduled jobs that run too often

A recurring workflow that checks for new records every minute does 1,440 runs a day, whether or not there is anything to find. If the business only needs a check every 15 minutes, you have cut that work by about 93 percent. Ask of every scheduled job: how often does the business really need this, and can it run only when something changes?

4. Outbound API calls and data exports

Calls to other services, large exports and CSV imports all show up as their own slices. A nightly export of your whole customer list when you only need yesterday's changes is a common waste. Bubble's metrics view lists these separately, so they are easy to spot.

5. Traffic you did not intend

Because page load work happens on every visit, visits you do not value still cost you. Bubble's page-load guide notes that users sometimes refresh the page on their own, so one user does not always mean one page load. Your own team testing on the live app counts too. Check the hour-by-hour chart: steady, odd-hour load with no matching sales is a hint that something other than customers is visiting. If you suspect that, a Bubble developer can help you look at the app's logs. I would not block anything without that review, as you could block visitors you want.

A worked example (made-up figures)

This is an invented example to show the order of work. Say your plan includes 175,000 units (an invented figure, check your own plan) and you used 600,000 last month with no workload tier. The 425,000 over the line is billed at $0.30 per 1,000, which is about $127.50 in overages on top of your plan price. In App Metrics you find that one scheduled workflow is 45 percent of all units and a dashboard page's searches are 30 percent.

  • You change the scheduled workflow from every minute to every 15 minutes. Its share drops by roughly 90 percent: 270,000 units become about 27,000. You saved about 243,000 units.
  • You move the dashboard's reports behind a "Show report" button and load 20 rows instead of 200. Say that halves the 180,000 units: another 90,000 saved.

New total: about 267,000 units. Overages fall to about 92,000 over the line, roughly $27.60. The bill went from about $127.50 in overages to about $27.60 for a few hours of work. Your own numbers will differ, but the shape is typical: two fixes beat twenty.

Should you leave Bubble?

Only after the clean-up. A migration to code is a rebuild: your data can usually be exported from Bubble (check what the export covers for your app), but in my experience the screens and the logic have to be written again. That costs real money. So the question is simple arithmetic.

Break-even months = one-off cost of the move, divided by the monthly saving.

Example, with invented figures: after your clean-up Bubble costs you $350 a month all in (plan, tier, overages and plugins). A code version would cost about $120 a month to host and maintain. The saving is $230 a month. If the rebuild costs $9,000, break-even is about 39 months. That is a poor trade unless you also need something Bubble cannot do. If the rebuild costs $4,000, break-even is about 17 months, and it becomes worth a conversation.

Stay on Bubble ifLook at leaving if
The bill is stable after fixesThe bill is still climbing faster than revenue after fixes
Break-even is longer than about 2 yearsBreak-even is under a year or two
Your team edits the app themselvesYou need things Bubble handles badly, such as heavy data work
The app is small and still changingThe app is stable and the rules rarely change

For the longer comparison, read Bubble agency versus custom code and Bubble alternatives. If an AI builder is tempting you, Bubble versus AI app builders explains the catch. If you are checking what you would be able to take with you, how to export code from an AI app builder sets out what to ask any tool. And if you would rather have a senior person advise you part-time than hire an agency, see fractional CTO versus development agency.

When to get a Bubble developer

Get help if you cannot read the App Metrics chart, if the top offender is a workflow you did not build, or if the app is slow as well as expensive. Slow and expensive together usually share a cause: too much data coming back. A good Bubble developer can often find it in a few hours. Ask them to show you the before and after in App Metrics, not just tell you it is better.

How I'd approach this

I would spend one afternoon on the chart before spending any money. Find the top two slices, fix them, then wait a week and read the chart again. Do not cap overages to save money on a live app, because the cost of a dead app is higher than the bill. Turn the usage alerts on so a spike reaches you in a day, not at month end.

Then work out break-even with your real numbers. If the answer is more than two years, stay and keep the app tidy. If it is under a year, plan a move, but do it in stages: keep Bubble running while the new version takes over one workflow at a time. If you want a second pair of eyes on the numbers, Blur Studio fixes and finishes start around $1,500, and the fix page shows what is included.

Questions people ask

What is a workload unit in Bubble?

It is Bubble's measure of the work its servers do to run your app: searching the database, saving records, loading pages, running workflows and calling other services. Your plan includes a monthly amount, and use above that is billed as overages.

How much does a Bubble overage cost?

Bubble's pricing FAQ says the overage rate is $0.30 per 1,000 workload units if you have no workload tier, as of November 2026. If you have a tier, your rate is on Bubble's pricing page. Check there for the current figure before you plan around it.

Can I stop Bubble from charging overages?

Yes, you can switch overages off in the app plan settings. The catch is that when the app hits its limit, Bubble takes it offline until overages are on again, you buy a tier or the next billing period starts. For a live business app that is usually a worse outcome than a bigger bill.

Why did my Bubble bill suddenly jump?

Open App Metrics and click the tall bar for the day it jumped. Common causes are a recursive workflow with a bad stopping condition, a new feature that runs heavy searches on page load, a scheduled job set to run too often, or a burst of traffic. Bubble also emails spike alerts, so check your inbox for them.

Is it cheaper to move off Bubble to custom code?

Sometimes, but only after the clean-up and only if the monthly saving repays the rebuild cost in a reasonable time. Divide the one-off cost by the monthly saving to get break-even in months. The comparison is explained in Bubble agency versus custom code.

Do I need a Bubble developer to cut my workload?

Not always. Many fixes, like moving reports behind a button or running a job less often, are small. If you cannot read the metrics or the offender is complex, a developer can find it in hours. A good one shows you before and after charts. See Bubble alternatives if the answer is to move.

More in this topic: Problem solving: AI-built and no-code apps (26 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…