Bubble
No-code platform for building real web applications with a database, workflows and user accounts, not just pages.
Quick facts
| Pricing | Freemium |
|---|---|
| Free tier | Yes — free plan for building and testing, with limits on workload and custom domains |
| Platforms | Web |
| Developer | Bubble |
| Website | https://bubble.io |
What Bubble is
Bubble is a no-code platform for building web applications rather than websites. You assemble pages visually, define a database with related tables, and express logic through a workflow editor; the platform then runs the application on its own infrastructure, including user accounts, file storage and APIs. The point is that a real application — with authentication, roles and state — can be shipped without writing code, which is a different job from dragging together a marketing page. It supports plugins, custom JavaScript when you need it, and an API connector for outside services. The limits are performance and lock-in: complex apps on shared plans can feel slow, and portability is limited because the logic lives in Bubble's model rather than in code you can take elsewhere. Pricing scales with workload units, which is hard to forecast before launch, so a prototype can be cheap while a launched product is not.
Best for
- Internal tools and client portals built without engineers
- Marketplaces and SaaS prototypes that need a real database
- Founders testing an idea before committing to a codebase
Not ideal for
- High-traffic consumer apps with strict performance targets
- Teams that need to export the app and leave the platform
Pros
- Genuine application logic, not just page layout
- Database, authentication and APIs are built in
- Plugins and custom JavaScript cover gaps
Cons
- Workload-based pricing is hard to forecast
- Performance degrades on complex apps at low tiers
- Logic lives in the platform, so migration means a rebuild
Pricing in detail
The free plan allows building and testing on a Bubble subdomain with a workload allowance and no custom domain. Paid plans are billed monthly or annually and add a custom domain, more workload units, collaboration seats and server capacity; production traffic is billed through workload units rather than page views. Because workload scales with usage, budget from expected activity rather than from the plan name, and watch the unit consumption during a pilot.