CHI Company Investigation · AI
Lovable
The Price Stayed the Same. What a Credit Bought Didn’t.
AI app builder · Build · Chat · Hosting · Cloud backend · In-app AI
Standard company investigation · No score assigned · Research current through 4 October 2026
Not a story of value taken away. Value rose throughout. Predictability fell.
Lovable lets people build working web applications by describing them. Its Pro plan has cost $25 for 100 credits since April 2025. Over the same period the thing a credit pays for was redefined: from a fixed message, to a variable amount of work, to a single balance that pays for building an app and for keeping it running. Customers received a far more capable product, code they own and can take with them, and no per-seat charges. They also took on an economic relationship that is harder to forecast. This page sets out both halves.
- 2024EditsA daily allowance of edits
- Nov 2024MessagesOne message, one unit
- Apr 2025Flat creditsOne message, one credit
- Jun–Jul 2025Effort-priced creditsCost follows the work done
- Jun 2026Build + run creditsOne pool for building and operating
More value What customers gained
A far more capable product, code the customer owns, and no seat pricing.
An agent that plans and builds whole features, a managed database and login system, AI features inside customers’ own apps, hosting, collaboration, free security scans and private projects on the free plan. Code can be synced to the customer’s own Git repository on every plan, and published apps stay online after a downgrade.S1S22S23
Less predictable What became harder to forecast
A meter that changed meaning, and a balance that now funds the live app too.
The cost of a build request is not shown before it runs. Lovable’s terms state that credits are used whatever the result. Since June 2026 the same prepaid balance pays for development and for the live app’s backend, and Lovable does not publish a complete Cloud rate card.S6S7S2
The cleanest finding is the unit of sale. Lovable did not raise the Pro price after April 2025. It has sold five different units since 2024, two of them since April 2025, while making the product substantially more useful.
01The unit of sale
Five meters in two years. One headline price since April 2025.
Each step is defensible as pricing that tracks Lovable’s real costs, and several came with clear gains for customers. Read together, they show a meter whose meaning kept changing underneath a sticker price that has held at $25 since April 2025.
Edits per day
Pro $19 a month
Free users got 10 edits a day; Pro users 100 edits a day.S5
Cost known in advance: yes
Messages per month
Starter $20 · Launch $50 · Scale $200
Paid plans moved to monthly message limits; free use fell from 10 edits to 5 messages a day. Existing Pro subscribers were kept on their old plan for a period Lovable did not specify.S5S29
Cost known in advance: yes
Flat credits
Pro from $25 · Teams from $30
Messages became credits, still one message for one credit. Multiplayer workspaces, a security scan and custom domains arrived in the same release.S16
Cost known in advance: yes
Credits priced by work done
Pro $25 for 100 credits
Agent mode priced each request by the work it took. Lovable’s examples run from 0.50 credits to recolour a button to 1.70 for a landing page with images (2.00 in the documentation). Simple edits became cheaper; complex ones cost more, with no fixed ceiling.S17S1
Cost known in advance: no
The sticker price remained comparatively stable while the meaning of the meter changed.
The point is not that $25 is too much; at Lovable’s own examples, a simple edit now costs about half what it did under one-message-one-credit. The point is that a customer in October 2026 cannot answer “what will this cost me each month?” from the price alone, because the unit no longer means one fixed thing. Lovable scheduled the end of its flat-priced “legacy” mode for 1 September 2025.S4Pre-April 2025 prices are from Lovable’s own 2024 changelog and its November 2024 pricing post (whose web address carries a January 2025 date).S29 The move from $20 to $25 in April 2025 applied to new buyers; how earlier plan subscribers were treated was not stated. Prices are in US dollars as published in Lovable’s documentation; Lovable’s public pricing page may display a local currency.
02Customer value
What customers got in return.
CHI measures extraction against delivered value. For Lovable, the value side is strong and documented, and it belongs at the top of the page, not the bottom.
Software without a software team
People with no engineering background build working web apps by describing them. Speed to a working product is the leading theme of user reviews.S27
From front end to full stack
An agent that plans and builds features, a managed database, login, file storage, hosting and AI features inside the customer’s own app, all added or expanded while the Pro price held at $25.S18S17
The customer owns what it builds
Lovable’s terms give the customer ownership of its apps and of the AI output generated for it, subject to third-party rights.S6
Git sync on every plan
Two-way sync to the customer’s own GitHub repository is available on all plans, including Free, and the repository stays with the customer if the link is cut.S22
No per-seat pricing
Plans are priced by the credits they include, not by the number of people. Inviting colleagues does not change the subscription price; it changes how fast the shared credits are used.S1
Teamwork made free
In June 2025 Lovable made workspace collaboration free on its Free and Pro plans. Its CEO said moving Teams customers onto the cheaper Pro plan cost $1.5 million of annual recurring revenue in a single day.S4S25
Private projects on the free plan
Projects that once defaulted to public on the free plan are now workspace-private on every plan, Free included.S1
Ten free fixes
Fixes for build errors and security findings are free up to ten per account, each restored 24 hours after use. No peer examined documents an equivalent allowance.S9
Apps survive a downgrade
Downgrading or cancelling does not unpublish a project, and already-connected custom domains keep working.S23
Free scans on every plan
Quick and deep security scans are free on all plans, and Lovable says they stay free; fixes beyond the ten-fix allowance use credits.S4
Review aggregates are third-party figures recorded on the date shown; they indicate broad satisfaction, not the experience of every customer. The negative minority in those reviews concentrates on credit use, which is the subject of the next sections.S27
03Mechanism · CHI Lexicon
Correction-Cost Transfer: a category mechanism that Lovable documents plainly and mitigates more than its peers.
A pricing architecture in which the customer bears additional usage cost when probabilistic software produces an incorrect, incomplete or unusable result that must be regenerated or corrected.
Charging for compute is not itself the mechanism. The CHI concern arises when usage is outcome-insensitive, the customer cannot reliably know the final cost before work runs, and failed or incorrect output can generate further customer-paid work. Read the Lexicon entry →Where Lovable meets the definition
- Outcome-insensitive by contract. Lovable’s August 2026 terms state that credits are consumed according to the effort and resources an AI action uses, regardless of the outcome, and are neither refunded nor restored when the output is erroneous, incomplete or has to be regenerated, except where the law requires otherwise.S6
- No price before the work. Lovable’s documentation states that it does not show a credit estimate before a Build mode request runs, because the cost depends on work discovered during execution.S7
- Reverted work still counts. Messages a customer later reverts are still charged, and reverting restores the project’s code but not its database data.S8
- Ordinary corrections are ordinary usage. When an app builds but does not do what was asked, the follow-up prompt is charged at the normal rate.S2
How Lovable mitigates it
- Ten free fixes. Each account has ten free fixes, shared across “Try to fix” on build errors and fixes offered by security scans, each restored 24 hours after use. Beyond ten, fixes are charged as standard usage.S9
- Nothing charged for nothing done. A request stopped before Lovable has changed the project is not charged; a stopped request is charged only for work completed.S2
- Cheaper small corrections. Since mid-2025 a small edit can cost about half a credit, where it once cost a full credit.S17
- Runaway protection. Since August 2026 long requests pause at a credit check-in (20 credits by default) so the customer can continue or wrap up.S2
- 11 Dec 2024
Lovable’s changelog announces that fix requests (“Ask the AI to fix”) will not count toward usage limits.S5
- Jun – Jul 2025
Lovable’s documentation describes “Try to fix” as free.S14
- 22 Jul 2026
The documentation again states that clicking “Try to fix” does not use credits.S15
- 11 Aug 2026
Lovable limits free fixes to ten per account, each restored after 24 hours. The allowance covers qualifying build errors and security findings, not every corrective prompt.S4
Lovable’s own pages are silent on fix pricing between late 2025 and mid-2026 in the snapshots CHI reviewed. This page therefore makes no claim about how fixes were priced in that interval; some third-party accounts from the period conflict.
Against the comparator set
The comparators whose charging CHI could document bill AI work by effort or tokens, including work that corrects earlier output.
- v0, Replit and CursorEach moved to effort- or token-based charging in 2025 and drew public complaints about cost after the change. Cursor apologised for unclear communication and offered refunds for unexpected charges.S26
- LovableThe only company in the set that documents any free-fix allowance at all, in the documentation CHI reviewed.S9
Why Lovable’s case is instructive
Not because it is worse, but because it is explicit.
Finding: strongly supported. Lovable exhibits the category mechanism but mitigates it more than the peers examined. CHI found no evidence that Lovable causes errors in order to sell credits, and this page makes no such claim.
04Mechanism · Lovable-specific · Provisional
Build–Run Pool Coupling: one balance pays for building the app and for keeping it running.
Since June 2026, a single prepaid credit balance funds development activity and the live application’s operation. Lovable reports “build” and “run” credits separately, but its documentation is clear that these are reporting views, not separate balances.S2
Development
- BuildPlan and Build mode requests
- ChatAfter a daily chat allowance
The live app
- Hosting + CloudDatabase, storage, compute, realtime
- In-app AIModel calls made by the deployed app
What happens when the shared balance reaches zero
The static published site stays live.S2
The Cloud backend can pause with a low-balance notice, and the published app cannot read or write data until it resumes.S10
Data is kept, but cannot be accessed or exported while the services are paused.S2
The customer adds credits and wakes the project; traffic alone does not resume it.S10
Development spend and production uptime draw on the same money
Heavy building can use the credits a live app’s backend depends on, and a busy app can use credits the builder meant for development. Per-member credit limits apply to build usage only, not to the running app.S11
Prepaid, bounded and partly cushioned
Billing is prepaid, so there is no open-ended overage invoice. Monthly grants are used first. Auto top-up is opt-in, with an optional monthly spend limit. And under the old split system, ordinary plan credits could not pay for hosting; now unused and rolled-over credits can.S2S19
This is a structural fact, not an observed pattern of outages.
CHI found one independent first-person account of a live app’s backend going dark when workspace credits ran out, and no wider data on how often it happens. The unified balance has also not yet reached every workspace. Build–Run Pool Coupling is recorded as a provisional mechanism and is not added to the CHI Lexicon.S28S1105Lovable Cloud
Dependency first, repair later.
Lovable Cloud is the managed backend — database, login, storage and server functions — that Lovable switched on by default in September 2025. Its record shows both sides of this relationship: a period of significant dependency and reduced predictability, followed by meaningful remediation.
- 29 Sep 2025 · Launch
Cloud launches, enabled by default. Every workspace receives $25 of Cloud usage a month, described from the first day as a temporary offer. Lovable’s documentation answers “Can I change my mind after adding Cloud to my project?” with no: a connected project could not be disconnected.S18S13
- Dec 2025 → Jun 2026
The temporary allowance is extended. Its stated end date moves from the end of 2025, to the beginning of 2026, to the end of the first quarter, to the end of May, and then to no stated end date.S13
- 13–18 Jun 2026
The unified balance launches, and the Cloud grant becomes 20 credits a month. Lovable says the cost of Cloud and AI services did not change.S19S4
- 3 Jul 2026
Database export and removal of Cloud become available on all plans.S4
- 8 Jul 2026
Manual pause arrives: an idle backend can be paused with its data preserved, though storage is still billed while paused.S4
- Jul – Sep 2026
More controls: smaller database size steps (31 July), resource-pressure cards (7 September) and in-product monthly cost estimates for each database size (23 September), alongside the per-project usage breakdown added in June.S4S10
Monthly Cloud usage on every workspace. Temporary from launch; end date pushed back three times, then dropped.
20 credits, at Lovable’s published conversion rate of $0.25 per credit.
20 credits, at Lovable’s published conversion rate of $0.50 per credit.
Lovable publishes no credit rate for the Free plan, so no dollar equivalent is given here.
This is an economic trade-off, not a simple removal. The $25 allowance was labelled temporary from launch and outlived three stated end dates. Its replacement is smaller on paid plans at Lovable’s own conversion, and Lovable’s June announcement did not mention the earlier figure. But ordinary plan credits, including rolled-over credits, can now pay for Cloud, which they could not before, and Lovable says most small apps remain covered by the grant. The current grant is itself described as temporary.S2S1
For about nine months after launch, Lovable’s own documentation said a project connected to Lovable Cloud could not be disconnected, and no database export was offered. Export and removal arrived on 3 July 2026.
Code remained exportable through Git throughout. Current exit mechanics are materially better than at launch.S13S4S22| Capability | At launch, Sep 2025 | Today, Oct 2026 |
|---|---|---|
| Disconnect Cloud from a project | Documentation said it could not be done | Remove Lovable Cloud (permanent) |
| Database export | None documented | Full SQL export of structure and data, one per 24 hours; databases up to 15 GB, export file up to 5 GB |
| User accounts | None documented | Current documentation says the export includes accounts and password hashes |
| Stored files, server code, secrets | None documented | Files downloaded separately; server code via Git; secrets re-entered by hand |
| Pause an idle backend | Not available | Pause and wake from settings since 8 Jul 2026; storage still billed while paused |
| Application code | Exportable through Git | Exportable through Git |
There is still no one-click transfer from Cloud to a customer-owned backend; moving requires export, re-configuration of sign-in providers and keys, and re-entry of secrets. Customers who connect their own Supabase project from the start keep their backend account throughout. On Cloud, the customer does not receive the backend’s direct database credentials.S10S12S24
06Pricing and entitlements
Today’s plans, and the changes that led to them.
| Plan | Price | Included | Notes |
|---|---|---|---|
| Free | $0 | 5 build credits a day, up to 30 a month; 20-credit monthly Cloud grant | Workspace-private projects; Git sync; no top-ups |
| Pro | $25 / month | 100 credits a month plus 5 daily build credits (capped at 30 a month on some regional plans); larger tiers to 10,000 credits | $250 a year on annual billing; rollover; top-ups; custom domains |
| Business | $50 / month | 100 credits a month plus 5 daily build credits (capped at 30 a month on some regional plans) | Adds SSO, internal publishing, security centre; each credit carries a higher dollar value |
| Enterprise | Custom | Volume-based | Platform fee and contract terms |
A Pro credit is not a Business credit
Lovable converts balances at $0.25 a credit on Pro and $0.50 on Business, and says credits are not necessarily equal in value across plans. The same Cloud usage deducts fewer credits on Business.S2S1
Credits keep, but not forever
Unused monthly credits expire two months after issue on monthly plans. Top-ups ($15 per 50 credits on Pro, $30 on Business) last 12 months. Daily credits expire at the end of each day.S1S2
Frozen, not forfeited
After cancelling, plan and rolled-over credits remain usable to the end of the billing period, then freeze, and reactivate if the customer re-subscribes before they expire; top-up credits stay usable until they expire. Fees and credits are not refunded except where the law requires.S1S3S6
| Date | Change | For customers |
|---|---|---|
| 11 Nov 2024 | Paid plans move to monthly message limits; free use cut from 10 edits to 5 messages a day; existing Pro keptS5S29 | Less generous |
| 11 Dec 2024 | Fix requests no longer count toward usage limitsS5 | More generous |
| 24 Apr 2025 | Pro from $25 (from $20), Teams from $30; messages become creditsS16 | Mixed |
| 26 Jun 2025 | Workspace collaboration made free on Free and ProS4 | More generous |
| Jun – Jul 2025 | Agent mode prices requests by work doneS17 | Mixed |
| 11 Aug 2025 | Business plan introduced at $50 with SSO and restricted projects; yearly plans addedS4 | Mixed |
| 1 Sep 2025 | Flat-priced legacy mode scheduled to endS4 | Less predictable |
| 29 Sep 2025 | Cloud and in-app AI launch as a usage-billed layer, with a temporary $25 Cloud allowance (end date later extended three times)S18 | Mixed |
| Nov – Dec 2025 | New projects private by default on every planS12 | More generous |
| 16 Jan 2026 | Credit top-ups introduced; previously the only way to more credits was a higher planS4 | New option, at a premium |
| 13–18 Jun 2026 | One credit balance; Cloud grant becomes 20 creditsS19 | Mixed |
| 31 Jul 2026 | Notice that Free and Pro data may be used for model training from 9 September unless opted outS4S21 | Default changed |
| 11 Aug 2026 | Free fixes limited to ten per accountS4 | Less generous |
| 17–18 Aug 2026 | Credit check-ins; pause instead of failure when credits run outS4 | More protective |
| 21 Sep 2026 | Daily chat allowance; described as temporaryS2 | More generous, for now |
Time-sensitive. Lovable describes the monthly Cloud grant and the current chat pricing as temporary and subject to change; the chat model was stated to run through 31 October 2026. These are not permanent commitments, and some workspaces have not yet moved to the unified balance. Lovable’s pricing page and documentation disagree on some smaller grants; those are omitted here.S2S11
07Ownership and portability
Code portability is strong. Platform dependency is the real question.
Lovable is not accurately described as code lock-in. The dependency that existed sat in the managed backend, and it has since been reduced.
Code portability
- Ownership: as between Lovable and the customer, the customer owns its apps and the AI output generated for it, subject to third-party rights.S6
- Git sync on every plan, including Free; the repository stays with the customer.S22
- Mainstream stack: React and TypeScript web code a hired developer can read and deploy elsewhere; projects created since May 2026 use a Lovable-maintained build package that also works off-platform.S30
- Apps stay published after a downgrade or cancellation.S23
Platform dependency
- Cloud default-on, with no documented way to disconnect it for about nine months.S13
- No direct database credentials on Cloud, and no one-click transfer out.S24
- Managed AI access uses a key Lovable holds; off the platform, the customer needs its own provider account.S12
- Export, pause and removal now exist (July 2026), with manual steps remaining.S10
Until July 2026 Lovable’s documentation said a Cloud-connected project could not be disconnected, and no export was documented — but code remained exportable through Git. That distinction matters, and the current product should not be described as trapping its customers.
What the terms say about customer data
The customer owns its data and output
As between Lovable and the customer, Customer Data, including the apps the customer builds, belongs to the customer, as does AI output generated for it, subject to third-party rights in the underlying models and outputs.S6
A broad, perpetual licence
The customer grants Lovable a worldwide, perpetual, royalty-free licence to use Customer Data for its business purposes, including improving the service and training AI models. Lovable may keep de-identified or aggregated data indefinitely.S6
Free to switch off, on every plan
Customers can opt out of model training and those business uses at any time, free and on any plan, for future use. Since 9 September 2026 Free and Pro data may be used for training unless the customer opts out; Business and Enterprise data is excluded by default.S6S21
This page describes the terms; it does not characterise their legality. The terms quoted are those last updated 28 August 2026 (effective 15 August 2026). Subscription fees and credits are not refundable except where the law requires, and statutory consumer rights are expressly preserved.S6
08Cost predictability
Visible after the fact. Hard to know beforehand.
No estimate
Lovable does not show a credit estimate before a Build mode request runs.S7
Running cost shown
Each message shows its cost as it works and when it finishes; long runs pause at a check-in at 20 credits by default, a configurable pause point rather than a hard cap.S2
No public rate card
Lovable describes what drives Cloud cost but does not publish unit rates per hour, gigabyte or request.S10
Lovable does not publish a complete Cloud rate card; existing customers can see estimates and actual usage inside the product.
Finding: partial transparency. A prospective customer cannot reproduce a live app’s running costs from public unit rates before adopting Cloud. Once inside, Lovable provides estimates, history and category breakdowns, and the exposure is bounded because billing is prepaid rather than open-ended.09Repairs and mitigations
What Lovable fixed, and when.
Lovable’s 2025–2026 record contains a substantial number of repairs. This page credits them in full when describing the customer’s current experience.
Outage credits restored. After a roughly 19-hour outage, Lovable published a post-mortem, apologised, restored credits used during the outage and gave paying users unlimited access the following weekend.S20
RemedyTop-ups allow more credits without changing plan, and reminders before rollover credits expire.S4
FlexibilityCloud export, removal and pause. Application code had always been exportable through Git.S4
ExitCredit check-ins, pause-not-fail when credits run out mid-request, and live per-message cost.S4
Spend controlCloud cost estimates for each database size and a daily free chat allowance (described as temporary).S4
Visibility10CHI pattern analysis
Two signals present, two not established, two mechanisms recorded.
Access that was included becomes metered or paid.
Moderate, narrowLovable publicly described fixes as free in 2024, 2025 and July 2026; in August 2026 it limited the free allowance to ten qualifying fixes per account. The $25 Cloud allowance, labelled temporary from launch and extended three times, became a smaller grant on paid plans at Lovable’s published conversion rate. Against this: private projects and collaboration moved from paid to free.
More yield from existing customers through pricing, packaging or add-ons.
ModerateCredit economics changed repeatedly; the flat-priced mode was scheduled to end; top-ups were introduced at a premium to the entry plan rate; and the unit grew to cover running the app as well as building it. Against this: the Pro price held and Lovable gave up revenue to move Teams customers to a cheaper plan.
Customer-facing withdrawal or migration of a legacy product.
Not establishedPlan succession was ordinary for a fast-moving product, and the direct Supabase path remains available. CHI does not assign this signal.
An explicit link between external cost pressure and a customer charge.
Not establishedPass-through of model or infrastructure costs has not been demonstrated sufficiently. CHI does not assign this signal.
Correction-Cost Transfer
Strongly supported. Added to the CHI Lexicon as a category mechanism. Lovable shows it explicitly in its terms and mitigates it more than the peers examined. Lexicon entry →
Build–Run Pool Coupling
Supported, provisional. A structural Lovable-specific finding. Not added to the Lexicon: one company, limited independent evidence of outages, and a rollout still in progress.
The changing unit of sale
The page’s central finding. Five units of sale since 2024 under a headline Pro price that has not moved since April 2025.
11Tested and not supported
What the evidence did not support.
The billing rule is documented; no evidence of intent was found, and none is suggested here.
Peers charge for corrections too; Lovable is the only one in the set with a documented free-fix allowance.
Code exports through Git on every plan; the historical dependency was in the managed backend.
Rates are not published, but estimates and actual usage are shown in the product and billing is prepaid.
No explicit link between external cost pressure and a price change was demonstrated.
Final disposition
Lovable created very substantial customer value and has unusually strong code portability for an AI app-building platform.
At the same time, the economic relationship became harder to predict as Lovable repeatedly changed the meaning of its usage unit and ultimately combined development consumption with production consumption in one prepaid pool.
Its contractual treatment of unsuccessful AI output provides unusually explicit evidence of Correction-Cost Transfer, although Lovable also provides more mitigation than the peers examined.
Its Cloud history shows both sides of the relationship: a backend that Lovable’s documentation said could not be disconnected for about nine months (application code remained exportable through Git throughout), a temporary allowance whose end date was pushed back three times before it became a smaller grant on paid plans, and no published rate card — followed by export, removal, pause controls, spend visibility and customer protections.
This is not a story of a company simply taking value away. It is a story of a product becoming far more capable while its economic architecture becomes more layered and less intuitively predictable.
12Methodology and sources
How this page was built, and how far it can be relied on.
Evidence base
A twelve-stream research dossier and an independent verification pass, followed by a publication clearance review that read Lovable’s rendered pricing page, its full terms, its documentation, all 129 dated changelog entries from December 2024 to October 2026, and archived copies of its documentation.
Hierarchy
First-party evidence leads: Lovable’s own pricing, terms, documentation, changelog and blog. Journalism and comparator companies’ own pages are second. Review sites and individual accounts are used only to illustrate, never to establish a finding.
Limits
CHI did not use a Lovable account, so in-product rate estimates were not observed directly. Archived pages were sampled, not read exhaustively. The terms are described, not legally interpreted. The Cloud grant and chat pricing are described as temporary; chat pricing is stated to run through 31 October 2026, and the grant may change at any time.
Scope. Security history is recorded in CHI’s research file in three separate classes — weaknesses in apps generated on the platform, a 2026 exposure of public-project chats and code (3 February to 20 April 2026) that Lovable describes in its own published incident post, and criminal misuse of the platform for phishing in 2025. It is not part of this page’s thesis and is not summarised here.
Lovable pricing page, rendered with plan cards and FAQ expanded, 4 October 2026. lovable.dev/pricingFirst-party
Credits and usage: credit types, grants, conversion rates, top-ups, expiry, check-ins and what happens at zero credits. docs.lovable.devFirst-party
Subscription plans: plan tiers, downgrade and cancellation. docs.lovable.devFirst-party
Lovable changelog, 129 dated entries, December 2024 – 1 October 2026; entries cited by date in the text. docs.lovable.dev/changelogFirst-party
Lovable feedback-board changelog, entries of 20 August, 11 November and 11 December 2024. feedback.lovable.devFirst-party
Lovable Terms of Service, last updated 28 August 2026: Credits; No Refunds; AI Output; Rights in Customer Data; Ownership. lovable.dev/termsFirst-party
Build mode: no upfront credit estimate before a request runs. docs.lovable.devFirst-party
Version history: reverted messages still count; reverting restores code, not database data. docs.lovable.devFirst-party
Project chat: ten free fixes, restored after 24 hours, then charged as standard usage. docs.lovable.devFirst-party
Cloud advanced settings: export, pause, removal, estimated monthly Cloud cost, and pausing at low balance. docs.lovable.devFirst-party
Project usage and costs: run credits, usage categories, grants, member limits and unified-billing rollout. docs.lovable.devFirst-party
Lovable Cloud and AI documentation: default enablement, managed AI key, Supabase option, project visibility. docs.lovable.devFirst-party
Lovable Cloud documentation as archived, 29 September 2025 to 11 July 2026: the $25 temporary allowance and its successive end dates, and the answer, until mid-2026, that a Cloud-connected project could not be disconnected. Sep 2025 · Jan 2026 · Mar 2026 · May 2026 · Jun 2026Archived first-party
Lovable FAQ as archived, June–July 2025: “Try to fix” described as free. web.archive.orgArchived first-party
Project chat documentation as archived, 22 July 2026: clicking “Try to fix” does not use credits. web.archive.orgArchived first-party
Lovable 2.0, 24 April 2025. lovable.dev/blogFirst-party
Agent Mode (beta), 30 June 2025, and Agent, 23 July 2025: usage-based pricing and example costs. beta · defaultFirst-party
Lovable Cloud and AI launch, 29 September 2025. lovable.dev/blogFirst-party
We’re simplifying how billing works, 13 June 2026. lovable.dev/blogFirst-party
GitHub outage incident report, January 2025. lovable.dev/blogFirst-party
AI model training opt-out: Free and Pro defaults from 9 September 2026; Business and Enterprise excluded by default. docs.lovable.devFirst-party
GitHub integration: two-way sync, available on all plans. docs.lovable.devFirst-party
Publishing: published apps stay live after a downgrade or cancellation. docs.lovable.devFirst-party
Targeted edits, Supabase integration improvements, and pricing updates, Lovable pricing post dated 11 November 2024 (its web address carries 13 January 2025): Free, Starter, Launch and Scale. lovable.dev/blogFirst-party
Building apps using TanStack Start, 1 June 2026: the default stack for new projects from May 2026. lovable.dev/blogFirst-party
Supabase documentation on Lovable Cloud projects: no service-role keys or direct database URLs. supabase.comInfrastructure partner
“Eight months in, Swedish unicorn Lovable crosses the $100M ARR milestone”, TechCrunch, 23 July 2025, reporting the Teams-to-Pro migration. techcrunch.comJournalism
Comparator pricing changes: v0 token-based pricing (Vercel, 13 May 2025); Replit effort-based pricing and reported cost complaints (Replit; The Register, 18 September 2025); Cursor pricing clarification and refunds (Cursor, 4 July 2025). vercel.com · replit.com · theregister.com · cursor.comComparator first-party and journalism
Review aggregates recorded 4 October 2026: Trustpilot, G2, Product Hunt. trustpilot.com · g2.com · producthunt.comThird-party, illustrative
First-person account of a live app’s backend pausing when workspace credits ran out, 17 September 2026. A single account. substack.comIndividual, illustrative
The complete research dossier, verification report and publication clearance memo, with their evidence ledgers and register of points withheld from publication, are preserved by CHI and are not reproduced here. Lovable and related marks belong to their owners; the name is used only to identify the company, and no endorsement or affiliation is implied. This page is research, not legal or financial advice.
Reading this beside the rest of the index
Every company here is assessed against the same question. Lovable is the one where the price held still and the meter moved.
Read it alongside the methodology, the new Lexicon entry, and the other AI investigations.