How Much Does Lovable Cost? Credits for a Small Business App

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Much Does Lovable Cost? Credits for a Small Business App.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How Much Does Lovable Cost? Credits for a Small Business App.

A small business app on Lovable typically costs $25 a month on Pro for 100 credits, plus an allowance of 5 free build credits each day. Credits pay for building changes, for the app's hosting and backend (Cloud), and for any AI features running inside the finished app. A modest tool fits in one or two small tiers.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The catch is that the sticker price covers only one of those three uses. Building is where most beginners spend credits, but a published app that serves customers keeps drawing credits every month, so a budget that ignores running costs will be wrong by the second month.

What do Lovable credits pay for?

Lovable credits come from one balance and pay for building, chat, the app's hosting and backend, and AI features in the deployed app, as the documentation says. Think of the balance as a wallet with four pockets, each spent in a different way.

  • Build mode. Each request that changes your app costs credits that depend on the task. The docs give illustrative costs: 0.50 for making a button grey, 0.90 for removing a footer, 1.20 for adding authentication and 2.00 for a landing page with generated images.
  • Plan mode. Planning conversations that never touch your code cost 1 credit per message, plus any research Lovable does while planning. Deep research costs more than 1.
  • Chat. Questions about your app are priced per message, typically a fraction of a credit. They draw first from a daily chat allowance, then from daily build credits, then from general credits.
  • Run credits. The live app's database, storage, network, compute and realtime updates (Cloud), plus model calls made by AI features inside your app. They draw first on the monthly Cloud and AI grants.

Lovable spends usage-specific grants before general credits, which is why the free grants matter for small apps. A quiet internal tool might never touch the general balance for running costs at all.

What does each Lovable plan include?

The Lovable Free plan gives 5 build credits a day, up to 30 a month, while Pro starts at $25 a month for 100 credits and Business at $50 for 100. Both paid plans add code editing and a custom domain.

All figures here are from Lovable's subscription-plans and credits pages, read on 17 November 2026, in dollars.

FreeProBusiness
Monthly plan creditsNoneFrom 100 ($25)From 100 ($50)
Daily build credits5 a day, 30 a month at most5 a day, no monthly cap5 a day, no monthly cap
Cloud grant20 a month20 a month20 a month
AI grant4 a month4 a month4 a month
Connector grant1 a month1 a month1 a month
Code edit and download, custom domainNoYesYes

The Free plan gives you 30 daily build credits a month, in effect six days of 5 credits, which is enough to test an idea but not to ship one. For more on what that allowance can create, see how to use Lovable for free. The Cloud grant of 20 credits and the AI grant of 4 credits are described in the docs as temporary and subject to change, so do not build a business case on them.

If you are choosing between Pro and Business, the difference is governance rather than credits, and the Business versus Pro comparison covers it. This tutorial stays with what the credits themselves buy.

How much does a Lovable credit cost at each tier?

A Lovable credit costs $0.25 on Pro from 100 to 800 credits and $0.24 at 2,000, so the bigger tiers save very little. Pro scales from 100 credits at $25 a month to 10,000 at $2,250 a month, and the table below works out the cost per credit.

Pro tierMonthly pricePer creditAnnual (per month)
100 credits$25$0.25$21
200 credits$50$0.25$42
400 credits$100$0.25$84
800 credits$200$0.25$167
1,200 credits$294about $0.245$245
2,000 credits$480$0.24$400

One-off top-ups on Pro cost $15 for 50 credits, or $0.30 each. That is 20 per cent dearer than the plan rate of $0.25, so a month where you regularly top up is a month to consider the next tier. Top-up credits last twelve months, though, which makes them the safer way to buy for a one-off rush.

Main worked example: a quote-request app for a small manufacturer

Say a manufacturer with fifteen staff wants a tool where customers submit a quote request, sales staff see the requests in a list and an AI step turns messy descriptions into a tidy summary. These numbers are assumptions for illustration, not measurements, and Lovable's real costs vary with how you prompt.

