Where to Host an AI-Generated Website

Which host is right for an AI-generated website?

Claude, Codex, ChatGPT, local scripts and design tools can now produce useful web output quickly. The result is often more than text. It is a folder with an index.html file, assets, Markdown notes, CSV data, PDFs, screenshots or a small static app.

The next question is where to put that folder.

GitHub Pages, Netlify, Vercel, Cloudflare Pages and a VPS (a rented virtual server) can all publish web content. But each one has different assumptions. The right choice depends on what you do: maintain a software project, run infrastructure, or share a generated folder with the right people.

Quick verdict

Use GitHub Pages when the site belongs in a GitHub repository and can be public.

Use Netlify when you want a developer-friendly platform with deploy previews, form handling, redirects and serverless options. Netlify also takes a plain folder by drag and drop.

Use Vercel when you build a frontend app, especially a Next.js app, and want preview URLs and app-platform features.

Use Cloudflare Pages when you have a finished folder and want to upload it without a repository. Also use it when the site is only for named people. Cloudflare Access can ask each visitor for a one-time email code.

Use a VPS, such as AWS Lightsail, Hetzner or DigitalOcean, when you need full server control. That includes SSH, Docker, databases, background jobs and operating-system access.

First, find out what the AI tool produced

A hosting choice makes sense only when you know what you have:

• A finished static folder (index.html, CSS, JavaScript, images) can go to any static host as it is.
• A framework project (package.json, src/) needs a build step. Upload the output folder (dist, build or out). As an alternative, connect the repository and let the host build it.
• An app with server code (API routes, a database, secret keys) needs an application platform or a server, not a static host.

Before any upload, remove API keys, .env files and private notes from the folder. Visitors can read every file that a browser can load. Our publishing checklist covers the review and test steps.

GitHub Pages

GitHub Pages is excellent for public static sites that belong in a repository. Examples are open-source docs, project pages, small portfolios and technical pages where Git is the natural source of truth.

To publish, put the files in a repository. Open Settings > Pages. Under Build and deployment, set Source to Deploy from a branch. Pick the branch and the /(root) or /docs folder. Then select Save (publishing source docs).

You can add files in the browser with Add file > Upload files. This method takes up to 100 files at a time and 25 MiB per file. You do not have to use Git commands. Changes can take up to 10 minutes to appear.

Know the limits before you choose it:

• On GitHub Free, the repository must be public. Also, GitHub Pages sites are public on the internet even when the repository is private. Private Pages sites need GitHub Enterprise Cloud. Only people with read access to the repository can see such a site.
• A published site can be no larger than 1 GB. The soft bandwidth limit (a guideline, not a hard cutoff) is 100 GB per month (GitHub Pages limits).
• GitHub does not let you use Pages to run an online business, e-commerce site or SaaS product.

GitHub Pages is the clean repo-to-public-site path. It is the wrong place for a confidential client draft. For the steps, see publish an AI-generated site on GitHub Pages.

Netlify

Netlify is a mature web deployment platform. It is strong when a team wants Git deploys, build commands, deploy previews, serverless functions, forms, redirects and framework support.

It also works when the output is already finished. Drag the folder onto Netlify Drop to get a live .netlify.app address. To update the site later, drag the new folder onto the Deploys page of the project (Netlify deploy docs). Log in first, so that the project stays in your account. Netlify keeps every deploy, so you can roll back with Publish Deploy on an earlier one.

Two features matter for AI-generated sites. Netlify Forms handles submissions from plain HTML forms. This fixes the common “the contact form does nothing” problem. Password protection is available, but it needs a Pro or Enterprise plan. For the steps, see publish an AI-generated site on Netlify.

Vercel

Vercel is a strong choice for production frontend apps, especially Next.js. Its main features are Git previews, production deployments, framework integrations and server or edge functions.

You do not need Git to try it. From the folder, run the Vercel CLI:

vercel

