I tried an AI app builder last month that promised to get me from idea to launch in hours.
It delivered. The app actually worked—form validation, backend logic, even a decent UI. I was genuinely impressed.
Then I asked: "How do I deploy this myself?"
The answer: "You can't. You have to use our hosting."
Their pricing? $99/month minimum, non-negotiable. And if I ever wanted to leave, my app stayed behind.
That's when it hit me—I didn't build anything. I rented access to their infrastructure wrapped in a friendly UI.
I started thinking about this differently after that. The builders worth their salt aren't the ones that generate code you can't touch. They're the ones that give you:
The builders that lock you in aren't being helpful. They're being extractive.
I've since built two small apps using tools that actually let me own the output, and the peace of mind alone is worth the extra friction.
Real question for this community: Have you hit this wall with a tool? What made you finally switch to something where you actually own what you build?
The cleanest ownership test is whether a founder can rebuild the production environment from an exported repository and documented dependencies without the vendor. Code export alone can still be theater if auth, database schema, secrets, migrations, or deployment configuration remain proprietary. Builders should publish an exit checklist before signup: what exports, what does not, and the estimated migration work.
The difference between generating an app and actually owning what gets generated is a useful distinction. Curious how many builders discover the hosting limitation only after they’ve already built something.