Lovable credits are one balance that pays for building, Lovable Cloud hosting and backend usage, and AI features inside your app. Pro starts at $25 a month for 100 credits ($21 a month billed yearly), and Lovable's own examples put a small edit at 0.50 to 0.90 credits and a full landing page with images at 2.00. Paid plans also add 5 build credits every day. For a single small app, 100 credits is usually more than enough. For a growing app you work on daily, the question is less the build cost and more the Cloud usage that follows it.
Rather than repeat the plan table, this guide walks through one plausible month on the entry Pro plan, costed with the figures Lovable publishes on lovable.dev/pricing and docs.lovable.dev. Checked Oct 2026. It is a worked estimate, not a measured log: Default Mode charges by task complexity, so your numbers will move with the size of your project.
The rules the month runs on
- Plan credits: 100 a month on the first Pro tier, added to your balance at the start of each cycle.
- Daily build credits: 5 a day on Pro and Business, with no monthly cap. They expire at the end of each day. Lovable notes that some regional plans cap them at 30 a month.
- Monthly grants on every plan: 20 Cloud credits, 4 credits for AI features in your app, 1 connector credit.
- Plan Mode: a flat 1 credit per message. Default Mode: varies with the task.
- Published examples: "Make the button gray" 0.50, "Remove the footer" 0.90, "Add authentication" 1.20, "Build a landing page with images" 2.00. Lovable calls these illustrative.
The project for the month is a booking page for a small yoga studio: a landing page, a class schedule, a booking form that saves to a database, and a login for the owner to see bookings.
Week one, the first version for about 10 credits
Day one is the big prompt. A landing page with generated images is Lovable's 2.00-credit example, and a page with a schedule section lands near that, so call it 2 credits. The next few days are the usual round of changes: new headline, different photos, a tighter schedule layout, a colour that matches the studio's sign. Eight edits at 0.50 to 0.90 credits each is 4 to 7 credits.
Spend two or three Plan Mode messages agreeing how bookings should work before you build it. At 1 credit each, that is cheap insurance against an expensive wrong turn. If you build on five days this week and use your 5 daily credits first, almost none of this touches the 100 plan credits.
Week two, the backend for another 10 to 15
Now the booking form has to save something. Turning on Lovable Cloud and asking for a bookings table is a mid-sized task. The owner login is Lovable's 1.20-credit authentication example. A protected page listing bookings, a filter by class and a confirmation email request are a handful more mid-sized edits at 1 to 2 credits each.
Then come the fixes. A date shows in the wrong timezone, the form allows double bookings, the list does not refresh. Debugging is where credit use is least predictable, because Default Mode charges by complexity and a fix may take two or three tries. Budget 10 to 15 credits for the week, and expect the daily credits to cover a good part of it.
Week three, one bigger feature
Suppose the owner asks for class capacity limits and a waitlist when a class is full. Features that touch the database, the form and the owner page at once cost more per message, and they often need a Plan Mode round first. Fifteen to 20 credits for the week is a reasonable guess. This is the week that usually reaches into the 100 plan credits.
Week four, publishing, the domain and the in-app AI
Pro is what lets you publish publicly, connect your own domain and remove the Edit with Lovable badge, so this week is about launch rather than building. A last polish round might be 5 credits.
If you add an AI feature inside the app, say a chat box that answers questions about classes, its usage draws on the 4 monthly AI credits first and then on your balance. Visitors browsing the schedule and making bookings draw on the 20 monthly Cloud credits. Lovable says most small apps stay inside those grants, and a studio site with modest traffic should.
Totting up the month
On these estimates the month costs roughly 40 to 55 credits of building. If you built on most days and spent your daily credits first, the draw on the 100 plan credits could be well under half of that. So the entry Pro tier covers this project with room to spare, and the $25 mostly pays for public publishing and the domain.
The picture changes in two cases. A larger app with many screens and frequent rework can use several hundred credits a month, which is why the Pro ladder runs from 100 credits at $25 to 200 at $50, 400 at $100, 800 at $200 and on up to 10,000 at $2,250. And an app that gets real traffic starts spending Cloud usage from the same pool.
What happens to credits you do not use
- Monthly plan credits expire two months after they are issued, so one quiet month carries over, but not two.
- On yearly billing, plan credits expire one month after the annual period ends.
- Daily build credits expire at the end of each day and never roll over.
- Top-up credits, available on Pro and Business, last 12 months from purchase. Free has no top-ups or rollovers.
- If you cancel, you keep your credits until the billing period ends and then drop to Free. Credits are not refundable.
Cloud usage is the line to watch
Lovable Cloud charges for database server and storage, network, file storage, compute and realtime messages. More visitors, more stored files and more backend code running all cost more. There is no fixed price per request, but paid users can resize the database and see an estimated monthly cost for each size before switching. Check the usage view once a month after launch, because a busy month can quietly eat the credits you planned to build with.
When Business or a top-up is worth it
Business starts at $50 a month for 100 credits. Lovable's docs value a Pro credit at $0.25 and a Business credit at $0.50, and they say this does not make Cloud or AI usage cheaper on Business: each Business credit is worth more dollars, so fewer are deducted. In other words, you pay double per credit for governance, not for cheaper building. That includes single sign-on, role-based access, workspace data excluded from model training by default, password-protected preview links and priority support. Pick it when a company needs those controls.
A top-up is the better move when one unusual month runs out, such as a launch or a large rebuild. If you top up two months in a row, move up a Pro tier instead.
The same month on VibeDream and two rivals
For comparison, and we make VibeDream: All Access Mini is $49 a month for 60 credits, with no free plan and no daily credits. Putting the app online costs 5 credits per publish, and hosting is included under a fair usage policy instead of drawing on credits as traffic grows. Built-in login and database now work with one tap, so an owner login for a booking app no longer needs extra setup. VibeDream plans are on the pricing page.
Base44 and Bolt.new price differently again: Base44 splits message credits from integration credits, and Bolt.new counts tokens. Our Base44 pricing and Bolt.new pricing guides work through those meters.