Credit Cost Estimator
A rough lantern in the dark. Estimate how many Lovable credits a stretch of work or a month of running The Spore Oracle is likely to consume.
One-off build actions
Enter how many of each you expect. Ranges reflect simple vs. complex work.
New page or route
A fresh route with layout, content and basic styling.
2–6 credits each
Content / copy edits
Small text, image or layout tweaks on existing pages.
0.5–2 credits each
Design polish pass
Refining spacing, typography, colour or responsive behaviour.
1–4 credits each
New interactive feature
E.g. a form, gallery, filter or member-only widget.
4–12 credits each
AI-powered feature
Anything calling the AI Gateway (chat, summaries, generation).
6–18 credits each
Database / schema change
New table, migration, RLS policy or backend function.
2–6 credits each
Bug fix or debugging session
Triage, reproduce and fix. Larger issues land at the top end.
1–5 credits each
Security scan & fixes
Running a scan and resolving the findings it surfaces.
2–6 credits each
Publish / deploy
Publishing is free; included here only for planning clarity.
0 credits each
Ongoing monthly runtime
Cloud and AI Gateway usage is deducted from your credit balance beyond the free allowance.
Lovable Cloud (database, storage, functions)
Light traffic typically stays within the free monthly allowance.
0–15 credits / month
AI Gateway usage
Depends on the model and how often members use AI features.
0–25 credits / month
Your forecast
Estimates are indicative only. Actual credit consumption depends on task complexity, number of iterations and the AI models used. Plan-mode messages cost 1 credit each. Publishing itself is free. Free monthly allowances (Cloud + AI Gateway) are applied before any of the above is charged.