Lovable pricing 2026: plans, credits and what you really pay

You're reading this on kliv.dev, so yes, we have a horse in this race: Kliv competes with these builders, and we'd like you to try it. Prices and limits come from each vendor's own pages, fetched on November 3, 2026 and linked under Sources.

What the plans cost

The $21/month on the annual card is $250 paid upfront, which works out to about $20.83 a month. Business annual is $500, about $41.67, listed as $42/month. Credits still arrive monthly whichever way you pay. Pay annually if the project will run a year. Pay monthly if you are not sure yet, which, for a first app, you usually are not.

Lovable prices the workspace, not the seat. You can invite as many builders as you want on any plan and the subscription stays the same; everyone just draws from one shared pile of credits. Business adds SSO and role-based access, and keeps workspace data out of model training by default. Pro 100 and Business 100 both come with 100 subscription credits a month, which looks like a wash until you notice that hosting and in-app AI are charged at the same dollar cost on both plans, so they use fewer Business credits. On those two things the Business credit is simply worth more.

What you get for free

Free gives you five build credits a day, capped at 30 a calendar month, so after six days of grants the tap shuts until next month. Pro and Business list the same five daily credits without that standard monthly cap. There is a wrinkle for some regions, though. The pricing FAQ says certain regional paid plans keep the 30-credit cap, and your workspace shows which allowance you are actually on. Trust that number over this page.

Every plan, Free included, also gets a monthly grant of 20 Cloud credits, four AI credits, and one connector credit. Each grant pays for its own kind of usage first, before any general credits are touched. They do not accumulate, and Cloud credits cannot be turned into building credits. Lovable calls these grants temporary, which we read as a hint not to build a long-term budget around them.

Chats and Chat mode are priced separately, per message, with a temporary daily allowance that is larger on Pro and Business. Again, the workspace shows the figure that applies to you.

How far 100 credits go

Not a fixed distance. Build mode charges by the complexity of the request and the work actually completed. Lovable's own examples are 0.5 credits to change a button color and 1.2 to add authentication. Plan mode is one credit per message, plus whatever subagent research it does. So a month of nudging colors around and a month of asking for whole features will drain the same 100 credits at very different speeds.

If you want a number to plan with, assume two build credits per request. That makes 100 subscription credits about 50 requests, before the daily grants help and before anything the running app spends. At five credits per request it is 20. Those are our assumptions, not measured averages, and we would not bet a launch on them. The better forecast is your own. Make your first ten useful changes, add up the credits including the retries, and divide by ten.

What you will probably pay

A top-up is 50 credits for $15 on Pro and $30 on Business, and it lasts 12 months, even on an annual subscription. The arithmetic on repeated top-ups turns quickly. Pro 100 plus two top-ups is $55 for 200 credits; Pro 200 is $50 for the same 200. Buy the 200 tier if you are topping up two months running. Buy a top-up if this month is unusual and next month will not be.

Daily build credits reset at 00:00 UTC and expire the same day. That rewards people who work a little every day and punishes the weekend builder, who gets a handful of days of grants instead of thirty. If your plan is a concentrated push before a launch, treat the subscription credits as the real allowance and count only the daily grants for the days you will actually be at the keyboard.

The running app spends the same credits

Once the grants are used, general credits pay for Cloud resources, in-app AI, and connector usage as well as building. Cloud cost depends on database resources, storage, network transfer, compute, and realtime activity, so a portal that takes large uploads or serves a lot of downloads is a different budget from a quiet prototype. In-app AI depends on which model you picked, how many tokens it chews through, and how often your users call it. None of that shows up in the plan price.

Keep two columns in your spreadsheet, development and customers. Lovable reports them as Build credits and Run credits, both drawn from the same general balance after grants, and the paid plans let you set usage limits and alerts. For a customer portal, feature work goes in the first column; uploads, database activity, and in-app AI calls go in the second. Then you get a monthly total and, more usefully, you can see which column is growing.

When credits expire, and when you can get at the code

On a monthly plan, subscription credits expire two months after they are issued. On an annual plan they last until one month after the billing year ends. Rollover needs an active subscription and does not extend those dates. Top-ups keep their own 12-month clock. A quiet month is not wasted, then, but if your project has long gaps between updates, check the expiry date before buying capacity ahead of time.

Git sync is on every plan. Direct code editing and downloads start at Pro, which makes Pro the entry tier for any web project where you want to touch the code or use your own domain. Lovable builds web apps and does not generate React Native projects. If you need a native mobile app, that is a different route, and the Replit comparison covers it.

And then there's Kliv (the site you're on)

We're smaller and younger than Lovable, and we built Kliv for apps that need sign-in, a database, commerce and email together, the kind of thing a business runs its customers through. Pro is $19/month. If that is the app you are pricing, we'd like you to try us.

Our paid tiers are Pro at $19, Max 5x at $49 and Max 20x at $99, with five and 20 times the Pro usage allowance. Free covers up to 25 apps. Database, authentication, commerce, email, edge functions and hosting are included on every plan; paying adds custom domains, removal of our branding, and capacity. We are also six dollars cheaper than Pro 100, which we mention because we are small enough to care about six dollars. If you are a large team shopping mainly for SSO governance, that entry price is not a reason to switch, and we would rather say so here than have you find out later. For everyone else, the comparison checklist is how we would run the trial: finished work against allowance used.