Lovable
lovable.dev · 2 records in Coding subscriptions, Compute · JSON
Records 2
- caveatLovable (Coding subscriptions)
Coding subscriptionsfree tieridentity emailno cardlimit volume-quotaevidence documentedstale on 2026-12-05
- caveatLovable (Compute)
Computefree tieridentity emailcard?limit request-rateevidence documentedstale on 2026-12-05
Lovable (Coding subscriptions)
Coding subscriptions- Free allowance
- Free: 5 build credits a day, capped at 30 a month, so the cap is spent in the first 6 days of each calendar month; Pro starts at USD 25 a month for 100 credits, plus 5 daily build credits with no monthly cap
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- volume-quotaFree: 5 build credits a day, 30 a month; the monthly cap is reached on the sixth day and daily credits resume on the 1st at 00:00 UTC
- Evidence
- documented24 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | Free: 5 build credits a day, capped at 30 a month, so the cap is spent in the first 6 days of each calendar month; Pro starts at USD 25 a month for 100 credits, plus 5 daily build credits with no monthly cap unit credits; metered on request-count; a credit is not a fixed unit of work: each message is charged on the work done, so the 30 free credits buy a variable number of messages |
|---|---|
| Price | none stated |
| Limits |
the 30-credit Free cap binds first; the API gate is a plan gate, and the API itself spends no build credits |
| Binding | volume-quota 30 build credits a month on Free, spent in the first 6 days of the month |
| Identity | email sign-up offers email, Google, GitHub or Apple and opens a Free personal workspace; the sign-up page shows an account form with an Email option and no card or phone field. Paid plans are billed through Stripe; what checkout asks for is unverified: behind a sign-up |
| Egress | not published on the pages read: no egress term was found, so nothing is asserted |
| Per-object cap | not applicable: the plan meters credits, not stored bytes |
| Retention | not applicable: no stored bytes are metered |
| Interface | rest, git a web app where a prompt builds a project. Git sync with GitHub, GitLab and Bitbucket is on every plan. The Lovable REST API at api.lovable.dev/v1 (Lovable-API-Key header, keys start lov_) manages and deploys existing projects, needs a Business or higher plan, and spends no build credits. AI project creation and editing run through the Lovable MCP server, which is open to every plan and spends the same credits as the web app |
| Tooling | hosted service with a web editor; no local client is documented. An MCP client such as Claude or Cursor can drive project creation and messages through the MCP server on any plan |
| Composes with | Pro, USD 25 a month for 100 credits (USD 250 a year), adds code editing and download, custom domains and credit rollover; the Lovable API needs Business, whose 100-credit tier is USD 50 a month. Plan mode costs 1 credit a message; Build mode messages are priced by the work done, from 0.50 credits for a one-line style change to 1.70 for a landing page with 3 generated images. Chat messages usually cost a fraction of a credit and draw first on a separate daily chat allowance of unpublished size |
| Reliability | the chat allowance and the monthly Cloud and AI grants are stated as temporary offers subject to change; the chat pricing is stated to apply through 2026-10-31, a date that had passed on the day read, and whether it was extended is unverified |
| Notes | A hosted AI app builder rather than a coding-agent subscription: the unit is a credit, charged per message. The same vendor's Free plan, Cloud grant and sign-up are also recorded under compute/lovable. Monthly Cloud (20 credits), AI (4 credits) and connector (1 credit) grants come on top of build credits on every plan. |
| Evidence note | documented plan table, credit rules, API and MCP terms are quoted from first-party pages read on 2026-11-02; the size of the daily chat allowance is not published, and the checkout requirements of Pro were not seen |
| Parsed numbers |
|
Evidence 24
| date | source | what it proved |
|---|---|---|
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | Free gets 5 daily build credits capped at 30 a month; Pro and Business get 5 per day |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | the Free monthly cap of 30 is spent in the first 6 days of each calendar month |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | Free has no subscription credits; Pro and Business start at 100 a month |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | the Pro tier with 100 monthly credits is USD 25 billed monthly or USD 250 billed annually |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | Pro is sold in credit tiers from 100 credits a month upward |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | Free has no code editing; Pro and above can edit code |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | Git sync is included on every plan, Free included |
| 2026-11-02 | docs.lovable.dev/introduction/subscription-plans | the Lovable API is included from Business upward and not on Free or Pro |
| 2026-11-02 | docs.lovable.dev/introduction/credits-and-usage | a Plan mode message costs 1 credit plus any subagent research |
| 2026-11-02 | docs.lovable.dev/introduction/credits-and-usage | a Build mode message has no fixed credit cost |
| 2026-11-02 | lovable.dev/pricing | a one-line style change cost 0.50 credits in the published examples |
| 2026-11-02 | lovable.dev/pricing | a landing page with 3 generated images cost 1.70 credits in the published examples |
| 2026-11-02 | docs.lovable.dev/introduction/credits-and-usage | a chat message costs typically a fraction of a credit |
| 2026-11-02 | docs.lovable.dev/introduction/credits-and-usage | the chat pricing model and daily chat allowance are stated as a temporary offer through 2026-10-31 |
| 2026-11-02 | docs.lovable.dev/integrations/lovable-api | API keys need a Business or Enterprise workspace and an owner or admin role |
| 2026-11-02 | docs.lovable.dev/integrations/lovable-api | the REST API manages and deploys existing projects and spends no AI build credits |
| 2026-11-02 | docs.lovable.dev/api-reference/introduction | every API key has its own rate limit |
| 2026-11-02 | docs.lovable.dev/api-reference/introduction | the API needs a verified account email |
| 2026-11-02 | docs.lovable.dev/features/api-keys | Free and Pro workspaces cannot create workspace API keys |
| 2026-11-02 | docs.lovable.dev/integrations/lovable-mcp-server | the MCP server, which can create and edit projects, is open to every plan |
| 2026-11-02 | docs.lovable.dev/integrations/lovable-mcp-server | building through the MCP server spends the same credits |
| 2026-11-02 | docs.lovable.dev/introduction/getting-started | sign-up takes an email, Google, GitHub or Apple login and opens a Free workspace |
| 2026-11-02 | lovable.dev/signup | the sign-up page shows an account form with an Email option and no card or phone field |
| 2026-11-04 | docs.lovable.dev/introduction/credits-and-usage | Free still gets 5 daily build credits capped at 30 a month |
Unknown values 1
- egress metered: egress metering was not published
Lovable (Compute)
Compute- Free allowance
- Lovable Free: "Daily build credits 5/day, 30/month", "Monthly Cloud grant 20 credits", "Monthly AI grant 4 credits", quoted; the footnote says "on Free, you receive daily build credits for the first 6 days each month (6 x 5 = 30), then none until the next month starts"
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailcard unknown, phone unknown
- Binding limit
- request-ratethe 30-credit monthly cap exhausts on the sixth day of the month, so two thirds of every month has zero build capacity on the free plan.
- Evidence
- documented10 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | Lovable Free: "Daily build credits 5/day, 30/month", "Monthly Cloud grant 20 credits", "Monthly AI grant 4 credits", quoted; the footnote says "on Free, you receive daily build credits for the first 6 days each month (6 x 5 = 30), then none until the next month starts" unit credits; metered on wall-clock; recurring-allowance |
|---|---|
| Price | none stated |
| Limits |
|
| Identity | email the sign-up page shows 'Create your account' with an Email field; no card or phone field is shown on that page, and any later step is unverified |
| Egress | not stated |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | the 20-credit monthly Cloud grant hosts a small app and its backend after the 30 monthly build credits are gone; on Free, code cannot be edited or downloaded inside Lovable, but Git sync with GitHub, GitLab and Bitbucket is included, so the code moves through a repository |
| Reliability | no reliability event recorded |
| Notes | The credit is not a token. The pricing page's own examples price a one-line style change at 0.50 and a landing page with three generated images at 1.70, so the unit varies by task. A daily chat allowance also exists with no published number. |
| Parsed numbers |
|
Evidence 10
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | docs.lovable.dev/introduction/subscription-plans | the Free column gives 5 daily build credits capped at 30 a month, a 20-credit monthly Cloud grant and a 4-credit monthly AI grant, quoted |
| 2026-10-22 | docs.lovable.dev/introduction/credits-and-usage | one credit balance covers build, chat, Cloud hosting with database, network, storage and compute, and AI gateway calls in deployed apps, quoted |
| 2026-10-22 | lovable.dev/pricing | the pricing page prices single messages at 0.50 to 1.70 credits by example, so the 30 monthly free credits buy roughly 18 to 60 build messages |
| 2026-10-22 | docs.lovable.dev/introduction/subscription-plans | probe GET returned status 200, 456647 bytes, sha256 a336e9b45071de52ed367c54abb3a21be3f189b82f5dfc7b67f843b964299233, no challenge detected, at 2026-10-22T15:23:48Z |
| 2026-10-30 | docs.lovable.dev/introduction/subscription-plans | the Free plan's allowance is denominated in credits: 5 build credits a day capped at 30 a month |
| 2026-10-30 | lovable.dev/signup | the sign-up form asks for an email address |
| 2026-10-30 | docs.lovable.dev/introduction/subscription-plans | the Free plan has no code editing and no code download, while Git sync is included on every plan |
| 2026-10-30 | docs.lovable.dev/introduction/subscription-plans | the Free plan still grants 5 build credits a day for the first 6 days of each month, 30 in total, with 20 Cloud and 4 AI credits a month |
| 2026-11-03 | docs.lovable.dev/introduction/subscription-plans | the Free plan still grants 5 build credits a day up to 30 a month, exhausted on the sixth day |
| 2026-11-04 | docs.lovable.dev/introduction/subscription-plans | the Free plan still grants 5 daily build credits capped at 30 a month |
More fields 1
| facets | {"class": "perpetual-allowance","free_tier_kind": "recurring-allowance","shape": {"vcpu": null,"ram_gib": null,"gpu_class": null,"gpu_count": null}} |
|---|
Unknown values 7
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- retention stated: the field does not apply to this kind of offer
- tooling: a source was read and is silent on this field