Build phase, month one. Suppose the owner sends about 60 Build-mode requests and 6 Plan-mode messages. Assume the average Build request costs about 1 credit, within the docs' 0.50 to 2.00 range, so building costs about 60 credits. Plan mode adds 6. Chat questions add perhaps 4. Total: roughly 70 credits.

Funding it. The owner builds on ten different days, so daily build credits supply up to 50 of those credits. The remaining 20 or so come from plan credits. A 100-credit Pro plan at $25 therefore covers the build with about 80 credits left over, and the Free plan alone would not.

Run phase, month two onward. The app now has about 30 requests a month. The Cloud work is small, so the 20-credit Cloud grant probably absorbs it. The AI summary calls are the open question. Lovable charges each model call by the model used and the tokens processed, and the docs point to the AI features page for rates rather than giving a flat price. With only 4 AI-grant credits a month, the owner should expect the general balance to cover the rest, and should check the Breakdown tab after the first week of live use.

So month one costs $25 and later months cost $25 plus whatever the running credits come to, with 5 daily credits available on any day of tweaking. Setting aside time costs, that is far below a freelance quote, which is the comparison made in the credits versus freelancer tutorial.

How do you see what Lovable credits are being spent on?

You can see where Lovable credits go in Workspace settings, under Plans and credit usage, and filter the usage details by time range, project and person. A project's usage page shows a total for the range you pick, so check the dropdown for the ranges on offer. New Cloud usage can take up to 24 hours to appear. Cloud usage is grouped into categories such as Database, Network, Storage, Compute and Realtime, with AI usage shown alongside. If Compute shows 1.6, then 1.6 credits of that period's Cloud spend came from compute.

A habit that keeps the bill predictable is a weekly five-minute check:

  1. Open the credit balance and note the remaining plan credits and the renewal date.
  2. Open the project's usage view and read the split between Build, Cloud and AI.
  3. If any one project used more than 5 run credits in the last 7 days, an "Optimize your usage" button appears. Press it and read the suggestions.
  4. Ask Lovable in the project chat what drives your run credit usage and how to lower it. The docs suggest exactly this.

A three-month projection with the totals added up

Turn the quote app into a calendar. These are illustrative assumptions: heavy building in month one, light tweaks after, and the AI step going live in month two.

MonthBuild and plan creditsRun credits beyond grantsCost
1 (build)70 (50 from daily credits, 20 from plan)0$25 plan
2 (AI step live)15about 20 for AI calls (an assumption to test)$25 plan
3 (quiet)8about 20 for AI calls$25 plan

Notice that the plan credits unused in month one (about 80) carry forward to months two and three, keeping their original expiry. By month three the firm holds a healthy surplus and could pause paying, if it did not need the custom domain. The point of the table is the habit, not the numbers: record what you assumed, then replace each assumption with a reading from the Breakdown tab.

A prompt and its credit cost, before and after

The wording of a request changes how much of the app Lovable touches. Here is a before and after for the same job, with a made-up but realistic cost. The credit figures below are illustrative, because Lovable only publishes examples and says actual costs vary.

BEFORE (vague, likely to touch many files)
"Make the quote form better and more professional."
Illustrative result: rewrites layout, adds three fields you did not ask
for, changes fonts. Cost: about 2.0 credits. You then spend 1.5 more
undoing the extra fields.

AFTER (specific)
"On the quote request form, add a required dropdown called 'Product
line' with the options Standard, Custom and Repair. Do not change
anything else on the page."
Illustrative result: one field added, one validation rule. Cost: about
0.9 credits. Nothing to undo.

The same habit applies to Plan mode. If you are unsure what to ask for, spend 1 credit on a planning message, because Plan mode never modifies your code, and then send one precise build request. It is often cheaper than three exploratory builds.

How do you test what the AI inside your Lovable app will cost?

