What happens to your website if you stop paying your AI website builder?
Cancellation is the moment ownership questions stop being theoretical. The platforms document some of what happens next and leave a lot unsaid. This guide separates downgrading, cancelling, deleting and being cut off, reports only what’s written down, and says plainly where we couldn’t verify. If the site matters, the work happens before you cancel.
Four different things that sound like one
“Stop paying” covers four situations, and the platforms treat them differently:
- Downgrading or cancelling a subscription. Your account continues on the free tier. This is what most people mean, and it’s the best documented.
- Deleting your account or workspace. You ask the platform to remove everything. Usually irreversible after a grace period.
- Termination by the provider. The platform ends your access under its terms of service, for cause or otherwise.
- Non-payment. A card fails and the platform suspends or downgrades you.
The sections below keep these apart, and report only what each platform’s current public documentation says. Where a platform doesn’t document what happens to a specific resource, the guide says so rather than guessing, because the honest answer to “what happens to my database if I cancel?” is often “the documentation doesn’t say”.
The comparison, verified only
Each cell is either a documented behaviour, “not documented”, or “depends on” another service. Downgrade or cancellation is the scenario unless a cell says otherwise.
| After you cancel | Lovable | Bolt | Replit | v0 |
|---|---|---|---|---|
| Code stays accessible | Yes. Git sync is on all plans; a connected repository stays on GitHub. Full ZIP download is paid-only, and the code editor is read-only on Free. | Yes. ZIP export has no documented plan gate; a connected GitHub repository is yours. | Yes. Downgrading deletes nothing; ZIP download and Git push are available. | Yes. The repository is on GitHub; v0’s Free plan lists GitHub sync. |
| GitHub sync keeps working | Yes. Git sync is listed on every plan. | Not documented (no plan gating stated for the GitHub integration). | Yes. The Git pane isn’t plan-gated in the documentation. | Yes. Listed on the Free plan. |
| Existing deployment stays online | Yes. A published site stays live indefinitely; downgrading or cancelling doesn’t unpublish it, though Lovable stops publishing new changes. Cloud and AI features need credits to serve requests. | Sites already published to a custom domain stay online, but can’t be republished on Free. Free hosting stops serving when monthly traffic limits are hit, until usage resets. | Replit warns published apps may go offline at the transition to Starter. Starter allows one published app that expires after 30 days. | Depends on the Vercel plan, not v0. Vercel Hobby is non-commercial; a paused deployment shows visitors a 503 error, and exceeded limits mean waiting until the 30-day period resets. |
| Custom domain stays connected | Yes. Already-connected domains keep working; connecting a new one needs a paid plan. | Yes, until you need to republish or reconnect, which Free doesn’t allow. Bolt-bought domains stay manageable. | No. Replit says custom domain connections are removed at the transition. | Depends on the Vercel plan. Domains are configured on the Vercel project. |
| Backend or database keeps running | Cloud runs on credits (Free grants 20 a month). When they run out, Cloud services pause, and Lovable says you can’t access or export the data until they run again. Your own Supabase project is unaffected by Lovable’s plan. | A published project’s Bolt Database isn’t paused; an unpublished one may be paused after about six days of low use. Fate on a lapsed subscription: not documented. | Replit says storage is reduced at the transition and the database restore window shortens. Whether the production database keeps running: not documented. | Marketplace resources are billed through the Vercel team; governed by Vercel, not v0. |
| Grace or export period | The plan stays active to the end of the billing period. Account deletion has a 30-day grace period; workspace deletion 60 days. | The plan runs to the end of the billing cycle. On a failed payment Bolt retries for a few days, then reverts you to Free. The StackBlitz terms give 30 days to export content if StackBlitz ends access other than for cause. | Plan features last to the end of the billing period. Some subscribers can pause for a month with published projects staying live. Deleted projects recoverable for 30 days. | The plan runs to the end of the billing period. Deleted chats are archived for 30 days. Vercel says content may be permanently deleted on termination of the account. |
| Eventual deletion | Only on account or workspace deletion, after the grace periods. Inactive-project deletion: not documented. | Deleting a project or account deletes its projects and databases. Inactivity deletion: not documented. | Free accounts inactive for a year can have their apps deleted; paid accounts aren’t subject to inactivity termination. Account deletion purges everything. | Account deletion is irreversible. Nothing documented about the repository or Vercel project on a v0 plan lapse. |
- Lovable
- Yes. Git sync is on all plans; a connected repository stays on GitHub. Full ZIP download is paid-only, and the code editor is read-only on Free.
- Bolt
- Yes. ZIP export has no documented plan gate; a connected GitHub repository is yours.
- Replit
- Yes. Downgrading deletes nothing; ZIP download and Git push are available.
- v0
- Yes. The repository is on GitHub; v0’s Free plan lists GitHub sync.
Code stays accessible
- Lovable
- Yes. Git sync is listed on every plan.
- Bolt
- Not documented (no plan gating stated for the GitHub integration).
- Replit
- Yes. The Git pane isn’t plan-gated in the documentation.
- v0
- Yes. Listed on the Free plan.
GitHub sync keeps working
- Lovable
- Yes. A published site stays live indefinitely; downgrading or cancelling doesn’t unpublish it, though Lovable stops publishing new changes. Cloud and AI features need credits to serve requests.
- Bolt
- Sites already published to a custom domain stay online, but can’t be republished on Free. Free hosting stops serving when monthly traffic limits are hit, until usage resets.
- Replit
- Replit warns published apps may go offline at the transition to Starter. Starter allows one published app that expires after 30 days.
- v0
- Depends on the Vercel plan, not v0. Vercel Hobby is non-commercial; a paused deployment shows visitors a 503 error, and exceeded limits mean waiting until the 30-day period resets.
Existing deployment stays online
- Lovable
- Yes. Already-connected domains keep working; connecting a new one needs a paid plan.
- Bolt
- Yes, until you need to republish or reconnect, which Free doesn’t allow. Bolt-bought domains stay manageable.
- Replit
- No. Replit says custom domain connections are removed at the transition.
- v0
- Depends on the Vercel plan. Domains are configured on the Vercel project.
Custom domain stays connected
- Lovable
- Cloud runs on credits (Free grants 20 a month). When they run out, Cloud services pause, and Lovable says you can’t access or export the data until they run again. Your own Supabase project is unaffected by Lovable’s plan.
- Bolt
- A published project’s Bolt Database isn’t paused; an unpublished one may be paused after about six days of low use. Fate on a lapsed subscription: not documented.
- Replit
- Replit says storage is reduced at the transition and the database restore window shortens. Whether the production database keeps running: not documented.
- v0
- Marketplace resources are billed through the Vercel team; governed by Vercel, not v0.
Backend or database keeps running
- Lovable
- The plan stays active to the end of the billing period. Account deletion has a 30-day grace period; workspace deletion 60 days.
- Bolt
- The plan runs to the end of the billing cycle. On a failed payment Bolt retries for a few days, then reverts you to Free. The StackBlitz terms give 30 days to export content if StackBlitz ends access other than for cause.
- Replit
- Plan features last to the end of the billing period. Some subscribers can pause for a month with published projects staying live. Deleted projects recoverable for 30 days.
- v0
- The plan runs to the end of the billing period. Deleted chats are archived for 30 days. Vercel says content may be permanently deleted on termination of the account.
Grace or export period
- Lovable
- Only on account or workspace deletion, after the grace periods. Inactive-project deletion: not documented.
- Bolt
- Deleting a project or account deletes its projects and databases. Inactivity deletion: not documented.
- Replit
- Free accounts inactive for a year can have their apps deleted; paid accounts aren’t subject to inactivity termination. Account deletion purges everything.
- v0
- Account deletion is irreversible. Nothing documented about the repository or Vercel project on a v0 plan lapse.
Eventual deletion
Lovable
Cancel or downgrade. Lovable’s pricing page says that after you cancel, remaining credits stay usable to the end of the billing period, then the plan switches to Free. Its documentation says a published site stays live and isn’t unpublished by a downgrade, that already-connected custom domains keep serving, that for most features Lovable keeps your configuration so they resume if you upgrade again, and that the “Edit with Lovable” badge returns on the next publish from a Free workspace. Downgrading freezes subscription credits and stops publishing new changes. Apps using Cloud or built-in AI need credits to serve requests: the Free plan grants 20 Cloud credits a month, and when a workspace runs out, Lovable says the backend services pause and the data can’t be accessed or exported until they run again. Lovable also pauses Cloud projects after a period of inactivity. Lovable-bought domains are billed separately and keep renewing.
Deletion. Deleting an account has a 30-day grace period, after which workspaces you own go too unless you transferred them; deleting a workspace stops its projects serving on their lovable.app addresses immediately and removes custom domains and data after a 60-day grace period. Removing Cloud from a project deletes the Cloud instance permanently. Before cancelling or deleting, projects can be moved to another workspace or their ownership transferred.
Termination. Lovable’s terms say your right to access the services ends on termination; we could not find a documented data-retention window after provider termination.
Not documented: how long a paused Cloud instance is retained, what happens on a failed payment, and whether inactive projects on a live account are ever deleted.
Bolt
Cancel or downgrade. Bolt says cancelling a paid subscription is the same as downgrading to Free at the next billing cycle. On Free, sites already published to a custom domain stay online, but you can’t republish or reconnect a custom domain; free hosting has hard monthly limits on traffic and requests, and a site goes offline for the rest of the month once they’re reached; the “Made in Bolt” badge appears. Bolt-bought domains stay in your account and can still be managed. A published project’s Bolt Database isn’t paused; an unpublished one may be after about six days of low use.
Non-payment. Bolt retries a failed charge a few times over the following days; if the payment method isn’t updated before the retries end, the plan reverts to the free tier and rollover tokens are lost.
Deletion. Deleting a project permanently removes its files, chat history and Bolt Database; a connected Supabase project is unaffected. Deleting the account deletes its projects. Before that, a project can be downloaded, synced to GitHub, or transferred to another Bolt user.
Termination. The StackBlitz terms that govern Bolt, published on 14 September 2026 and effective for existing accounts from 29 September, say StackBlitz may restrict or end access at any time with or without notice; if it does so other than for cause, it will provide a reasonable means to retrieve your content for thirty days, after which it may delete it. Termination for breach of the acceptable-use policy carries no export period.
Not documented: what happens to a Bolt Database when a subscription simply lapses, whether the GitHub integration is affected by plan, and any inactivity-based deletion.
Replit
Cancel or downgrade. Replit’s subscriptions page says you keep your plan’s features until the end of the billing period, then move to the free Starter plan, and warns that before that transition published apps may go offline, custom domain connections are removed and storage is reduced, and that you should download anything you want to keep first. Its plan-change page says downgrading deletes nothing; projects and data stay intact, and the two statements reconcile as “your data isn’t deleted, but deployments and domain connections can go down”. The database’s point-in-time restore window shortens. On Starter, one published app is allowed and its link goes down after 30 days. Some subscribers can pause a subscription for a month with published projects staying live, which may suit a short break better than cancelling.
Non-payment. Continuous payment failures can lead to published apps being suspended, after a 24-hour grace period, and Replit’s terms say an unpaid account may be limited or terminated.
Deletion and inactivity. Deleted projects are recoverable for 30 days. Deleting the account purges everything, unrecoverably. Free accounts inactive for a year can be terminated and their apps deleted; paid accounts aren’t subject to inactivity termination.
Termination. Replit’s terms let it suspend or terminate an account at its discretion, with access ending immediately; data after account deletion is handled under a retention policy the terms don’t quantify.
Not documented: what happens to the production database (on Neon) after a downgrade beyond “storage is reduced”, and what happens to a Replit-bought domain’s registration.
v0 and Vercel
v0 is different because the site never lived in v0. Cancelling a v0 plan moves the account to Free at the end of the billing period; purchased credits remain but need an active paid plan to use; deleted chats are archived for 30 days. v0’s Free plan lists GitHub sync and deploying to Vercel. The repository is on GitHub and the site is a Vercel project, so what happens to the live site is governed by the Vercel plan: Hobby is restricted to personal, non-commercial use, can’t deploy from a private repository in a GitHub organization, and pauses features when usage limits are exceeded until the 30-day period resets. Vercel says a paused account or deployment stops serving and visitors see a 503 error, and names commercial use on Hobby as a frequent trigger. Downgrading a Vercel team from Pro to Hobby removes its other members, and Vercel says connected stores and domains must be transferred elsewhere first.
Non-payment and termination (Vercel). If a payment can’t be charged, Vercel may suspend or terminate access and may let a domain registration expire. Vercel’s terms allow termination with thirty days’ notice for convenience, ten days for breach, two for non-payment, and say your content may be permanently deleted on termination; Hobby projects may be shut down without notice. Within fourteen days of its domain terms ending, Vercel will help transfer unexpired domains to another registrar on request.
Not documented: anything in v0’s documentation about the repository or the Vercel project on a v0 plan lapse, because those aren’t v0’s to change.
Before you cancel
The pattern across all four is the same: the code is safe, the live site is the platform’s to keep serving or not, and the backend is the least documented. So if the website matters, establish ownership and portability before you cancel, not after.
Pre-cancellation checklist
- The code is in a GitHub repository under my account, and I’ve opened it. Guide.
- I know which builder services the site depends on: database, sign-in, storage, managed keys. Guide.
- I have a downloaded export of the database and the uploaded files, taken this week.
- Every secret is listed by name with where it’s regenerated. Guide.
- The domain is in a registrar account I control, or I’ve started moving it. Guide.
- If I want the site to keep running after cancelling, it’s deployed from the repository on a host I control and the domain points there. Guide.
- I’ve read what my builder documents for my exact situation: Lovable, Bolt, Replit, v0.
- I’ve taken the portability test and fixed anything the first two and fifth questions turned up.
Sources
The rules and product behaviour described above were checked against these pages when the guide was last updated. If something here has changed, these are the places to look.
- Pricing FAQ: cancelling · Lovable
- Terms of service · Lovable
- Publish · Lovable
- Custom domain · Lovable
- Subscription plans · Lovable
- Cloud · Lovable
- Delete your account · Lovable
- Delete a workspace · Lovable
- Billing · Bolt
- Domains · Bolt
- Hosting plans · Bolt
- Bolt Database · Bolt
- Projects and files · Bolt
- Terms of service (published 14 September 2026) · StackBlitz
- Subscriptions help · Replit
- Changing your plan · Replit
- Starter plan · Replit
- About usage-based billing · Replit
- Account inactivity · Replit
- Deleting your data · Replit
- Account · v0
- Pricing · v0
- Vercel integration · v0
- Hobby plan · Vercel
- Pro plan: downgrading · Vercel
- Fair use guidelines · Vercel
- Why is my account or deployment blocked? · Vercel Knowledge Base
- Terms of service · Vercel
- Credits and usage · Lovable
- Terms of service · Replit
Keep going
Related guides
Or go back to the overview of what owning your site means, which ties all of these together.
Is your AI-built website actually portable?
A concrete portability test for a website built with an AI tool: nine questions about the code, the accounts, the hosting, the domain, the data, the credentials and the deployment path, with a way to score where you stand and what to fix first.
About a 7 minute read
How to take your website with you when you leave an AI builder
Leaving an AI website builder means more than downloading the code. An inventory of everything a site depends on, from the domain to the database to the secrets, and a structured checklist for moving it all.
About a 10 minute read