Back to Dashboard

Vibecoding Guides & Best Practices

Learn how to correctly configure Sup to keep your AI-generated backends fully awake across platforms like Lovable, Bolt.new, and Replit.

The Frontend Trap

If you just paste your vercel.app frontend URL into Sup, your database might still hibernate! Pinging a static or cached NextJS/Vite UI does not wake up a Supabase or Neon backend unless the frontend route explicitly queries the database when pinged.

The Solution: You must configure Sup to ping your database's REST API directly, OR build a dedicated /api/heartbeat route on your frontend that runs a database query.

Lovable.dev & Supabase

Lovable heavily pairs with Supabase as its official backend provider. Supabase pauses idle databases on the free tier after 7 days of inactivity. To prevent this, you need to point Sup directly at your Supabase REST API.

  1. Log into your Supabase Dashboard (the one linked to your Lovable project).
  2. Go to Project Settings > API.
  3. Copy the Project URL (it looks like https://[REF].supabase.co).
  4. In Sup, add /rest/v1/ to the end of that URL. Example: https://xyz.supabase.co/rest/v1/
  5. Copy your Supabase anon public key from the same API settings page.
  6. In Sup's Custom Headers drawer, add a header with Key: apikey and Value: [Your Anon Key].

Bolt.new / Bolt.diy

Bolt generates full-stack Remix or Vite applications. If you deployed your Bolt project via Netlify or Vercel, simply hitting the homepage will prevent the edge functions from cold-starting.

  • If your Bolt app connects to a real database (like an external Neon connection), you must explicitly create a loader route in Remix (e.g. app/routes/api.heartbeat.ts) that runs a dummy query.
  • If you are only fighting Netlify/Vercel cold boots, pasting your https://project.netlify.app URL directly into Sup with a 15-minute interval is sufficient.

Replit Deployments

Replit automatically spins down Repls that haven't received HTTP traffic. Autoscale deployments hibernate fiercely.

  • Find your Replit permanent URL (typically ending in .repl.co or .replit.app).
  • Enter this exact URL into Sup. A frequency of every 3 hours is usually enough to keep a standard webview active.
  • If you are using Replit's built-in PostgreSQL database, the network traffic hitting your Repl is enough to keep the environment running, which in turn prevents the database gateway from fully archiving.