writing
Leaving Bubble, written down honestly.
Almost nobody writes seriously about migrating off Bubble, and the people who do are usually selling the migration. These are the posts we wanted to read: real numbers, named tradeoffs, and the cases where staying is the right call.
What Bubble actually costs at 10k, 50k and 200k Workload Units a month
Three usage levels with the overage arithmetic shown, so you can find your own number instead of trusting a pricing page.
When to leave Bubble, and when not to
The honest diagnostic, expanded: the six signals that mean stay, the six that mean go, and the three reasons people migrate that turn out to be wrong.
What actually breaks in a Bubble migration
The six things that reliably turn out to be harder than the plan said, and how to go and find yours before anyone quotes you.
What Bubble's privacy rules become in real code
Privacy rules translate to Postgres row level security almost one to one. The hard part is that nobody knows what the current rules say.
Bubble plugins that have no code equivalent
Most plugins are a wrapper around an API you can call directly. Sorting yours into three piles changes the shape of every quote you receive.
How to get your data out of Bubble
Your data is yours and it is gettable. The export is straightforward; the shape it arrives in is the work.
What Next.js and Supabase actually cost
The other side of the comparison, itemised from the vendors' published prices, including the costs that never appear on an invoice.
Or skip the reading and get your own number.
The calculator runs the same arithmetic these posts do, against your plan and your Workload Units. It will tell you to stay on Bubble if that is what the numbers say.