Lovable for Startups: MVP Costs, Limits and the Engineer Hand-off

Lovable fits a startup that needs a working web MVP before it has an engineer. You describe the product, the agent writes a React app with a database and logins, and it goes live on a lovable.app address. The usual path starts on Free at $0 and moves to Pro with 100 credits, $25 per month billed monthly or $21 per month billed annually, once you need payments, your own domain or editable code.^[1] That price covers the whole workspace, so cofounders add no seat cost. Lovable does not publish a startup credit or discount program. The real risks are credit burn while you iterate and hosting costs that grow with users, both paid from one balance.

Week one: a clickable product on the Free plan

A Free workspace gets 5 build credits a day, up to 30 a month, plus 20 Cloud, 4 AI and 1 connector credit a month. That is enough to learn whether the idea survives contact with real screens and flows. Build mode bills on the work done, and the pricing page lists sample costs: 1.20 credits to add sign-up and login, 1.70 to build a landing page with images. Plan mode costs 1 credit per message plus any research it runs. Thirty credits will not build a company. They will build a demo.

That demo can go public. Free projects publish to lovable.app for anyone with the link, or invite-only for up to 10 people per project, which suits early interviews with a named group of prospects. Lovable's SEO docs treat a lovable.app address as fine for MVPs, demos and paid-traffic tests, and a custom domain as the way to build search presence. Lovable owns those subdomains and can reclaim one, generally with 7 days' notice. A Free project without a custom domain can also be unpublished after 12 months with neither visits nor an owner login.

Three things that push a founder onto Pro

Payments come first. Built-in payments, where Lovable creates and manages a Stripe or Paddle account for subscriptions or one-time sales of software, start on Pro. Lovable adds no fee of its own: Stripe charges its standard rates, and Paddle through Lovable takes 5.0% + $0.50 per transaction, or a flat 10% under $10, acting as merchant of record with no monthly fee.^[2] On Free you can still paste your own Stripe key, but only one key works at a time, so a live key turns test payments in the preview into real charges.

The second trigger is looking like a real company. Connecting a custom domain needs a paid plan, as does hiding the Edit with Lovable badge, and both matter once you pitch paying customers. App emails from your own domain also begin on Pro, with 50,000 transactional emails a month per paid workspace. The third trigger is code. Free shows code read-only, while Pro opens the code editor and the zip download of the whole codebase, which a technical cofounder will want quickly.

The term matters more than the tier at this stage. By our arithmetic, Pro with 100 credits costs $300 a year at $25 per month billed monthly, against one charge of $250 a year at $21 per month billed annually, so annual saves $50. Because that annual charge equals ten monthly payments, monthly billing costs less for any team that stops within 9 months. Runway decides. On top of plan credits, Pro keeps the 5 build credits a day, about 150 in a 30-day month if used daily (some regional plans cap them at 30 a month), and those never roll over.

Business with 100 credits costs $50 per month billed monthly or $42 per month billed annually, per workspace. A Business credit costs twice a Pro credit at most menu options, so the same credit count costs twice as much on Business; for Cloud and AI the dollar cost is the same, which is why a Business workspace shows fewer credits used for them. At seed stage, Business is about obligations, not capacity. If no customer asks for the Business-only items, workspace SSO and an included DPA, Pro covers a small team, because every paid plan is priced per workspace with unlimited users.

When real users arrive, so does the hosting bill

Lovable Cloud gives each project a PostgreSQL database, user accounts, file storage and edge functions, built on Supabase, and it bills from the same credit balance you build with. Each Free, Pro and Business workspace spends its 20 Cloud credits and 4 AI credits a month first, then general credits. Lovable says most small or new apps cost nothing beyond the Cloud grant, while apps with significant traffic or size draw on the balance. Visitors spend the owner's credits. A launch spike is a credit event.

Instance size drives much of that cost. A larger database instance costs more credits for every hour the app runs, and the Manage instance dialog estimates the monthly Cloud cost in credits from the last 30 days. Lovable publishes no dollar price per instance size. Free apps created from May 2026 are capped at 1,000 server requests per project per 10 seconds, while paid plans carry no visitor or bandwidth cap. Our Lovable Cloud guide covers regions, backups and sizing.

