DoWebsites verdict: Lovable is a capable AI application builder for teams that can review code and own their GitHub, backend and deployment. Its 2026 unified credit model means build work, hosted backend use and in-app AI can all affect cost.
Price and terms checked 2026-08-11: Free; Pro starts at $25 monthly for 100 credits ($250/year); Business starts at $50 monthly for 100 credits ($500/year). Free/Pro/Business also have 5 daily build credits, with a 30/month cap on Free.
Lovable: the decision in one table
| Build usage | Plan mode costs 1 credit/message; Build mode varies with work complexity |
|---|
| Paid entry | Pro 100 credits: $25 monthly/$250 annually; Business 100: $50 monthly/$500 annually |
|---|
| Run usage | Cloud database, storage, network, compute and realtime draw credits |
|---|
| AI gateway | Model/token/call usage inside deployed apps draws credits separately from building |
|---|
| Git | Two-way GitHub sync supports external code ownership and deployment workflows |
|---|
| Hosting | Lovable hosting/custom domains are available; connected external services can add cost |
|---|
| Production duty | Generated auth, RLS, secrets, payments, accessibility and monitoring require review |
|---|
The old $25/month summary no longer explains cost
Lovable now describes one balance used across building, Cloud and deployed AI features, with usage-specific grants consumed before general credits. Plan mode has a fixed one-credit message cost while Build mode varies with complexity. A realistic budget needs both creation and production usage.
Cloud usage can continue after the build is finished
Database instance time, storage, network, file storage, compute and realtime activity affect run credits. A quiet brochure site and an authenticated application with uploads and realtime events have different cost shapes even if they required similar prompts to build.
GitHub sync is the ownership control
Connect a business-owned GitHub organisation early, keep the main branch protected and review generated diffs like any other code. Git sync reduces builder lock-in, but ownership is not automatic if the repository, deployment or secrets live in a contractor’s personal account.
Lovable Cloud and Supabase are not interchangeable assumptions
Projects can use Lovable’s built-in Cloud or connected services such as Supabase. Inspect the actual project. For Supabase, verify tables, RLS policies, privileged functions, Storage rules and production keys; a working preview does not prove authorisation is correct.
Security work starts where the preview succeeds
Test authentication, role boundaries, direct API access, file uploads, rate limits, secrets, payment webhooks and account deletion. Generated UI validation is not server-side authorisation. Run accessibility, mobile, error-state and data-recovery QA before public launch.
Best fit for Kenyan teams
Lovable fits prototypes, internal tools and custom web apps where speed matters and a technical owner remains involved. International billing, external service costs and payment integrations must be modelled. A fixed-scope brochure site may be cheaper and simpler on a conventional CMS or builder.
Questions buyers actually need answered
What uses Lovable credits?
Building/editing, Lovable Cloud resources and AI model calls made by deployed app features can all consume credits.
Can I own the code?
GitHub sync provides a practical code-ownership path. Use a business-owned repository and deployment account.
Does a published preview prove the app is secure?
No. Authentication, authorisation/RLS, secrets, uploads, payments and APIs require explicit review and adversarial testing.
Are Cloud and AI grants permanent?
Current documentation labels the monthly Cloud and AI grants as temporary and subject to change.
Evidence boundary
This is a buying analysis, not an invented hands-on test. We verified the published offer and policies, separated introductory equivalents from money charged, and discounted claims we could not independently benchmark. Recheck the final checkout and keep an independent backup or export before moving a production service.
Sources checked