You can test the AI cost of a Lovable app by running twenty realistic inputs through the live feature and dividing the AI credits used by twenty. The running cost most owners cannot guess is the AI inside their own app, since it depends on which model the feature calls and how long the inputs are. The docs say rates follow the underlying provider's costs and point to model tables on the AI features page. Rather than reading tables, measure it.

  1. Write twenty realistic inputs. For the quote app, that is twenty real customer descriptions with names removed, from short ("need 40 brackets") to long, multi-paragraph ones.
  2. Note the AI and general balance before you start, from the credit balance dialog.
  3. Run all twenty through the live feature.
  4. Read the Breakdown tab and divide the AI credits used by twenty. That is your cost per request.
  5. Multiply by the requests you expect each month, then add 30 per cent for the long ones you will meet in real life.

Say the twenty tests used 2 credits. That is 0.1 credits per request, and 300 requests a month would use 30 credits plus a margin of 9. Those would first draw on the 4-credit AI grant and then on your general balance, so you would plan on about 35 credits a month for the AI line. The figures are made up; the method is the point.

Five small apps, five different credit profiles

A stock-count tool for a wholesale distributor

Mostly build credits: ten screens, one barcode field, one export. Almost no AI. After the build the app sits quiet. A single 100-credit Pro month plus daily credits is plausible, then drop to Free daily credits for occasional fixes if the app no longer needs custom domain or code edits. Check that the downgrade does not stop your published app before you cancel.

A booking enquiry page for an HR consultancy

One page, one form, one email notification. Cheap to build, but the confirmation emails need setup; see the Lovable email setup tutorial. Run costs are tiny because traffic is low.

A customer portal for a B2B software reseller

