Host a Lovable/Bolt App on Hostinger (2026)

What Lovable and Bolt actually produce

Lovable and Bolt.new are AI app builders: you describe what you want in plain language and they generate a working web app. Under the hood, what you get is a standard modern codebase — typically a Vite + React + TypeScript frontend with Tailwind CSS, and (in Lovable’s case) a Supabase project handling the database, auth, and storage. Bolt apps lean on similar stacks, often with the backend pieces you wire up yourself.

That “standard codebase” detail is the whole reason this page exists: because the output is ordinary code, it can be hosted anywhere ordinary code runs — including a Hostinger VPS. Nothing about a Lovable app requires Lovable’s own hosting. The question is never can you, it is whether the savings and control are worth the manual work.

For context on the AI-builder landscape, see our Horizons vs Lovable comparison — Hostinger’s own AI builder takes a different approach to the same problem.

Step 1 — Export your app to GitHub

Both platforms support pushing your project to GitHub. In Lovable, connect your GitHub account in the project settings and sync — every change you make in Lovable then lands in the repository. Bolt.new offers a similar GitHub export. Do this first, before anything else: the repo becomes your source of truth, your backup, and your deployment source.

Once the code is in GitHub, verify what you actually have. Clone it locally and check: is it a pure static frontend (vite build outputs HTML/CSS/JS), or does it need a Node server at runtime? Most Lovable apps are static frontends talking to Supabase — which makes hosting dramatically simpler than a full Node deployment. If there is a server component, our Node.js deployment guide covers the full VPS setup.

Step 2 — Decide what needs hosting

A typical Lovable app has two halves with different hosting needs:

• The frontend (your React app) — static files after npm run build. Can be served by any web server, including Nginx on a $4-ish VPS or a free static host.
• The backend (Supabase: database, auth, storage, edge functions) — stays on Supabase’s hosted platform. You do not need to move it, and you should not: self-hosting Supabase is a serious ops commitment.

This split is good news. It means “hosting your Lovable app on Hostinger” usually means hosting static files — the easiest possible hosting job. Update the Supabase anon key and project URL in your frontend’s environment variables to point at your existing Supabase project, and the app works exactly as it did on Lovable’s hosting.

Step 3 — Deploy the frontend on a Hostinger VPS

For a static build, the VPS setup is refreshingly simple — no Node runtime needed in production:

1. Provision a Hostinger KVM VPS (the entry plan is plenty for static files) with Ubuntu —
   63% OFF Verified Oct 8, 2026

   VPS KVM 2

   $8.99/mo $24.49/mo

   24-month plan, paid upfront

   Renews at $14.99/mo

   • 2 vCPU + 8 GB RAM
   • 100 GB NVMe storage
   • 8 TB bandwidth
   • Full root access
   • n8n one-click template available

   Get this deal
   .
2. SSH in, install Nginx: apt update && apt install -y nginx.
3. On your own machine, build the app: npm ci && npm run build — this creates the dist/ folder.
4. Copy dist/ contents to /var/www/html on the server (via scp or a deploy script).
5. Configure Nginx to serve the directory with a fallback to index.html (required for client-side routing — without it, refreshing any page except / returns a 404).
6. Add free HTTPS with Certbot: certbot --nginx -d yourdomain.com.

For updates, the loop is: pull the latest from GitHub, rebuild, re-copy dist/. A tiny shell script or GitHub Actions workflow automates this in minutes. If your app instead needs server-side rendering or API routes, you are back in Node-server territory — follow the full Node.js VPS deployment guide.

The honest DIY gap

Here is the part AI-builder marketing skips. Lovable’s one-click publish handles, invisibly: builds, CDN distribution, SSL certificates, preview URLs, rollbacks, and uptime monitoring. Moving to a VPS means you own every one of those. Concretely, the gap looks like this:

• Deploys: one click on Lovable vs. build + copy + verify on the VPS (until you automate it).
• SSL: automatic on Lovable vs. Certbot setup and renewal monitoring on the VPS.
• Rollbacks: instant on Lovable vs. keeping previous dist/ builds yourself.
• Uptime: Lovable’s problem vs. yours — add an uptime monitor (UptimeRobot’s free tier works) on day one.
• Scaling: Lovable absorbs traffic spikes vs. your single VPS has a fixed ceiling.

None of this is hard — it is an afternoon of setup, and developers do it routinely. But if you chose Lovable specifically to avoid technical work, think carefully before reintroducing server management. The VPS saves money and gives control; it does not give you your Saturday afternoons back when something breaks.

When the VPS is the right call (and when it is not)

• VPS wins: production apps with steady traffic, apps needing custom server config, anyone already managing a VPS for other projects, cost optimization at scale.
• Stay managed: MVPs and prototypes, non-technical founders, apps where Lovable’s per-month cost is still trivially small, anything where a day of downtime costs more than a year of hosting.
• Middle path: frontend on Vercel or Netlify free tier + Supabase backend — zero server management, zero VPS bill, and a clean migration path to the VPS later.

Cost comparison (checked October 2026)

• Hostinger KVM VPS (entry, plenty for static sites):
  63% OFF Verified Oct 8, 2026

  VPS KVM 2

  $8.99/mo $24.49/mo

  24-month plan, paid upfront

  Renews at $14.99/mo

  • 2 vCPU + 8 GB RAM
  • 100 GB NVMe storage
  • 8 TB bandwidth
  • Full root access
  • n8n one-click template available

  Get this deal
  — flat, unlimited bandwidth.
• Lovable paid plans: from $25/mo (pricing page, October 2026) — includes hosting, but you pay per workspace regardless of traffic.
• Vercel Hobby: free for personal projects; Pro $20/seat/mo for commercial use.
• Netlify Starter: free tier covers most small static apps.
• Supabase: free tier covers the backend for most MVPs; paid from $25/mo when you outgrow it — this cost exists no matter where the frontend lives.

The math that matters: the Supabase/backend cost is constant across options, so compare only the frontend hosting line. For a validated product, the VPS is usually the cheapest line item within the first month — the real question is whether the setup afternoon is worth it to you.

Frequently asked questions