Bubble’s pricing model trips up founders more than almost any other no-code platform. Not because it’s unreasonable — it’s actually quite flexible — but because the unit of measurement (the Workload Unit) is invisible until you have a live app. By then, the surprises have already started showing up on your statement.

I’ve worked with Bubble apps across the range: MVPs that barely touched 50k WUs a month, and SaaS products that blew past 400k WUs before hitting their growth stride. The patterns of where costs spike are consistent, and they’re mostly avoidable once you know what to look for.

This guide covers everything: what a WU actually is, what each plan includes, the workload tier math, and the specific app behaviors that drain your budget fastest.

What Is a Workload Unit — Actually?

Bubble’s own docs describe it cleanly: a Workload Unit measures the server processing required to run your app. Every time something happens on the server side — a database search, a workflow trigger, an API call, a user login — Bubble logs the computational effort and counts it toward your monthly total.

Think of it like electricity for your app. Each action draws a different amount of current. A simple page load that reads five fields from one database record barely registers. A workflow that searches your entire user table, filters by multiple conditions, then fires three separate API calls? That’s a serious draw.

The 12 activity types that contribute to workload (per Bubble’s own documentation):

One thing worth knowing: both your Live and Development environments consume WUs. You get 100,000 WUs/month for the Dev environment on any paid plan, separate from your live allocation. That matters during heavy testing phases — if you’re running bulk data operations to clean up test records, those count.

Bubble.io Plans Compared: WUs, Features, and Real Costs

Here’s the full breakdown. All prices shown are annual billing (which saves roughly 10–15% vs. monthly).

Something worth noting: the jump from Starter to Growth is steep ($29 to $119) but the WU increase is relatively modest — 175k to 250k. Most founders on Growth are there for the extra collaborator seat and the 14-day server logs for debugging, not purely for WUs. If you genuinely just need more capacity without the extra features, the Workload Tier system is usually cheaper.

Workload Tiers: The Smarter Way to Handle Overage

Here’s where a lot of founders leave money on the table. When your app starts approaching its WU limit, most people assume they need to upgrade their plan. That’s often not necessary, and it’s frequently more expensive than the alternative.

Workload Tiers are add-on packages you buy on top of your existing plan. They give you pre-purchased WUs at a discounted rate compared to standard overage pricing. The more you buy, the lower your per-unit cost.

The math here is stark. If you burn 300,000 WUs over your Starter limit in a month, the standard overage bill would be $90. With Tier 1 ($29/mo), you’d pay $29 for the tier plus a fractional overage — total bill under $35. The tier pays for itself the moment you use more than about 100k bonus WUs.

What Actually Drains Your WUs (Real Patterns)

This is where generic guides tend to fail you. They’ll say “database searches use WUs” without showing you the specific patterns that blow budgets in practice. After building and auditing a number of Bubble apps, here’s what actually causes runaway costs.

1. Database Searches Inside Repeating Groups

This is the most common offender. When you put a “Do a Search For” constraint directly inside a repeating group, Bubble runs that search once per row returned. If your repeating group shows 50 users and each row fetches their latest order status, that’s 50 database searches per page load — not one. On a high-traffic page, this adds up extremely fast.

The fix: fetch all needed data outside the repeating group and pass it in as a data source. One search, not fifty.

2. Scheduled Backend Workflows That Run Too Frequently

Recurring workflows are brilliant for automation but they run whether or not there’s anything meaningful to process. A workflow that checks for updates every five minutes across 10,000 users fires 2,880 times a day. Even if each run is cheap, the volume multiplies quickly. Audit your scheduled workflows and ask: does this actually need to run this often?

3. Poorly Constrained API Calls

Every API Connector call pulls from your WU balance. When your app calls a third-party API on each page load — say, fetching a real-time exchange rate that doesn’t actually change more than once an hour — you’re burning WUs on information you could cache or store. A simple caching pattern (store the result in your database with a timestamp, refresh only when stale) can eliminate 95% of those calls.

4. Bulk Operations in Dev Environment

Don’t forget: your Development environment has its own WU allocation (100,000/month), but heavy bulk operations — importing test data, running cleanup scripts — count against that. If your dev WU allotment runs out mid-sprint, it disrupts your workflow. Keep bulk operations lightweight in Dev and run large data jobs only when necessary.

5. Search “Get All” Without Constraints

Anytime you use “Get all [DataType]” without meaningful constraints, you’re loading your entire table. On small apps this is fine. On apps with tens of thousands of records, each unconstrained search is proportionally more expensive. Always filter and limit your searches — even if you’re only displaying 20 results, return only 20 results.

How to Monitor and Control Your WU Usage

Bubble gives you the tools to track this. They’re not always front-and-center, but they’re genuinely useful once you know where to look.

