Data gone? Your free backend may be paused
You launched a small site, shared it, and moved on to the next idea. A couple of weeks later someone tries to log in and nothing works. The page loads, the design looks fine, but every list is empty, sign-in spins forever, and forms throw a vague network error. You didn't change a thing. That is exactly the problem.
A lot of sites built with Lovable, Bolt, Replit, v0 and Cursor sit on a free backend or a free hosting plan. Free plans are great for getting started, but many of them pause, sleep or shut down services that don't get enough traffic. Your front end keeps loading from a static host, so the site looks alive while the part that holds your data is switched off.
The symptom
- The page loads, but data never appears and loaders spin forever.
- Login and sign-up fail with a generic "Failed to fetch" or network error.
- The first visit after a quiet spell takes 30 seconds or more, then things work again.
- Everything was fine at launch, and it broke without any new deploy.
- Your backend dashboard shows the project as paused, inactive or sleeping.
The cause
Free tiers save money for the provider by stopping things nobody is using. The exact rules differ by provider and change over time, so check their current docs, but the common patterns are these:
- Paused databases. Supabase, the backend behind many Lovable and Bolt sites, can pause free projects after a period of low activity. A paused project stops answering API calls until someone restores it from the dashboard.
- Sleeping servers. Some hosts spin down a free web service or API after it has been idle for a while. The next request has to wake it up, which can be slow enough to time out.
- Stopped development workspaces. On Replit, a project that only runs inside the editor, rather than as a proper deployment, isn't meant to stay up when you close it.
Because the static front end is served separately, your home page still returns a normal page. A simple uptime check that only looks at the home page will report that everything is fine.
Step-by-step diagnosis
- Open the live site in a private window and open the browser's developer tools. Go to the Network tab and reload.
- Look at the API requests, not the page itself. Requests to your Supabase URL, your API server or your functions will show the real problem: failed, timed out, or an error status.
- Check the Console for messages like "Failed to fetch", connection refused or timeout errors.
- Log in to your backend dashboard. In Supabase, the project page says clearly when a project is paused and offers a restore button. On other hosts, look at the service status and the logs for "sleeping", "stopped" or "suspended".
- Time a cold request. If the first request after a quiet period is very slow and the next ones are fast, you are looking at a service that sleeps, not one that is broken.
Fixes per builder or host
Lovable and Bolt with Supabase
- Restore the paused project from the Supabase dashboard. Your data is normally kept while it is paused, but restore it soon and read the notice on the project page.
- If real users depend on the site, move the project to a paid plan that doesn't pause. That is the only fix the provider guarantees.
Replit
- Publish the site as a deployment instead of relying on the workspace preview. Pick the deployment type that matches your site; a static site and a server that must always answer are different products.
v0, Cursor and other self-hosted setups
- If your front end is on Vercel or Netlify and your API or database lives somewhere else, check that other service's plan. The front-end host being up tells you nothing about it.
- For an API on a free plan that sleeps, either upgrade to an always-on instance or make the front end handle a slow first request with a clear loading message and a retry.
How to verify
- After restoring or upgrading, load the live site in a private window and confirm data appears and login works.
- In the Network tab, confirm your API requests return success and respond in a normal time.
Prevention
- Know what your free plans do when idle. Write down every service your site depends on: database, auth, API, file storage, email. Note which ones pause, sleep or expire.
- Upgrade before real users arrive, or at least before you ask anyone to rely on the site.
- Show a real error. Make your site show a friendly "We're having trouble loading your data" message instead of an endless spinner, so users tell you instead of leaving.
- Check more than the home page. Watch a page or request that actually reads from your backend, so a paused database shows up as a failure, not a pass.