Running dry is the scenario to plan for. At zero, the published site keeps serving, but AI features return errors and apps on the built-in backend pause, so data, logins and storage stop until you add credits and click Wake up; a top-up alone does not restart them.^[3] Top-ups cost $15 per 50 credits on Pro, which is $0.30 per credit against $0.25 per credit inside Pro with 100 credits billed monthly, and they last 12 months. Usage limits and alerts start on Pro. Set them before launch.

Keeping iteration from draining the balance

Every Build attempt is billed, including output you throw away, and reverting to an earlier version refunds nothing. Fix loops are the most expensive habit in an early product. Subscription fees and credits are non-refundable except where the law requires, and the pricing breakdown covers rollover windows and cancellation. Plan mode helps here: you approve the approach for 1 credit per message, plus any research it runs, before Build spends on it, and that pays off whenever the redo it prevents would cost more.

Credit check-ins, still in beta, pause a long message at 20 credits by default, adjustable up to 100,000, though they notify rather than cap. A /goal run works unattended for up to 10 hours and costs noticeably more than a regular message, so keep it for jobs you can specify fully. Per-member monthly limits arrive on Pro, but they count build credits only and cannot cap an app's hosting spend. Some work is free: publishing from the Publish dialog, security scans, 10 free fixes per account, and editing code yourself on a paid plan.

Handing the code to your first engineer

Git sync works on every plan with GitHub, GitLab and Bitbucket Cloud, in both directions, and each project syncs to a new private repository that Lovable creates; it cannot connect or import a repository you already have.^[4] Lovable says engineers can continue the synced code in Claude Code, Cursor or other tools. Pushing to the repository never publishes the app. Connect it in week one, so the commit history already exists when you hire.

Code is the easy part. Git sync and the zip download carry source, configuration and database migration files, not database records, stored files, secrets, auth provider settings or connectors. A full database export, including user accounts with password hashes, is a separate step. Leaving Lovable Cloud means moving the backend to managed or self-hosted Supabase by hand, with no one-step move. Apps built on TanStack Start from May 2026 (June 2026 on Enterprise) also need a host that runs server code.

Some founders connect their own Supabase project from the start instead. Then Lovable credits pay only for building, Supabase bills the backend, and the backend is already yours at hand-off. The trade-off is losing the in-editor database, users and storage views, daily backups, instance resizing and managed Google sign-in. Choose early. Moving from your own Supabase into Lovable Cloud is not supported, so the decision is hard to reverse once customers have accounts.

Questions investors and first enterprise buyers will ask

Data use comes up first. Since September 2026 Lovable may use Free and Pro customer data, including prompts and code, to train its models unless the account holder opts out in Account settings; the opt-out is free and applies going forward only. Business and Enterprise workspaces are excluded by default, with no opt-out needed. A founder guarding proprietary logic should opt out on day one, because the switch does not reach back to content already sent.

Security questions follow. Lovable lists SOC 2 Type II, ISO 27001:2022 and AIUC-1, but apps you build do not inherit those certifications. Lovable signs no Business Associate Agreements, rules out HIPAA use, and its Terms bar health data unless a written agreement permits it. It sets basic row-level security automatically, and its own docs tell you to review it. Lovable says that between February and April 2026 public projects' chat history and code could potentially be accessed by any Lovable user with a project link, while private projects and Cloud were not affected.

Lovable's proof for founders is its own selection of stories. Its Series B post (December 2025) names Lumoo at 800K ARR in nine months and ShiftNex at 1M ARR in five months, and Atonom says it replaced a Salesforce contract with a CRM built on Lovable (February 2026). None show what those teams spent in credits. Support is modest: Free gets community help only, and Pro email support promises a first reply within 24 hours, mainly on weekdays, without debugging your project code.

The bottom line

For a founder without an engineer, Lovable is a fast route to a web MVP that real customers can sign into and pay through, and finding out costs $0 on Free. Move to Pro with 100 credits at $25 per month billed monthly, per workspace, once payments or a custom domain matter, and stay on monthly billing until you know you will run past 9 months. Budget for credits as users arrive, opt out of training, and connect Git sync early, because the code leaves easily and the data does not. Look elsewhere for a store-listed phone app or health data.