Skip to main content
Deployment guide ยท Web apps ยท 12-point pre-flight check

Deploy Vibe Coded Apps

Your AI-built prototype works on localhost or in a builder's preview. This guide turns it into a production web app that keeps its data, keeps its secrets, survives real traffic and doesn't surprise you with the bill.

  1. Pre-flightFix the 12 things that break between localhost and live
  2. DeployFollow the path for the tool that built your app
  3. Pick hostingChoose free, managed or flat-rate for your traffic

"Localhost to Live" pre-flight checklist

Twelve checks that catch the problems AI-built apps most often hit in production. Open any item to see why it fails and copy a prompt that fixes it. Your progress is saved in this browser.

0/12 checks passed
Prompts for:

Secrets & .env

0/3

Database & Storage

0/3

URLs & CORS

0/3

Security & Rate Limits

0/3

Stack-specific deployment paths

Pick the tool that built your app. Each path has four steps, the commands to run and the gotchas that catch people on that stack.

Browser-based builders that generate a Vite + React front end, usually wired to Supabase. Their one-click publish is fine for demos; for a real product, move the code to GitHub so you own the deploy pipeline, the domain and the history.

Typical hostingNetlify, Vercel or Cloudflare Pages + Supabase
  1. Sync the project to GitHub

    Use the builder's GitHub integration so every change lands in a repo you own. Clone it and confirm it builds on your machine, outside the builder.

    git clone https://github.com/you/your-app.git
    cd your-app
    npm install
    npm run build && npm run preview
  2. Separate dev and production Supabase

    Create a second Supabase project for production, enable RLS on every table, and keep only the anon key in the front end. Apply the schema with migrations instead of clicking in the dashboard.

    npx supabase link --project-ref YOUR_PROD_REF
    npx supabase db push
  3. Deploy with an SPA fallback

    Import the repo into your host with build command npm run build and output folder dist. Add a rewrite so deep links like /dashboard don't 404 on refresh.

    # Netlify / Cloudflare Pages
    echo "/*  /index.html  200" > public/_redirects
    
    # Vercel: vercel.json
    { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }
  4. Point your domain and update auth URLs

    Add the domain in your host, create the DNS records it shows you, then set the Site URL and redirect URLs in Supabase Auth to the new domain.

    Type   Name   Value
    A      @      <IP from your host>
    CNAME  www    <your-project>.netlify.app

โš ๏ธ Bolt.new / Lovable gotchas

  • RLS disabled on tables created during prototyping. The anon key is public, so these tables are effectively public too.
  • Supabase free projects pause after about a week without activity. A launch page nobody visits will go dark.
  • Preview-only features: builder-specific integrations and edge functions may need to be re-created as Supabase Edge Functions or host functions.
  • Two sources of truth: once you edit code locally, re-sync before prompting the builder again or it may overwrite your changes.

Free vs. flat-rate hosting matrix

Where vibe coded web apps usually end up, what you get for free and what bites later.

PlatformFree tierPaid fromBilling modelWatch out for
Vercel Hobby plan, non-commercial use only Pro $20/user/mo + usage Usage-based Commercial apps need Pro. Image optimization and function time are metered.
Netlify Free plan with monthly usage limits Pro ~$19/member/mo Credits / usage Bandwidth and build minutes add up; free sites pause when limits run out.
Cloudflare Pages & Workers Static hosting with unmetered bandwidth Workers Paid $5/mo Requests + CPU time Workers aren't full Node.js; some npm packages need changes.
Render Free web services that sleep when idle Starter $7/mo per service Flat per instance Free services spin down after ~15 min idle; free Postgres expires.
Railway One-time trial credit Hobby $5/mo incl. $5 usage Usage (CPU + RAM) Idle services still bill for the memory they hold.
Fly.io Pay as you go A few $ per small machine Usage per machine Machines and volumes left running in extra regions keep billing.
Supabase 2 free projects Pro $25/mo per org Flat + usage Free projects pause after ~1 week idle; compute add-ons cost extra.
VPS + Coolify / Dokploy n/a (self-hosted, open source) ~$5โ€“12/mo (Hetzner, DigitalOcean) Flat rate You own updates, backups, security and uptime.

Approximate list prices in USD as of November 2026. Plans change often, so confirm on each vendor's pricing page before you commit.

Hosting cost estimator

Set your traffic and the kind of app you built to compare monthly bills and see which strategy fits.

Monthly traffic
Workload
Recommended

Free tiers

Cloudflare Pages, Vercel Hobby, Netlify, Render free, Supabase free

$0 /mo

Recommended

Managed / usage-based

Vercel Pro, Netlify Pro, Render, Railway, Supabase Pro

$0โ€“$20 /mo

Recommended

Flat-rate VPS

Hetzner or DigitalOcean with Coolify or Dokploy

$5โ€“$8 /mo

Best strategy

Free tier while it's a side project

Next.js deploys with zero config on Vercel, and small traffic fits inside free limits. If the app makes money, budget $20/mo for Vercel Pro from day one.

๐Ÿšฉ Billing traps at this size
  • The Hobby plan doesn't allow commercial use.
  • Serverless functions time out (10โ€“60 s by default), so long AI calls or PDF generation fail only in production.

Rough monthly estimates for one app, excluding your domain (~$10โ€“15/year). "Outgrown" means free limits, sleep or commercial-use rules make that option a poor fit at this traffic. Real bills depend on page weight, caching and how chatty your app is with its database.

After you launch

Deploying is the start. Keep the habits that got you here: small changes, one at a time, committed when they work.

We use cookies for ads and analytics.