Security and shipping

Deploying a vibe-coded app: Vercel, Netlify or shared hosting?

Published Updated 8 min read

Read in : Français

Contents
  1. Is your app static, or does it need a server?
  2. Vercel, Netlify and shared hosting: how do they compare?
  3. Vercel: the best fit for Next.js, as long as you pay for commercial projects
  4. Netlify: simple and feature-rich, but watch your credits
  5. Shared hosting: the cheapest option for a static app, with caveats
  6. Which host should you choose?
  7. What should you check after deploying?
  8. Frequently asked questions
  9. Frequently asked questions
  10. Sources

When you deploy a vibe-coded app, the first question is not "which host?" but "does my app have server code?". A static app (React and Vite, with Supabase as the database) can go live anywhere, including cheap shared hosting. An app with server-side rendering or API routes needs Vercel, Netlify or a host that runs Node.js. Here is how to tell, compare and choose.

Is your app static, or does it need a server?

Your app is static if the build command produces a folder of HTML, CSS and JavaScript files that is enough to run it. That is the case for React and Vite apps: npm run build writes to a dist folder by default, and any web server can serve that folder.

Your app needs a server if it contains code that runs on the server for each request: Next.js API routes, Server Actions, server-side rendering.

How to recognise your stack:

Clue in the projectType of appWhere to deploy it
vite.config.ts, a dist folder after buildStatic (SPA)Anywhere: Vercel, Netlify, shared hosting
next.config.js, an app/api folderNext.js with server codeVercel, Netlify, or a Node.js host
A supabase/functions folderStatic, plus functions hosted by SupabaseAnywhere for the front end; functions stay on Supabase
TanStack StartHas server codeA host that can run that code

An important point if you use Lovable: its docs say older apps are React and Vite and build to static files, while new apps created from 13 May 2026 use TanStack Start, which runs server code and needs a compatible host. Check when your project was created before you choose.

Vercel, Netlify and shared hosting: how do they compare?

The three options serve different needs. Prices checked on 21 November 2026 on each host's official pages.

CriterionVercelNetlifyShared hosting (Hostinger, o2switch)
Static appYesYesYes
Node.js server codeYes, native (Next.js)Yes (functions)Depends on host and plan
Free tierHobby: personal, non-commercial useFree: 300 credits a month, hard limitNo
First paid planPro: $20 a month per developer seatPersonal: $9 a monthHostinger: from $1.99 a month on a 48-month term
DeploymentAutomatic on every Git pushAutomatic on every Git pushFile upload (FTP, file manager)
Preview per branchYesYesNo
HTTPSIncludedIncludedIncluded (free SSL on Hostinger plans)

Vercel: the best fit for Next.js, as long as you pay for commercial projects

Vercel makes Next.js, and it is where Next.js apps deploy with the least friction. You connect your GitHub repository, every push creates a deployment, and every branch gets its own preview URL.

What to know about the free plan:

The trap to know about: environment variable changes only apply to new deployments. If you change a key, redeploy. And any variable prefixed with NEXT_PUBLIC_ is bundled into browser code, so never put a secret key in one (see why API keys must never live in your front end).

Netlify: simple and feature-rich, but watch your credits

Netlify works like Vercel for Git deployments and previews, with a credit system across all its plans.

What to know about the free plan:

Do the maths: 300 credits buys 20 production deploys, or about 15 GB of bandwidth, but not both. A vibe-coded app you tweak several times a day can burn through the Free plan in a week. Batch your changes and test on deploy previews, which are free.

Paid plans: Personal at $9 a month with 1,000 credits, and Pro at $20 a month for unlimited members with 3,000 credits.

For a static app with client-side routing (React Router), add this rule in a public/_redirects file, or deep links will return a 404:

/*  /index.html  200

Shared hosting: the cheapest option for a static app, with caveats

Shared hosting such as Hostinger, or a local provider like o2switch in France, serves a static app perfectly well: upload the contents of your dist folder to the public directory and you are live.

Prices checked on 21 November 2026:

Always check the renewal price: that is what you pay from year two (or year five on a long term).

The limits to know about:

  1. No automatic deployment: you upload files by hand after each build, unless your host offers Git deployment and you set it up.
  2. SPA routing: as on Netlify, unknown URLs must be rewritten to index.html. On Apache, one line in .htaccess does it:
FallbackResource /index.html
  1. Node.js is not guaranteed: on cPanel, running Node.js apps depends on packages your host has to install. Ask your host before deploying a Next.js or TanStack Start app there.

Which host should you choose?

The right choice depends on two questions: does your app have server code, and is it commercial? Here is the decision tree.

The full monthly budget, hosting included, is in what a vibe-coded app really costs. And if you want to do it all without paying, see what you can really do with free vibe coding.

What should you check after deploying?

Deploying is not the finish line; it is the moment your app goes public. Five checks to run within the hour:

  1. HTTPS everywhere: http:// should redirect to https://.
  2. Deep links: reload an inner page (for example /account). A 404 means the routing rule is missing.
  3. Environment variables: every variable you need is set for production, and no secret key has a public prefix.
  4. Auth redirects: in Supabase, add your production domain to the allowed redirect URLs, or sign-in will fail or send users to the wrong address.
  5. Security headers: run your URL through MDN HTTP Observatory.

These points are part of the pre-launch security checklist. To get back to a working version if a deploy breaks everything, keep a clean history with Git for vibe coders, and test big changes on a staging environment. If your app needs to be found on Google, read why Google can't see your page as well.

Frequently asked questions

Frequently asked questions

Can I use Vercel's free plan for a client project?

Not if the project is commercial. Vercel's terms of service limit the Hobby plan to personal or non-commercial use, and its docs point commercial use to the Pro or Enterprise plans. A site built for a client, one that sells a service or carries a company brand, belongs on Pro, which cost $20 a month per developer seat as of 21 November 2026.

What happens when you run out of Netlify Free credits?

All your projects are paused, and visitors see a "Site not available" page. The Free plan is a hard limit: you cannot buy extra credits, so you have to wait for the monthly reset or upgrade to a paid plan. At 15 credits per production deploy and 20 credits per GB, 300 credits go quickly if you deploy often.

Can I host a Lovable app on cheap shared hosting?

Yes, if it is a static React and Vite app: export the code through GitHub, run npm run build, then upload the contents of the dist folder to your public directory, with a FallbackResource rule in .htaccess. Lovable apps created from 13 May 2026 use TanStack Start and run server code, so check that your plan can run Node.js first.

Do I need a host if the tool already publishes my app?

Not necessarily. Lovable, for example, publishes your app for free on a lovable.app subdomain and offers custom domains on paid plans. A separate host becomes useful when you want to control costs, stop depending on the tool, add server functions or keep your data in a specific country. Export your code to GitHub either way.

Vercel or Netlify: which is easier for beginners?

Both are equally easy for a static app: connect your GitHub repository and every push triggers a deployment. Vercel is the natural home for a Next.js app, since it makes the framework. Netlify's credit model makes costs easy to read, but it pauses your site on the free plan. The deciding factor is often whether the app is commercial.

Sources