keep it running
Maintenance
For apps that are fine on Bubble. Bug fixes, Stripe and subscription work, API integrations, admin dashboards, Workload Unit optimization. Capped hours, two-business-day response, no on-call.
Keep it runningno-code to full stack
Your Bubble app works. The person who built it is gone. The bill keeps going up.
We take it over, fix it, run it, and move it to real code when the numbers say it makes sense. One team for the whole lifecycle, and we will tell you which half you need, including when the answer is neither.
- in codepostgresrecords become rows
- in codeapi + jobshidden logic becomes visible
- in codenext.jsscreens become a codebase
two services, one promise
Keep it running, or move it to code.
Equal weight, and genuinely different answers. Migration is the next step of the relationship when your app outgrows the platform, not an upsell attached to a maintenance contract.
move it to code
Migration
For apps that have outgrown the platform. Postgres instead of the Bubble database, API routes instead of workflows, row-level security instead of privacy rules. Incremental, so your app never goes dark.
Move it to codethe diagnostic
How to tell which one you need
Most Bubble apps should stay on Bubble. Here is the actual test, so you can run it yourself before talking to anyone, including us.
stay on bubble if
- Workload Unit spend is flat month over month
- Workflows are simple and mostly synchronous
- The user base is small and growing slowly
- Nobody is asking you about SOC 2 or HIPAA
- Nothing about the app feels slow to the people using it
- It is working, and it is cheap
time to leave if
- Workload Unit costs climb every month and you cannot see why
- Users complain that it is slow and you have run out of fixes
- You need to hire developers and cannot find Bubble ones
- SOC 2, HIPAA or data residency has entered the conversation
- An acquirer or investor is asking to see the codebase
- Native mobile performance has become a real problem
If you are reading both columns and only the first one describes you, do not migrate. That is a real answer and it is free.
the sequence
What a takeover looks like
Three steps, in this order, because each one is only possible once the previous one is done.
Audit
One week on your actual app. A feature-parity map, a 12-month cost comparison, performance findings, a risk list and a fixed quote. $500, half of it credited against whatever comes next.
Plan
What stays on Bubble, what moves, in what order, and what it costs at each stage. Yours to keep, including the option of handing it to someone else.
Execute
Either a retainer that keeps the app healthy on Bubble, or an incremental migration that never takes it offline. Usually it starts as the first and becomes the second.
two use cases, verdicts included
One stayed. One moved.
Served shows why a working Bubble app should not be migrated by default. AiudApp shows what happens when the platform becomes the ceiling. The verdict depends on the app, not the service we would rather sell.
maintenance was the answer
Served: stayed on Bubble
Built by someone else and handed over mid-flight, with Stripe subscriptions to rebuild, missing admin reporting, and a backlog of web and mobile bugs. It is still on Bubble because the cost case for migrating was not there.
- took over
- mid-flight
- No original developer, documentation, or handover call.
- scope
- stripe + admin
- Subscription billing rebuilt and reporting added from scratch.
- verdict
- stay on bubble
- The platform was still the right fit. We said so.
migration was the answer
AiudApp: moved to code
AiudApp was preparing to grow, but no-code had become the boundary. Workload Unit economics constrained the system while the builders constrained what the product experience could become. We migrated the ecosystem to code so every layer could be controlled directly.
- pressure
- growth
- The platform had become the ceiling, not the product.
- constraint
- WU + UI/UX
- Usage economics and builder limits were holding it back.
- verdict
- move to code
- Full control over data, workflows, and product experience.
so nobody wastes a call
Who we don’t work with
- New MVPs
- We do not build from scratch. If there is no live app yet, we are the wrong shop and there are better ones for that.
- Apps that are working fine and cheap
- Do not migrate for the sake of it. If your Workload Unit line is flat and nobody is complaining, keep your money.
- Anyone who wants a fixed migration quote without an audit
- That number would be invented. We would rather lose the job than guess at it.
Cheaper than an agency, more thorough than an export tool, and the only one that will tell you not to bother.
Everything on this site routes to the same place: a paid audit of the app you already have. $500, one week, half of it credited against a migration if one follows.