More screens, authentication (1.20 credits in the docs' example) and several database tables. Build cost might be three times the stock tool. Run costs depend on how many customer contacts log in and how large the database instance is. The Manage instance dialog shows an estimated monthly cost for each instance size.

An internal assistant that answers policy questions

This one is AI-heavy. Each question is a model call, charged by model and token count. Long documents pasted into prompts cost more than short ones. Budget the AI line by testing twenty realistic questions in the live app and reading the Breakdown tab afterwards, rather than guessing from price lists.

A weekend landing page for a one-off event

Two credits for a landing page with generated images, a few tweaks, done. Free daily credits may cover it, though a custom domain needs a paid plan.

Which mistakes quietly burn Lovable credits?

Three habits drain a Lovable balance without anyone noticing: repeated vague requests, a heavy database instance left running, and auto top-up left at its default monthly limit.

A pattern worth naming is the rebuild loop. A six-person consultancy asks Lovable to "make it look better" five times, each change touching many components, and spends 12 credits on something a single precise prompt would have done in 2. Specific prompts like "change the submit button to the brand's deep orange and widen the form to 640 pixels" cost less than open-ended ones, though the docs only say costs vary with complexity and scope, so treat the saving as a tendency, not a promise.

A second is leaving a heavy database instance on. Larger instance sizes use more credits and uptime and traffic both count, so a prototype left running on a large instance drains general credits while nobody uses it. Check the estimate in Manage instance after the build ends.

A third is relying on auto top-up without a cap. The defaults are 100 credits per top-up when the balance falls below 25, with a monthly limit of 400 credits. On Pro that is up to $120 a month beyond the plan price, spent without a prompt. Lower the monthly limit to a figure you have chosen.

Should you buy a Lovable top-up or move up a tier?

Buy a Lovable top-up only for a rush you will not repeat, and move up a tier if you run short most months. A top-up costs $0.30 a credit and the plan rate is $0.25. Take a four-person HR consultancy that needs 130 credits in a busy month on a 100-credit plan. Topping up 50 credits costs $15, so the month totals $40. Moving to the 200-credit tier would cost $50 and leave 70 credits spare, which carry forward. If the busy month happens once a quarter, top up. If it happens every month, change tier.

Use this quick test whenever the balance runs low:

  1. Count how many of the last three months you ran short.
  2. If it is one, buy a top-up of the shortfall, rounded up to the nearest 50.
  3. If it is two or three, move up one tier and drop the top-ups.
  4. If you ran short only because of AI calls inside the live app, look at the cost per request first, because a longer prompt inside the app may be the real cause.

If the spreadsheet side of your budgeting is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

What does the Lovable plan price leave out?

The Lovable plan price leaves out four costs: a domain name, email sending, a security review and, largest of all, your own time to test. A domain name is bought separately from the plan, though the plan lets you attach one. Email sending may need a third-party service, depending on how you build it. And an app that stores customer details deserves a proper security pass, covered in the vibe-coded app security checklist, which may mean paying a reviewer.

The credits also have rules on lifespan, which affect how you buy. Monthly plan credits expire two months after issue on monthly billing, daily credits expire at the end of each day and top-ups last twelve months. On annual billing you pay two months less than twelve times the monthly price, but unspent credits do not live forever, so buy the tier you will use.

A simple budget template

Lovable monthly budget (fill in each line)

Plan credits bought:             ____ credits  = $____
Daily build credits expected:    ____ days x 5 = ____ credits
Build requests planned:          ____ x average ____ credits = ____
Plan-mode messages:              ____ x 1 credit = ____
Chat allowance used (estimate):  ____ credits
Cloud (after 20-credit grant):   ____ credits (check Breakdown tab)
AI in the live app (after 4):    ____ credits (test 20 real uses)
Top-up buffer:                   ____ credits x $0.30 = $____

Total credits needed: ____    Credits supplied: ____
If needed > supplied, pick the next tier before topping up.

Filled in (illustrative, month one of the quote app):
Plan credits 100 = $25 | daily 10 days x 5 = 50 | build 60 x 1 = 60
Plan mode 6 | chat 4 | Cloud 0 (grant) | AI 0 | buffer 0
Needed 70, supplied 150. Stay on 100 credits.

If you want a second opinion on what an app should cost to build and run, the quote form comparison with Bolt.new shows another way to measure credits against output.

When credits stop being the right way to buy

Credits suit an app you build and change. If you are paying for the fifth month of tweaks, ask whether a ready-made tool would do the job for less. If your app grows into something customers depend on, price in maintenance, and see how Lovable's costs compare with other builders in Lovable against Replit for a business app.

Plans, grants and rates change, so open the subscription-plans and credits pages in Lovable's docs on the day you buy, and treat every figure above as the picture on 17 November 2026.

If you want help deciding what an app should cost to build and run in your business, I offer one-to-one AI consultations for small businesses.

Lovable pricing: questions small business owners ask

How many credits does one Lovable prompt use?

It varies with the task, so there is no single number. Lovable's docs give illustrative Build-mode examples from 0.50 credits for changing a button colour to 2.00 for a landing page with generated images. Plan mode costs 1 credit per message, and chat is usually a fraction of a credit. The More options menu shows the exact cost of a reply.

Do unused Lovable credits roll over?

Partly. Unused monthly plan credits carry forward each billing cycle while the subscription stays active, and keep their original expiry: two months after issue on monthly plans, or one month after the annual period ends on annual plans. Daily build credits and the monthly Cloud, AI and connector grants do not roll over.

Is hosting included in the Lovable subscription?

Not as a separate bill. Hosting and the built-in backend are paid from the same credit balance, as Run credits. A monthly Cloud grant of 20 credits covers light use. Heavier traffic or a bigger database instance draws on your general credits, so a busy app costs more to run than a quiet one.

What happens when my credits run out mid-month?

You have four options: wait for the next daily credits, buy a one-time top-up, turn on auto top-up, or upgrade the plan. Top-ups cost $15 per 50 credits on Pro and $30 on Business and last 12 months. Cancelling a plan keeps remaining credits until the billing period ends, then the workspace returns to Free.

How much does Lovable cost for a small business app?

It usually starts at $25 a month on Pro for 100 credits, since Free has no custom domain and stops its daily build credits at 30 a month, enough to test an idea but not to ship one. Building a small tool can fit inside Pro, but a live app keeps drawing credits for hosting and any in-app AI, so budget the running cost too. Business is $50 a month for the same 100 credits.

Further reads

Sources: Lovable documentation pages on subscription plans, credits and usage, project usage, Cloud and credit top-ups, read on 17 November 2026.

Ready to put AI on the jobs that eat your week?

No data team or big budget needed. In a 1:1 consultation I show small and medium-sized businesses and self-employed people which AI tools they can use, one workflow at a time.

Book a 1:1 call with me