Vibe coding costs, code ownership & exit plans

Use a common unit of work

Different products charge in credits, tokens, agent actions, subscriptions, or combinations of these. The units are not interchangeable. Giving each tool one prompt does not create a fair cost comparison when one generates a complete app and another expects more setup or iteration.

Define a deliverable and record the total work needed to accept it. Include planning, revisions, fixing defects, deployment, and handoff. Keep actual spending records and note the plan and date. This reference has not run that study and does not declare a cheapest product or publish unverified monthly price figures.

Separate building from running

Development usage is only one part of the budget. A launched app can incur hosting, compute, database calls, storage, bandwidth, domains, transactional email, payment processing, or external AI costs. Some resources are bundled; some have limits or overages. Ask what happens when an allowance is reached and whether spending controls are available.

Estimate both a quiet month and a busier month using an explicit workload. Identify which cost grows with users, requests, stored data, or generated media. A free prototype can become an expensive production service if every visitor triggers an unbounded external API call.

Code rights and code access differ

Lovable's introduction says users retain code ownership, and Bolt's introduction says created code can be used for legal purposes including commercial projects. Those statements are useful starting points, but the current terms remain the authority for legal questions. Third-party packages, generated assets, and user-provided content may have their own licenses.

Macaly documents paid source-code ZIP export and plan-dependent GitHub integration, with GitHub excluded from Starter. Ask about access before selecting a plan for an engineering handoff. Being allowed to use code is not the same as having a complete, reproducible copy with the configuration needed to run it.

Test an exit plan

Export the source, record dependencies, and write a setup guide that lists required environment variable names without exposing secret values. Export the database separately and identify where uploaded files are stored. List authentication providers, webhooks, domains, and third-party services. Each is an operational dependency that may need migration.

Ask another developer to run a non-production copy from the handoff materials. Check that the application starts, important data can be restored, and the main workflow works. Note what still depends on the original platform and the effort required to replace it. Portability is a demonstrated workflow, not a checkbox in a comparison table.

Make the commercial decision

Choose the tool whose development and operating model fits your budget and maintenance plan. A managed builder can be sensible when it reduces work your team does not want to own; a repository-centric environment can be sensible when engineers need deeper control. Neither approach is automatically cheaper once maintenance time is counted.

Before purchase, check the current vendor plan page, renewal terms, collaboration limits, source export, domain requirements, and overage policy. Keep the dated quote. This site's Macaly affiliation is visible and its recommendation is editorial. Do not treat that preference as purchasing advice based on an independent financial or performance benchmark.

Continue reading

Your next useful step.

• Vibe coding for beginners: the learning path
• Full-stack AI apps: architecture learning path
• Deploying AI-built apps: the launch learning path
• AI app builder costs: the buying learning path