Lovable hosting cost: build a budget for the whole app

First, identify what you are hosting

Lovable provides hosting and a built-in Cloud backend with database, authentication, storage and functions. An app may instead connect to an external backend. Check your project's actual setup before assuming you need a separate Supabase subscription or that every service is included in one bill.

Write down the critical user journey. For a course directory, that might be opening a page and following a course link. For a member portal, it could include signing in, retrieving a record and uploading a file. For an AI assistant, add the model request and response. This simple map helps you identify which services need a cost line.

Keep four budget lines separate

Avoid double-counting usage as an external invoice. Equally, an independently billed provider cost does not disappear because the frontend was built in Lovable. Use your actual setup and billing records to fill in these four lines.

• Subscription: record the actual plan, currency, renewal date and billing period shown in your account.
• Usage: record workspace and production project consumption. Separate included credits or grants from additional purchases.
• Domain: record the registration or renewal charge and due date. An annual payment is a cash expense when it renews, even if you divide it by 12 for monthly planning.
• External services: record any separately billed database, email, payment service or external model API, using that provider’s bills and limits.

An illustrative monthly budget

Imagine a planning worksheet with 30 budget units for the subscription, 8 for additional usage, 12 for external services and a domain that costs 24 units annually. The monthly planning total is:

30 + 8 + 12 + (24 / 12) = 52 budget units.

These numbers are invented solely to demonstrate the arithmetic. They are not current prices, credits, a recommendation or a Lovable allowance. Replace them with verified amounts in the same currency.

For a stress case, increase additional usage from 8 to 20 units. The monthly total becomes 64 units. Ask what would drive that change: more uploads, repeated AI requests or background work? Keep the assumptions alongside the calculation.

Record the actual invoice beside the estimate. A forecast describes a possibility; a bill records a charge. Neither proves that users completed the task they came to do.

Auto top-up and usage limits do different jobs

Auto top-up purchases credits when the configured threshold is reached, subject to a monthly top-up limit. That limit resets on the first calendar day of each month at 00:00 UTC, independently of the subscription billing cycle. Turning auto top-up off prevents future automatic purchases; it does not refund past purchases. Read the costs displayed in your account.

Usage rules can notify, block activity or do both. A low-balance alert only notifies. Check each rule’s scope and credit type: member limits apply to Build activity, while project and workspace rules can cover broader usage. Blocking can interrupt building or running features. Paid-plan owners and admins can configure these controls.

A top-up limit is not a cap on every company expense. Keep subscription, domain and external-service costs in the budget. Make the tradeoff between service continuity and spending deliberately: an alert does not necessarily block charges. Before enabling a blocking rule, answer these questions:

• Which activity stops when the limit is reached?
• What will the customer see?
• Who receives the alert and decides what happens next?

What a custom domain adds

Connecting a new custom domain requires a paid plan. You can connect an existing domain or buy one through Lovable’s domain flow. Already-connected domains can keep working after a downgrade. Confirm the actual renewal price and ownership details; an introductory price is not necessarily the renewal price.

Keep the registrar, renewal date, primary hostname and responsible person recorded, even if you move the app later.

Should you move to external hosting?

Lovable’s deployment documentation describes options that include moving the frontend while retaining the backend, migrating backend services, and a broader migration. Moving the frontend alone does not replace the database, AI services or connectors it depends on.

Compare the whole operating plan: setup work, backups, monitoring, support and rollback, as well as the hosting quote. Test a copy with representative, non-sensitive data before making a decision. This article has not tested a migration or benchmarked hosting providers. Use the official deployment, hosting and ownership guide linked above to check the scope of a proposed move.

A useful check before launch

Use this checklist to turn the estimate into an operating plan. Continue to the Lovable Cloud pricing guide in the related guides below for the Cloud-specific part of the budget.

Plan the next step: Growth Tools launch costs, approvals and useful measurements

• Confirm the production project and the services it uses.
• Capture plan prices, currencies, renewal dates and current usage.
• Check the scope and consequences of each spending control.
• Test the main user journey on mobile and desktop.
• Record how to recover if an essential service stops.
• Review actual usage after launch before expanding the budget.