Bubble.io Pricing 2026 — What Does It Actually Cost?
Every plan dissected. Server units demystified. Hidden costs exposed. Real-world cost scenarios for MVPs, SaaS products, marketplaces, and agencies — so you can budget your Bubble project with zero surprises.
Bubble.io Pricing at a Glance — 2026
Bubble.io uses a tiered infrastructure-based pricing model. You pay for the platform capacity your app runs on — not per user, not per transaction, and not a percentage of revenue. This makes Bubble economically very different from many SaaS platforms: a single monthly plan can serve 1 user or 100,000 users at the same cost.
There are four core plans: Free, Starter, Growth, and Team, plus a custom Enterprise tier. All prices below are current as of February 2026. Bubble periodically adjusts pricing — always verify on bubble.io/pricing before committing to an annual plan.
All Bubble.io Plans: 2026 Pricing
Annual vs. Monthly: The Maths
Annual billing saves roughly 18–20% across all plans. Starter saves $36/year ($3/month), Growth saves $180/year ($15/month), Team saves $600/year ($50/month). If you are building something you are committed to for at least 12 months, annual billing is the clear choice. If you are still validating whether Bubble is right for your project, monthly gives you an exit with no penalty.
Server Units Explained — The Number That Actually Matters
Server Units (SUs) are Bubble’s measure of compute capacity. Every action your app takes consumes SUs: loading a page, running a workflow, querying the database, calling an external API, sending an email. Your plan includes a fixed SU allocation. When your app consistently uses more than its allocation, Bubble throttles performance — it becomes slower, not inaccessible.
Understanding SUs is the key to choosing the right plan. An app with 50 daily users that runs complex nested workflows might need more SUs than an app with 500 daily users that is well-optimised. It is always about efficiency, not just scale.
SU Allocation by Plan
DAU estimates are rough guides, not guarantees
The “Daily Active User” estimates above assume a reasonably well-optimised app. A poorly-built app with excessive client-side filtering (:filtered by on large lists), deeply nested repeating groups, or unoptimised workflows will consume SUs far faster than the estimates suggest. If you are hitting SU limits earlier than expected, optimise first — before upgrading your plan.
What Consumes the Most Server Units?
Add-On SU Capacity: Prices
If your app regularly exceeds its plan’s SU allocation, you can purchase additional capacity without upgrading your plan. Add-on SUs are available on Growth and Team plans.
| Add-On Package | Additional SUs | Price/Month | Best For |
|---|---|---|---|
| Capacity Boost S | +25 SUs | ~$25/mo | Starter apps approaching the limit |
| Capacity Boost M | +50 SUs | ~$45/mo | Growth apps with traffic spikes |
| Capacity Boost L | +100 SUs | ~$80/mo | High-traffic apps below Team threshold |
| Capacity Boost XL | +200 SUs | ~$150/mo | Apps approaching Team-tier scale |
* Add-on pricing is approximate and subject to change. Verify current prices in your Bubble account dashboard under Settings → Plan.
Full Feature Comparison: Free vs. Starter vs. Growth vs. Team
The plan summary cards above show the highlights. This table is the exhaustive comparison — every feature, every limit, side by side. Use this to make the final call on which plan is right for your project at launch, and which you’ll need when you scale.
| Feature | Free | Starter | Growth | Team |
|---|---|---|---|---|
| ▶ PRICING | ||||
| Monthly (billed monthly) | $0 | $32 | $134 | $399 |
| Monthly (billed annually) | $0 | $29 | $119 | $349 |
| Annual total (prepaid) | $0 | $348 | $1,428 | $4,188 |
| ▶ CAPACITY | ||||
| Server Units included | 2 | 50 | 150 | 500 |
| File storage | 100 MB | 2 GB | 10 GB | 50 GB |
| Database capacity | Limited | Standard | Standard | Standard |
| Add-on SU capacity available | — | Limited | ✓ | ✓ |
| ▶ DEPLOYMENT & DOMAIN | ||||
| Production deployment | — | ✓ | ✓ | ✓ |
| Custom domain | — | ✓ | ✓ | ✓ |
| SSL certificate (auto) | — | ✓ | ✓ | ✓ |
| Custom email domain | — | — | — | ✓ |
| “Built with Bubble” badge removed | — | ✓ | ✓ | ✓ |
| ▶ COLLABORATION | ||||
| Collaborators (editors) | 1 | 2 | 5 | 15 |
| Additional collaborator seats | — | — | Add-on | Add-on |
| Guest (view-only) access | ✓ | ✓ | ✓ | ✓ |
| ▶ BACKUPS & HISTORY | ||||
| Automated backups | — | Daily | Daily | Hourly |
| Manual backup & restore | — | ✓ | ✓ | ✓ |
| Version history | 7 days | 14 days | 30 days | 90 days |
| ▶ DEVELOPER FEATURES | ||||
| API Connector | ✓ | ✓ | ✓ | ✓ |
| Backend (server-side) workflows | ✓ | ✓ | ✓ | ✓ |
| Scheduled workflows (recurring) | — | — | ✓ | ✓ |
| Sub-apps | — | — | — | ✓ |
| Bubble native plugin development | ✓ | ✓ | ✓ | ✓ |
| App metrics & logs | Basic | Basic | Advanced | Advanced |
| ▶ SUPPORT | ||||
| Community forum access | ✓ | ✓ | ✓ | ✓ |
| Email support | — | Standard | Standard | Priority |
| Priority support queue | — | — | — | ✓ |
| Dedicated success manager | — | — | — | Enterprise only |
Which Plan Is Right for Your Project?
The right plan depends on three factors: your deployment stage, your expected traffic, and your team size. These four scenarios cover the vast majority of Bubble projects. Find the one that matches your situation.
You are still building, validating your idea, or have just launched with early users.
- ✓Building an MVP or prototype (use Free)
- ✓Under 100 daily active users
- ✓Solo builder or one co-builder
- ✓Need a custom domain (use Starter)
- ✓Simple app with lightweight workflows
- ✓Internal tool for a small team
You have a live product with real users, subscriptions running, and a small team.
- ✓100–500 daily active users
- ✓2–5 people editing the app
- ✓Need scheduled API workflows (billing, emails)
- ✓Growing SaaS with subscription revenue
- ✓Need 30-day version history
- ✓Most Bubble SaaS and marketplace projects
You have proven product-market fit and need scale, reliability, and larger team capacity.
- ✓500+ daily active users
- ✓6–15 builders on the team
- ✓Need hourly backups for data safety
- ✓Multiple sub-apps in your product
- ✓Custom email domain required
- ✓Marketplace or high-frequency workflows
You are a funded company or agency with complex compliance, scale, or security needs.
- ✓Need SSO / SAML authentication
- ✓Require custom data residency (EU, etc.)
- ✓Need a formal SLA / uptime guarantee
- ✓Dedicated server infrastructure
- ✓Agency managing 15+ client apps
- ✓Need DPA / BAA for HIPAA or GDPR
The Scheduled Workflows Upgrade Trigger
One of the most common reasons people upgrade from Starter to Growth is the need for scheduled API workflows. These are workflows that run automatically on a recurring basis: sending daily email digests, running monthly billing checks, auto-expiring trial periods, cleaning up old records. Starter does not include scheduled workflows. If your SaaS billing or product logic depends on recurring background jobs, you need Growth at minimum.
Bubble Enterprise: What You Get & What It Costs
Bubble Enterprise is not a fixed plan — it is a custom contract negotiated with Bubble’s sales team. Pricing is based on the number of apps, number of collaborators, server capacity requirements, compliance needs, and support tier. It typically starts around $2,000–$5,000/month and scales from there.
SSO / SAML Login
Your team members log into Bubble using your company’s identity provider (Okta, Azure AD, Google Workspace). Required for SOC 2 compliance and enterprise security policies. Only available on Enterprise.
Custom Data Residency
Store your Bubble database and files in a specific AWS region to meet GDPR, CCPA, or other data sovereignty requirements. Critical for EU-based apps serving EU customers. Available only on Enterprise.
Dedicated Infrastructure
Your app runs on dedicated servers, not shared infrastructure. Guarantees consistent performance regardless of what other Bubble customers’ apps are doing. Essential for enterprise-grade uptime SLAs.
SLA & Compliance Docs
Enterprise includes a formal Service Level Agreement with guaranteed uptime, a Data Processing Agreement (DPA) for GDPR, and BAA for HIPAA compliance if applicable. Without these, you cannot pass enterprise security reviews.
Dedicated Success Manager
A named Bubble employee who manages your account, helps with onboarding, and is your first point of contact for any technical issue or feature request. Dramatically reduces time-to-resolution versus standard support.
Custom SU Packages
Enterprise plans include custom server capacity tuned to your specific workload, with burst capacity available during traffic spikes. No throttling during normal operations — guaranteed headroom.
Frequently Asked Questions About Bubble.io Pricing
These are the questions we hear most often from founders and builders evaluating Bubble. We’ve answered each one as concretely as possible, based on real-world experience building apps across all plan tiers.
No — Bubble does not charge per end user of your application. Your plan covers unlimited end users. You can have 1 or 100,000 users in your app’s database without paying more. This is one of Bubble’s biggest advantages over per-seat SaaS platforms.
The only seat-based cost is for collaborators — people who can access and edit your app in Bubble’s editor. Free: 1, Starter: 2, Growth: 5, Team: 15. Additional collaborator seats are available as paid add-ons on Growth and Team.
Yes, absolutely. Upgrading from any plan to any higher plan is seamless. Your app, all its data, your workflows, your design — everything is preserved. Bubble upgrades are instant and non-destructive.
Downgrading is also possible but comes with restrictions: if your app uses features only available on a higher plan (like scheduled workflows on Growth), those features will stop working if you downgrade to Starter. Bubble will warn you before allowing a downgrade.
No. Bubble takes zero percentage of your app’s revenue. What your users pay you is entirely yours. Bubble only charges for the infrastructure plan.
Payment processing fees (e.g., Stripe’s 2.9% + 30¢ per transaction) are charged by your payment provider, not Bubble. This is an important distinction: Bubble’s business model is infrastructure, not transaction revenue.
Bubble throttles your app’s performance — it becomes noticeably slower for users, but it does not go offline or show an error. You will see warnings in your Bubble dashboard when you are regularly exceeding your capacity.
Your options: (1) upgrade to a higher plan, (2) purchase an SU capacity add-on, or (3) optimise your app to consume fewer SUs. In our experience, optimisation should always be the first step — many apps that appear to need a plan upgrade actually have easily-fixable inefficiencies like :filtered by overuse or unoptimised database searches.
Yes — you can build indefinitely on the free plan. The Free plan gives you access to the full Bubble editor, all plugins, and all features needed to build. The restriction is only at the deployment stage: the client’s app needs a paid plan to go live with a custom domain and real users.
Common agency workflow: build on your own Bubble account (Free or paid), then transfer the app to the client’s Bubble account when it’s ready. The client then subscribes to the appropriate plan. Alternatively, build and host under your Bubble agency account using the Team or Enterprise plan.
For most MVPs and early-stage SaaS products: yes, decisively. A full-stack developer building a comparable app from scratch would cost $80,000–$200,000+ in engineering time, plus ongoing infrastructure costs ($200–$2,000/month on AWS). Bubble lets you build the same thing for $32–$349/month in platform cost, plus 4–12 weeks of builder time instead of 6–18 months of developer time.
The calculus changes at scale. Once you have a proven product generating significant revenue, a migration to custom code may make sense for performance, control, and cost reasons. But for the first 12–24 months of product development, Bubble’s economics are almost always superior.
Many plugins in the Bubble marketplace are free. However, premium plugins from third-party developers typically cost $5–$25/month each. For a typical production app using 3–5 paid plugins, budget $20–$75/month in plugin costs on top of your Bubble plan.
Common paid plugins include: Zeroqode’s Stripe.js ($20/mo), various calendar/date pickers ($10/mo), advanced UI component libraries ($15–$25/mo), and integration-specific plugins. Always check the plugin’s pricing in the marketplace before committing to using it in your core architecture.
Each Bubble app requires its own plan subscription. You can have multiple apps in your Bubble account, but each app that you want to deploy to production needs its own paid plan. Building and testing multiple apps on the same account is free — only deployment requires a paid plan per app.
For agencies building many client apps, the Team plan includes a sub-apps feature that allows multiple related apps to share capacity. Enterprise plans support custom multi-app arrangements. If you need to manage a large portfolio of client apps, contact Bubble’s sales team about agency pricing.
Bubble does not offer a time-limited free trial of paid plans in the traditional sense. Instead, the Free plan is Bubble’s “trial” — it gives you full access to the editor, all plugins, and all features needed to build. You only pay when you are ready to deploy to production with a custom domain.
This is actually a better model for developers: you can spend weeks or months building your app without paying anything, and only upgrade when you have something ready to launch. There is no 14-day clock counting down while you are still learning the platform.
In practice, the three biggest differences are: server capacity (150 SUs vs. 500 SUs), backup frequency (daily vs. hourly), and collaborators (5 vs. 15). For most SaaS products, Growth is sufficient for the first 12–24 months of operation.
The most common reasons to upgrade from Growth to Team: (1) you’re consistently hitting the 150 SU limit and add-ons are no longer cost-effective, (2) you have a large team of 6+ builders working in the editor simultaneously, (3) you need hourly backups for compliance or data safety reasons, (4) you need custom email domain support for your notification emails, or (5) you need the sub-apps feature to architect a multi-product suite.
Bubble’s standard policy is that annual plans are non-refundable after the initial period. Bubble does offer a 14-day refund window for new annual subscriptions — if you upgrade to an annual plan and decide within 14 days it’s not right for you, you can request a full refund.
After the 14-day window, annual plans are billed for the full year. If you cancel mid-year, your plan remains active until the end of the billing period. You won’t be charged again, but you won’t receive a prorated refund. This is why we recommend starting with monthly billing if you are uncertain, then switching to annual once you are committed.
Yes — on all paid plans, your app is fully white-labelled. There is no “Built with Bubble” badge, no Bubble branding in the UI, and nothing in the app’s interface that reveals the underlying platform. Your users only see your custom domain, your branding, and your product.
One thing to note: technically-inclined users could potentially identify Bubble from network request patterns or HTML structure. But for all practical UX and business purposes, a Bubble app on a paid plan is indistinguishable from a custom-coded app to the end user.
This depends heavily on complexity and who builds it. Here are realistic ranges:
DIY (you build it yourself): $0–$384/year for the first year on Bubble’s Free/Starter plan, plus your time. A solo founder with 3–6 months of Bubble learning time can build a functional SaaS MVP for under $500 in total platform costs.
Freelance Bubble developer: $3,000–$25,000 to build a production-ready SaaS MVP, depending on scope and the developer’s rates. Senior Bubble developers charge $75–$150/hour. An MVP typically takes 100–300 hours.
Bubble agency (like us): $8,000–$60,000+ for a full-featured SaaS product, depending on complexity, design requirements, and integrations. Ongoing Bubble plan costs ($32–$349/month) are separate.
Mistake 1: Starting on Growth when Starter would work fine. Many founders pay for Growth capacity before they need it. Unless you specifically need scheduled workflows or more than 2 collaborators, start on Starter and upgrade when you’re approaching limits.
Mistake 2: Not accounting for third-party service costs. The Bubble plan is just the foundation. Budget 2–3× your Bubble plan cost for the full stack (Stripe, email, plugins, etc.).
Mistake 3: Upgrading instead of optimising. When an app hits its SU limit, the first response should always be to audit and optimise workflows and database queries — not immediately upgrade. Optimisation is almost always faster and cheaper.
Mistake 4: Choosing monthly when annual would save money. If you are committing to a 12-month build, annual billing saves 18–20% — that’s $84–$600/year depending on plan.
Bubble does not publicly advertise student or nonprofit discounts as of 2026. However, Bubble has previously partnered with startup accelerators and educational programs to offer discounted access. It is worth contacting Bubble’s support team directly to ask about any current educational pricing or social impact programs.
For students, the most practical route is the Free plan for learning and prototyping, with an upgrade to Starter ($32/month annual) only when a project is ready to launch. The Free plan is fully capable for educational purposes and building portfolio projects.
When & How to Upgrade Your Bubble Plan
Knowing when to upgrade is as important as knowing which plan to start on. Upgrading too early wastes money. Waiting too long degrades your users’ experience. These are the signals that tell you it’s time.
Clear Signals You Need to Upgrade
- ✓You need a custom domain. This is the clearest signal. Free plan only gives you a bubbleapps.io subdomain. Any production launch needs Starter minimum.
- ✓You need scheduled/recurring workflows. Automated billing checks, trial expiry workflows, recurring email sends — these require Growth. If your SaaS depends on time-based automation, you need Growth.
- ✓Your app is consistently slow. If page loads are taking 3+ seconds and you’ve already optimised your searches and workflows, you’re likely hitting SU limits. Check your capacity meter in the dashboard first.
- ✓You have more than 2 people building. Starter allows 2 collaborators. Adding a third builder requires Growth (5 collaborators) or an add-on.
- ⚠You are manually triggering things that should be automated. If you’re manually sending follow-up emails or manually processing recurring tasks, that’s a signal you need Growth’s scheduled workflows.
- ⚠A data incident would be catastrophic. Daily backups on Starter may not be sufficient if a bug corrupts your data. Growth’s same daily backup frequency won’t help much — but Team’s hourly backups provide much finer-grained recovery points.
The Right Time to Invest in Optimisation vs. Upgrade
Optimise First When…
You are hitting SU limits but your user count is still low (<200 DAU). Optimisation (removing :filtered by, fixing nested searches, reducing workflow steps) often recovers 30–60% of SU consumption and is effectively free performance gain.
Upgrade When…
You have already optimised and are still hitting limits. Or you need a specific feature (scheduled workflows, more collaborators) that is only available on a higher plan. Or your user growth means the higher plan is clearly where you’re heading in the next 3 months anyway.
Ready to Build on Bubble?
We build production-grade SaaS products, marketplaces, and internal tools on Bubble —
from architecture and data modelling through to Stripe billing and launch.