1. Open the Logs tab in your editor. The Workload Charts section shows your WU consumption over time — daily, weekly, and monthly views. This is your baseline dashboard.
2. Drill into activity types. Bubble’s charts break down consumption by activity (database operations, workflows, web requests). Identify which category is consuming the most, then drill further.
3. Check the App Plan tab for current usage. You’ll see your current cycle’s consumption against your limit and can buy a workload tier directly from here.
4. Toggle overage protection. If you’re on a strict budget, disable flexible overages in the App Plan settings. Bubble takes the app offline rather than charging extra — you get an email alert and can bring it back up manually or wait until next month.
5. Use Bubble’s Subscription Planner tool. It helps you figure out whether a tier or a plan upgrade makes more sense given your current usage pattern.

Which Plan Should You Actually Start On?

The honest answer varies more by stage than by ambition. Here’s how to think through it:

One scenario I see regularly: founders jump to the Growth plan for WUs when a Starter + Tier 1 combo would’ve been cheaper. Growth at $119/mo gives you 250k WUs. Starter + Tier 1 gives you 375k WUs (175k base + 200k tier) for $58/mo. The Growth plan makes sense when you need the extra collaborator seat or the longer server log retention — not purely for WU capacity.

Web, Mobile, and Web+Mobile Pricing

Bubble now separates pricing across three tracks depending on what you’re building. This trips people up when they’re planning their stack.

Important: the WU allocation is shared across both platforms on Web+Mobile plans. So if your mobile app and web app both hit users simultaneously, they pull from the same monthly pool. Factor that into your capacity planning if you’re going cross-platform.

7 Concrete Ways to Reduce Your Monthly WU Bill

These aren’t theoretical. They’re the changes that actually move the needle on real apps.

1. Move searches out of repeating groups. Always fetch data at the page or workflow level, not inside individual group cells. One search per load vs. N searches per row.
2. Use client-side logic where possible. Sorting, filtering, and counting that can happen in the browser (using custom states) doesn’t touch the server. Shift as much display logic client-side as your app allows.
3. Batch API calls. If you’re updating 500 records via an external API, look for a bulk endpoint rather than 500 individual calls. Most modern APIs support batch operations.
4. Cache external API responses. Store third-party data in a Bubble table with a “last_fetched” timestamp. Only call the API when the cache is stale (e.g., more than one hour old).
5. Audit and reduce scheduled workflow frequency. Dial back recurring jobs that run more often than necessary. A daily digest job doesn’t need to run every 15 minutes.
6. Use constraints on every search. Never return “all records” from a large table without proper filters. Add limits (e.g., max 100 results) and make sure constraints eliminate unnecessary rows server-side.
7. Review the Workload Charts weekly. Set a habit: check your WU consumption once a week. Catching a spike early — when a new feature releases and turns out to be expensive — prevents surprise end-of-month bills.

Disabling Overages: When It Makes Sense

Bubble lets you turn off flexible overages from the App Plan tab. When overages are off, your app simply stops serving requests once it hits the WU cap — no additional charges. It comes back online at the start of the next billing cycle.

When this is a reasonable choice: internal tools, admin dashboards, or apps used by a small known audience where brief downtime at month-end is acceptable and you’re on a strict budget ceiling. You’ll get an email when you hit the cap, and you can reactivate overages or buy a tier manually.

When you absolutely should not disable overages: customer-facing apps with SLAs, paid subscriber products, marketplaces, or any app where downtime means lost revenue and user trust. In those cases, keep overages enabled and instead manage costs proactively through tier purchases and optimization.

Frequently Asked Questions About Bubble WU Pricing

Do unused WUs roll over to the next month?

No. WUs reset at the start of each billing cycle. If you’ve had a quiet month and used only half your allocation, those unused units don’t carry forward. It’s a fresh pool each month.

Can I disable overages but still get notified before the app goes offline?

Yes. Bubble sends an email alert when you hit 75% of your monthly WU limit. That’s your window to act — either buy a tier or prepare for the cap.

Are WUs the same across web and mobile plans?

The WU amounts vary slightly by plan tier, but the mechanics are identical. Web+Mobile plans share a single WU pool between both platforms.

Does the Free plan get the 100k Dev environment WUs too?

The 100,000 Development WUs are included on paid plans. The Free plan has its own 50,000 WU allotment for general use (no separate live/dev split).

What happens if I’m on annual billing and need to upgrade mid-year?

Bubble allows upgrades at any time. You’ll be charged a prorated amount for the remainder of your billing cycle at the new plan’s rate. Downgrading also works, though you should check which features you’d lose before making that call.

Is there a way to see which specific workflows are eating my WUs?

Yes — the Logs tab in your editor has detailed Workload Charts that break down consumption by activity type. You can see database operations vs. workflow runs vs. web requests, and drill into specific workflows to find the expensive ones.

Pricing data referenced from Bubble.io official pricing page and Bubble documentation. Last verified June 2026.