Publishing a Lovable app takes one click, and the paid plans that add a custom domain start at $25 a month at the time of checking (November 2026), according to Lovable's subscription plans. The gap between that first publish and a product customers can find, trust and rely on is where most of the real work sits. This guide works through it in the order the decisions usually come up for a UK business: hosting and plan, domain, code ownership, search and AI visibility, speed, the Supabase backend, data location and cookies, cost and scale.
- Publishing works on every Lovable plan; a custom domain needs Pro (from $25 a month) or above.
- Lovable sends other connected domains to your primary one with a temporary 302 redirect, so canonical tags and the sitemap must name the primary domain.
- Apps created from 13 May 2026 render on the server; older apps serve pre-rendered pages only to verified crawlers.
- Supabase's Free Plan has no automatic daily backups, and its built-in email provider sends 2 auth emails an hour.
- Pick a Europe backend region before enabling Lovable Cloud: it cannot be changed later.
How does Lovable hosting work?
Lovable hosts every published app for you at an address ending in lovable.app, with HTTPS included and no servers to set up. Publishing works on all plans; what you pay for is your own domain and team features.
One detail catches people out. In the words of Lovable's publishing documentation, "the live site keeps showing the version you published, and later changes stay off it until you publish again." That gives you a release step, but someone has to decide when a change is ready and check the live site afterwards. The Publish dialog itself uses no credits; publishing from the project chat does.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Publish to lovable.app | Yes | Yes | Yes |
| Custom domains | No | Yes | Yes |
| Single sign-on (SSO) | No | No | Yes |
| Monthly price, from | $0 | $25 | $50 |
Sources: Lovable, Subscription plans, checked November 2026; Lovable, Launch on a custom domain, 2026
For most small businesses, Lovable's own hosting is the right production choice. Lovable's publishing always deploys to its own hosting, so moving elsewhere is a developer job, worth doing only for a specific need such as edge logic or an existing deployment pipeline. Because the code can sync to your own repository, it stays an ordinary project that any React development team can build and deploy.
How do you connect a custom domain to a Lovable app?
Move to a paid plan, add the domain in the project's domain settings, then create the A record and the _lovable TXT verification record that Lovable shows you at your registrar. Lovable issues the SSL certificate automatically once DNS resolves.
- Choose one primary address: www or the bare domain
- Add the domain in Lovable and copy its records
- Create the A and TXT records (DNS only on Cloudflare)
- Wait for Live status and the SSL certificate
- Set it as primary and update sign-in redirect URLs
- 72 hours is the longest DNS changes may take to propagate, though most are live within a few hours
- 300 seconds is the minimum TTL for records you add in Lovable
- 1 hour is the usual setup time for a domain bought through Lovable
- 1 domain can be primary at a time; the others redirect to it
Sources: Lovable, Custom domains, 2026; Lovable, Launch on a custom domain, 2026
The redirect type matters for search. Lovable's custom domain documentation says it "uses a 302 temporary redirect for page visits" to the primary domain. Google's guidance on redirects and Google Search says that for temporary redirects the indexing pipeline "doesn't use the redirect as a signal that the redirect target should be canonical." So the other signals have to agree: canonical tags, sitemap URLs, internal links and social profiles should all use the primary domain, never the lovable.app address.
Then check sign-in. For apps on the built-in backend, Lovable adds custom domains to the authentication redirect list automatically. If you use your own Supabase project, Google sign-in with your own OAuth credentials, or another sign-in provider, add the new address yourself, along with payment webhooks and email templates. Otherwise password reset and magic-link emails that worked in the preview will fail on launch day.
Do you own the code, and why does it matter?
You own it once Git sync is on: Lovable commits every change to a repository you own on GitHub, GitLab or Bitbucket, with two-way sync on one branch. Turn it on before launch.
The repository gives you a full history of every change, a copy of the code you control and an exit plan. A developer, or a coding agent working alongside one, can pick up from where you are rather than starting again. Our guides to using Claude Code in a business and Codex vs Claude Code cover how that hand-over usually works.
Is a Lovable app good for SEO?
Technically, yes. Lovable's SEO and AI search documentation says new apps created from May 13, 2026 "use TanStack Start with server-side rendering (SSR)", while older React and Vite apps get on-request pre-rendering that "is only served to verified crawlers." Rendering makes pages eligible to rank; content and metadata decide whether they do.
| Visitor | New apps (TanStack Start) | Older apps (React + Vite) |
|---|---|---|
| People in a browser | Yes, rendered on the server | No, built in the browser |
| Google and Bing | Yes | Yes, pre-rendered on request |
| Verified AI search crawlers | Yes | Yes, pre-rendered on request |
| Unverified bots and tools | Yes | No |
Source: Lovable, SEO and AI search, 2026
That still matters because, as Google's JavaScript SEO basics put it, "not all bots can run JavaScript", and "server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers." Rendering is only the start, though. Lovable says it "creates a robots.txt with every new project, but not always a sitemap, and the starting metadata is generic." The practical list:
| SEO item | What to do | Why |
|---|---|---|
| Titles and descriptions | Write a unique title and meta description for every important page | Generic defaults look like duplicates |
| Sitemap | Publish a sitemap.xml with absolute URLs on the primary domain | Google asks for fully qualified URLs and caps one file at 50,000 URLs |
| Search Console | Verify the custom domain and submit the sitemap after publishing | Google reads the live site, not the preview |
| Share images | Give each key page its own 1200 x 630 Open Graph image | Social platforms read tags from the HTML |
| Content and headings | One clear H1 per page, descriptive H2s and real text | Search and AI answer engines quote what they can read |
| Structured data | Add markup only where it matches visible content | Mismatched markup is ignored |
Sources: Lovable, SEO and AI search; Google Search Central, Build and submit a sitemap
Run Lovable's SEO and AI search review after the domain goes live, because some checks only run against the live site, and run it again whenever you change the primary domain. It can connect Google Search Console, verify the site and submit the sitemap for you. The bigger limit is usually content: an app with a sign-in screen and a pricing page gives search engines very little to rank, so plan the service, comparison and guide pages your customers actually search for. That is the part an SEO specialist adds to a Lovable build.
How fast does a Lovable app need to be?
Fast enough to pass Google's Core Web Vitals at the 75th percentile of page loads: the largest element painted within 2.5 seconds, responses to taps and clicks within 200 milliseconds, and almost no layout shift.
- 2.5 s or less for Largest Contentful Paint (LCP)
- 200 ms or less for Interaction to Next Paint (INP)
- 0.1 or less for Cumulative Layout Shift (CLS)
Source: Google web.dev, Web Vitals, 2026
Lovable notes that its SEO review "no longer runs Lighthouse audits", so test key pages in PageSpeed Insights yourself. The common fixes in Lovable apps are small: compress and size hero images, reserve space for images and embeds so the layout does not jump, avoid loading every database row on first paint, and delay heavy third-party scripts such as chat widgets until they are needed.
Is your Supabase backend ready for production?
Not by default. Supabase's production checklist expects Row Level Security on every exposed table, your own email sender, reviewed rate limits and a backup plan, and the Free Plan has no automatic daily backups.
Lovable's built-in backend, Cloud, "utilizes Supabase's open-source foundation", and you can connect a Supabase project of your own instead. Either way, the items that matter most are:
- Row Level Security on every table in an exposed schema, with policies tested as different users.
- Your own SMTP sender for sign-up and password reset. Supabase's auth rate limits allow "2 emails per hour with the built-in email provider."
- Authentication rate limits reviewed for your expected traffic.
- Backups you can restore, plus point-in-time recovery if losing a day of data would hurt.
- No secret keys in the front end; anything privileged runs in a server function.
Free projects get no automatic daily backups; point-in-time recovery is an add-on from Pro.
| Supabase plan | Daily backups kept |
|---|---|
| Free | |
| Pro | |
| Team | |
| Enterprise |
Sources: Supabase, Database backups, checked November 2026; Supabase, Pricing, checked November 2026
If you run your own Supabase project, the Supabase pricing page also notes that "free projects are paused after 1 week of inactivity" and include a 500 MB database, which is fine for a prototype and wrong for a launch. Our Supabase and Lovable security checklist covers RLS testing in depth, and a vibe-coded app security audit is the formal version before you take payments.
Where is your data stored, and what do UK GDPR and PECR require?
For a UK business, keep the backend close to your users: the Europe region on Lovable Cloud, or London on your own Supabase project. Then set up cookie consent that matches PECR before you add analytics or advertising tags.
Lovable's Cloud documentation says "projects use one of three regions: Americas, Europe, or Asia Pacific", and that you cannot change a project's region after the backend is enabled. Supabase lists "West Europe (London), eu-west-2" as a specific region. Under UK GDPR, the ICO calls sending personal information to a separate organisation outside the UK a restricted transfer, so record where the data lives in your privacy notice and check which transfer route applies.
Cookies, pixels and local storage fall under PECR. The ICO's guidance on storage and access technologies says "there are five exceptions" to the consent rule, and advertising is never one of them.
| What the app stores | Consent needed? | Condition |
|---|---|---|
| Sign-in session cookies | No | Strictly necessary for the service the user asked for |
| Usage statistics to improve the app | No, within the exception | Statistics is the sole purpose, with clear information and a simple, free way to object |
| Theme or layout preferences | No, within the exception | Covered by the appearance exception |
| Advertising pixels and remarketing tags | Yes | Online advertising purposes are not exempt |
These checks are easier with someone on UK hours who knows what the ICO expects. Circlemount is based in Telford, Shropshire, where Marcus (founder) and a team of 12 specialists work on Lovable apps; if you want to meet in person or work remotely with a UK team, see our pages for Telford, Birmingham, Coventry and London.
How much does it cost to run a Lovable app in production?
At the time of checking (November 2026), Lovable Pro starts at $25 a month and Business at $50, and your own Supabase project adds a Pro plan "from $25/month". Hosting and the built-in backend draw on the same credit balance you build with.
Monthly billing in US dollars; annual billing gives two months free.
| Plan | From – To |
|---|---|
| Pro | |
| Business |
Lovable's plans and credits page explains that Cloud usage "draws from your available credits, starting with any monthly Cloud grant included in your plan", which is 20 credits a month on Free, Pro and Business. The publishing docs add that apps using the built-in backend or AI features "do need available credits to serve requests." In plain terms, an empty balance is a production risk, so set a usage alert and keep a buffer.
What happens when a Lovable app needs to scale?
Most Lovable apps never hit a hard platform limit. What they hit first is the cost and slowness of code written for ten users, and the fixes are unglamorous:
- Add database indexes for the columns your screens filter and sort by.
- Paginate lists instead of loading every row.
- Move heavy work, such as sending emails, generating PDFs or calling AI models, into server functions or background jobs.
- Cache data that rarely changes.
- Set usage alerts on Supabase, Lovable and any AI provider, so a spike becomes a message, not a bill.
The other scaling problem is the codebase. After hundreds of prompts, a project can contain duplicated components and tables nobody remembers adding. A short clean-up in the synced repository, the kind of work covered by our fix a vibe-coded app service, usually makes the next six months of prompting faster and safer.
What is a sensible launch checklist?
A Lovable app is ready for real customers when these six things are true:
- Security scan clean and RLS tested by hand
- Primary domain live, with auth redirect URLs updated
- Code syncing to your own Git account
- Unique titles, share images and a submitted sitemap
- Sign-up, reset and payments tested on the live domain
- Backups, usage alerts and error alerts owned by someone
If you are still choosing a platform, see Lovable vs Bolt vs Replit vs Cursor, and for the bigger picture, what vibe coding is and where it breaks. If the app is still an idea, app MVP development covers building it production-ready from the start, and a Lovable developer can take an existing project through this list with you.
Frequently asked questions
Can I use my own domain with a Lovable app?
Yes, on a paid plan. Add the domain in the project settings, create the A and TXT records Lovable shows at your registrar, and set it as primary. The built-in backend adds it to sign-in redirect URLs automatically; with your own Supabase project or OAuth credentials, add it yourself, plus payment webhooks.
Do changes in Lovable go live automatically?
No. The live site keeps showing the version you last published, and later edits stay off it until you publish again. Treat each publish as a release: check the preview, publish, then test the key journeys such as sign-up, login and checkout on the live domain straight away.
Is Lovable good for SEO?
It can be. Apps created from 13 May 2026 use TanStack Start and render on the server, and older apps serve pre-rendered pages to verified crawlers. You still need unique titles and descriptions, a valid sitemap, share images, clear headings and real content, plus Google Search Console set up on your domain.
Can I host a Lovable app somewhere else?
Lovable's publishing always deploys to Lovable's own hosting. Because the project can sync two-way with GitHub, GitLab or Bitbucket, a developer can also build and deploy the code elsewhere. That is worth doing only for a specific need, as you then manage the build, environment variables and backend connection yourself.
Is Lovable Cloud the same as Supabase?
Lovable's built-in backend, called Cloud, is built on Supabase's open-source foundation. You can also connect your own Supabase project instead. In both cases the same production advice applies: Row Level Security on every exposed table, no secret keys in the browser, your own email sender and working backups.
How much does it cost to run a Lovable app in production?
At the time of checking in November 2026, Lovable Pro starts at $25 a month and Business at $50, with higher credit tiers costing more. Hosting and the built-in backend draw on the same credits as building, and a separate Supabase Pro project starts at $25 a month.
Where is Lovable Cloud data stored for UK users?
Lovable Cloud projects use one of three regions: Americas, Europe or Asia Pacific. For UK customers, Europe is usually the sensible choice, and it must be chosen before the backend is enabled because the region cannot be changed later. Record the location in your privacy notice to meet UK GDPR transparency duties.
Sources
Checked on 16 November 2026. Product features and figures change quickly, so check the current source before you rely on a detail.
- Lovable documentation: Subscription plans
- Lovable documentation: Custom domains
- Lovable documentation: Launch on a custom domain
- Lovable documentation: SEO and AI search
- Lovable documentation: Cloud (built-in backend)
- Supabase documentation: Database backups
- Supabase documentation: Production checklist
- Google web.dev: Web Vitals
- Google Search Central: Redirects and Google Search
- ICO: Storage and access technologies, what are the exceptions?
Ready to take your Lovable app live?
Circlemount works as your Lovable developer: custom domains, Supabase hardening, SEO and the code clean-up that lets you keep building with confidence. Join the Circle for a free business analysis and proposal.





