What is Lovable, what does it cost, and who owns the code it builds?

What is Lovable? An AI platform that builds a working web app (screens, database, sign-in) from a plain-English description, and then hosts it for you. What does it cost? It's free to start with 5 build credits a day (up to 30 a month); Pro starts at $25 a month for 100 credits and Business at $50, per Lovable's own pricing on November 3, 2026. Who owns what it builds? You do, under Lovable's Terms: your apps, code and AI output. Two catches: the same Terms give Lovable a license to use your content, and since September 9, 2026 content from Free and Pro accounts may be used to train Lovable's models unless you switch that off.

What is Lovable, in plain words?

Lovable's documentation opens with: "Lovable is a full-stack AI development platform for building, iterating on, and deploying web applications using natural language, with real code, security, and enterprise governance." In practice: "You describe what you want to build, and Lovable generates a working application that includes frontend, backend, database, authentication, and integrations, all backed by editable code."

Three parts make up every Lovable app, per its ownership docs:

• The code. Real source code, "managed in Lovable, synced via Git sync" to a repository if you connect one. Apps created from May 13, 2026 use TanStack Start, which runs server code; older apps use React and Vite and build to static files.
• The frontend hosting. Lovable's docs say "Lovable hosts your app", and hosting "scales with traffic automatically."
• The backend and data. A built-in backend Lovable calls Cloud, with "a database, storage, authentication, realtime, and functions." Lovable says it "utilizes Supabase's open-source foundation", so you don't need your own Supabase account: "Do I need Supabase? No." If those words are new, what Supabase is and what a backend does are short primers.

We haven't built a production app in Lovable ourselves, so this page reports Lovable's own documentation, pricing and Terms, not a hands-on review.

How much does Lovable cost?

Free to start, then $25 a month for Pro with 100 credits. Here is every self-serve plan as Lovable's pricing page and plan docs listed it on November 3, 2026 (USD, monthly billing unless noted):

A few rules from the same pages that change what you actually pay:

• Bigger tiers. Pro and Business come in tiers from 100 to 10,000 credits a month. Pro tops out at $2,250 a month for 10,000 credits. At the entry tier, $25 for 100 credits is $0.25 a credit, the "plan credit rate" Lovable's credits docs list for Pro; Business is $0.50 a credit.
• Seats are free. "Workspaces support unlimited members on all plans", and a workspace shares one credit pool.
• Credits expire. On monthly billing, plan credits expire two months after they're issued (on yearly billing, one month after the billing year ends); top-up credits last 12 months; daily build credits don't roll over. Credits "aren't refundable or redeemable for cash."
• Students and teachers get 50% off Pro (100 credits, monthly billing) for up to 12 months, verified through an academic email at lovable.dev/students.
• Hosting is usually covered. Lovable's pricing FAQ says that for "smaller or new apps", the cost to keep an app running is "minimal and fully covered by the included grant"; busier apps draw on your credit balance.

What does one prompt cost in credits?

It depends on the job. Lovable's pricing FAQ gives examples: "Make the button gray" cost 0.50 credits, "Remove the footer" 0.90, "Add authentication with sign up and login" 1.20, and "Build me a landing page, use images" 1.70. Plan Mode is 1 credit per message, plus the cost of any research Lovable runs while planning. Lovable's Terms add a line every buyer should read: credits are used "regardless of the outcome," including when the output "must be regenerated." A prompt that breaks something still costs credits, so the free plan's 30 credits a month go faster than the examples suggest.

Who owns the code and the app Lovable builds?

You do. Lovable's Terms of Service (last updated August 28, 2026) say: "As between us, you own your Customer Data, including the applications, websites, or other projects you build using the Services. As between us, you also own any AI Output generated for you through the Services, subject to any third-party rights in the underlying models, training data, or outputs."

Lovable's ownership docs put it more simply: "Your apps, code, and content you create with Lovable are yours, subject to third-party rights such as open-source licenses. You can modify them, use them commercially, and host them wherever you choose."

Three limits sit in the same Terms, and they matter more than the headline:

• Lovable gets a license to your content. "You grant us a worldwide, perpetual, royalty-free license to use, copy, modify, process, analyze, and otherwise exploit your Customer Data for our business purposes," including "developing and training artificial intelligence and machine learning models." Ownership and a license are different things: you keep the app, but Lovable may use what you put in.
• Your output isn't unique. "AI Output may be similar or identical to content generated for other users who submit similar prompts." Owning your code doesn't stop someone else from getting near-identical code.
• The free web address isn't yours. For apps on yourname.lovable.app, "Lovable retains all ownership rights in the lovable.app domain and all subdomains" and can reclaim one "at any time and for any reason." If the address matters, put the app on your own domain, which needs a paid plan.

Lovable also owns the "Usage Data" (telemetry, logs, usage metrics) your activity generates, per the same Terms.

Who owns the data, and does Lovable train AI on it?

Your database is yours and portable; your prompts and code may be used for training unless you opt out. Lovable's ownership docs say: "You own your data. Your database, storage, and configuration are portable. You can export schemas and data, migrate to another provider, or run everything on infrastructure you control."

Training is a separate question, and it changed this fall. Lovable's privacy docs say: "As of September 9, 2026, customer data from Free and Pro plans may be used to train, develop, and improve Lovable's AI models and AI-powered features." Lovable defines customer data as your prompts (including attached images and files), code, project files, hosted apps, configurations and generated outputs.

What Lovable says it does not train on: "Your apps' end-user data", meaning what your visitors and customers type into your app; your account and billing details; and Business and Enterprise workspace data, which is "excluded from training by default."

Can you take your app out of Lovable?

Yes, but you set it up yourself. "When you build with Lovable, your project code is stored and managed inside the Lovable platform." To hold your own copy, connect Git sync, which is "two-way" with GitHub, GitLab or Bitbucket and is included on every plan, Free too. Editing code inside Lovable and downloading it directly are paid-plan features.

Lovable's ownership docs say "you are never locked in", and lay out what a full move involves:

• The frontend can move to any host. Older Vite apps are static files; TanStack Start apps (new from May 13, 2026) need a host that runs server code.
• The backend is the harder part. "If you move the built-in backend, the supported destinations are managed Supabase and self-hosted Supabase." And "Moving the PostgreSQL database alone does not move authentication, storage, realtime, or Edge Functions."
• Everything Lovable did for you becomes your job: hosting, backups, sign-in, secrets and security, per the docs' own list of "What changes if you stop using Lovable."

The practical rule: turn on Git sync the day you start, not the day you want to leave. If you're weighing a move to a code editor, Lovable vs Cursor vs Claude Code compares the monthly cost and what breaks.

Is a Lovable app safe to share?

Safer than a blank project, but who-sees-what is still your call. Lovable's docs say it "runs automated security checks against your database configuration, including Row Level Security (RLS) coverage," and that its hosting is "SOC 2 Type 2 and ISO 27001 certified." Neither decides who in your app may see which rows. That's what Row Level Security is for; the short list to confirm before you share the link is the six things to fix in your Lovable app. If the app slows down as data grows, here's why, and the full pre-launch list is everything to check before real people use your app.

This page has no affiliate links or sponsored placements; we don't have a referral deal with Lovable. Every price, quote and rule here comes from Lovable's own pricing page, documentation and Terms of Service, read November 3, 2026. Plans change, so check lovable.dev/pricing before you budget.