The first deployment of a new project goes to production. Later releases go to production with:

vercel --prod

For private review, Vercel Authentication works on all plans. But visitors need a Vercel account with access, or a Shareable Link that you create for a deployment. Password Protection is available on Pro as a paid option and on Enterprise, not on Hobby (Deployment Protection). For the steps, see publish an AI-generated site on Vercel.

Cloudflare Pages

Cloudflare Pages takes a finished folder through Direct Upload. Drag and drop in the dashboard takes up to 1,000 files. The Wrangler command-line tool takes up to 20,000 files. Each file can be up to 25 MiB (Direct Upload docs). Cloudflare Pages can also build from a Git repository. Choose carefully, because you cannot switch a Direct Upload project to Git later.

Its strength for client work is Cloudflare Access. Instead of one shared password, you list the email addresses of the reviewers or their company domain. Each visitor receives a one-time code by email. You can remove one reviewer, and the access of the other reviewers does not change. For the steps, see protect a Cloudflare Pages site with Access. For the walkthrough without Git, see host an AI-generated website without Git.

VPS hosting

VPS providers such as AWS Lightsail, Hetzner and DigitalOcean give you a server. That can be exactly right when you need full control: custom services, long-running processes, databases, Docker, cron jobs (scheduled tasks), backend APIs or private networking.

A server also means that you own the work to run it. This work includes SSH, operating-system updates, web server configuration, TLS certificates, firewall rules, backups, monitoring, logs, deployments and security patches.

If the job is only “make this folder live”, a static host is the shorter path. If the folder is one part of a larger system that you already run, serve it from that server. For the steps, see publish a static folder on a VPS with Caddy.

Decision table

Need	Best fit
Public docs for an open-source repo	GitHub Pages
Marketing site with Git deploys and branch previews	Netlify, Vercel or Cloudflare Pages
Next.js or frontend app deployment	Vercel
Full server control, Docker, databases, backend services	VPS hosting
AI-generated folder that needs a live URL today, no repository	Netlify Drop or Cloudflare Pages Direct Upload
Client review link limited to named people	Cloudflare Pages with Cloudflare Access
Client review link with one shared password	Netlify (Pro or Enterprise) or Vercel (Pro paid option or Enterprise)
Folder with HTML, Markdown, CSV and PDF files	Any static host, plus an index.html that links the files

Example workflow

Suppose Codex or ChatGPT creates a folder like this:

launch-report/
  index.html
  Readme.md
  data/report.csv
  docs/brief.pdf
  assets/chart.webp
  notes/client-followup.md

Before you publish anywhere, look at every file. notes/client-followup.md sounds like an internal note. If it is, delete it. A static host serves every file in the folder to anyone who has the URL.

Then make the folder easy to read online. A static host serves each file as it is. Browsers open PDFs directly, but Markdown and CSV files often download or show as plain text. Ask the AI tool to make index.html a short landing page. The page links to the PDF and the CSV, with one line about the content of each. Also ask the tool to turn the notes for reviewers into HTML.

Now pick the host:

• Use GitHub Pages if this folder will become a public report in a repository.
• Use Netlify or Vercel if it grows into a web project with Git deploys, previews, builds or app features.
• Use Cloudflare Pages with Access if the report is only for the client’s team.
• Use a VPS if the folder is one part of a larger server that you already control.

AI tools make it easy to create useful web folders. The publishing layer must match the job. Ask who must see the result and how long it will live. Also ask whether anything on it needs a server.

A docs portal with Ask AI
and support tickets

Connect a repository, or describe your product to start. Each docs site has search, Ask AI, an API console, an MCP server and support tickets.

• Publishes from GitHub on every push
• Works with Mintlify repositories
• API console from your OpenAPI file
• MCP server and llms.txt for AI agents
• Ask AI and support tickets
• Analytics for people and AI agents

Start Free→ Questions? Ask AI in our docs

No card required.