Where to host an AI-built website

You have built a website with ChatGPT, Claude, Cursor, Bolt or Lovable, and it works on your computer. To put it online, first ask what needs to run when someone visits it. The tool that wrote the code does not determine the hosting.

Best hosting for AI-built projects: a 2026 comparison

There is no universal winner: generated code may be a static site, a server-rendered app, or a frontend connected to an API and database. This editorial comparison was reviewed on 9 October 2026 using the linked public product and pricing pages. It compares workflows and published limits; it is not an independent speed, uptime or support test.

For a static Git frontend, compare Projects, Netlify and Vercel by framework, workflow and billing. For Next.js with SSR, validate the exact runtime; static export changes hosting requirements. For Docker or background jobs, compare managed containers with a VPS and include operations time. An external database, authentication service or file store does not move with the frontend. Hostbrid operates infrastructure in Spain; see Sites, Projects and VPS pricing and limits. Vercel, Netlify and Hostinger pricing can vary by country, currency, taxes and usage: check Vercel Hobby terms, Vercel pricing and Netlify pricing and credits. For managed website hosting and total cost, see our web hosting value comparison.

Choose hosting based on what your project needs to run

• HTML, CSS or a static frontend built from Git: Projects builds and publishes the repository. Check the framework, build command and output directory; the AI tool’s name does not guarantee compatibility.
• WordPress, PHP or a website managed through a control panel: compare Sites and its compatible applications. For Node.js, first check the Node Apps workflow in Sites: it requires an app associated with a domain and has its own configuration.
• If you manage websites for several clients: read the agency hosting guide, which compares Sites Agency with the separate features of reseller hosting.
• An API or Node/Docker process alongside the frontend: consider Projects services only after checking the runtime, plan, quotas, port and storage it needs. For Node.js, compare this with the Sites and VPS paths.
• Docker Compose, system packages or root access: a VPS lets you manage the environment; you are responsible for configuring and maintaining the system and services.

If the project exposes tools through MCP and needs to stay reachable over HTTP, see the guide to hosting your own MCP server on a VPS. That is different from connecting an assistant to Hostbrid’s MCP to manage resources in your account.

For Nuxt, check whether the app builds to static files or needs Nitro running at request time; the Nuxt SSR on Projects guide explains the Node output and deployment checks.

For SvelteKit, the adapter determines what the host must run. See the SvelteKit adapter-node guide for Projects if the app needs a server; if it can be prerendered, check the static output before choosing a runtime.

If you are considering leaving Netlify, first check whether your site relies on forms, functions or previews from that platform. The guide to moving a static Netlify site to Projects reviews those dependencies before you change DNS.

If the project has a database, authentication or files, decide where each component will live before ordering: publishing the frontend does not migrate that data or create a backend by itself. If you keep Supabase while moving a Vite frontend, use the guide to URLs, RLS and redirects to check the connection.

Guides for your next step

With Cursor, distinguish the editor from the deployment service: Cursor’s Cloud Agents can publish through Vercel when you connect a Vercel account. If you want to take the code to another provider, push it to Git and check its framework, server and external services first; Cursor’s Git guide covers cloning, pushing and syncing repositories. Then follow our guide to publishing a website built with Cursor on Projects.

Once the project is live, follow the guide to connect a custom domain to Projects without replacing your entire DNS zone or disrupting email. If you are deciding between publishing without a monthly plan or moving to a paid plan, see free vs paid web hosting to compare the subdomain and Dev limits with your project’s service needs.

If you built with Figma Make and want to deploy its GitHub repository, follow the Figma Make to Projects guide. This is different from Figma Sites, which has its own publishing option. If you built with Claude Code, first check whether your repository produces static files or needs a server; our Claude Code Git and deployment guide separates the coding agent from hosting.

If you built with Base44 and want to move the code outside its platform, see the GitHub export and hosting guide; changing frontend hosting does not migrate its backend or data. If you used Google AI Studio, check which parts are static and which need a server before moving the app to GitHub and Projects; its keys and external services do not migrate by themselves.

For a specific project, use the guide to publish from localhost to a public URL, deploy React and Vite from Git, publish Astro and Markdown from Git, or check whether Next.js can be exported as static files. Each walkthrough checks a different case; they do not imply that every feature works on the same product.

A static website: files the browser can load

An HTML landing page with CSS and images can be served as files. A React project using Vite can also produce static files after a build. That does not make every React application static: check for server code and external services.

Inspect package.json and its build command. In a Vite project configured for static deployment, npm run build normally creates dist; configuration can change that directory. Do not upload node_modules or confuse the development server with the production build. Vite documents this process.

Hostbrid Projects imports repositories from GitHub, GitLab or Bitbucket, builds your project and publishes it with HTTPS. Check the build command and output directory for your repository. This workflow uses Git: downloading a ZIP from an AI tool does not mean the panel supports direct ZIP uploads.

If you have plain HTML and CSS without a backend, follow the AI-generated HTML publishing walkthrough, with a reusable repository, settings and a live demonstration.

If the website includes a form, distinguish browser validation, the backend and message delivery with our form diagnostics guide. A success screen does not prove email receipt; the original example only validates synthetic data locally without sending email.

An application with a server: a process that must keep running

A Node API, pages rendered on each request or a Docker service needs an environment that runs that process. Copying only the frontend files would leave that component behind.

Projects also offers backends and containers on a paid plan. Identify the start command, port, environment variables and persistent storage requirements before choosing it. A directory named dist does not, by itself, prove that your application is static.

If your project needs a server process, check its port, health, routes and memory with our original Node and Docker example. The container test does not demonstrate a publicly hosted HTTPS service.

If your application uses Prisma and PostgreSQL, review how to apply production migrations and check your data before moving the backend. Deploying code does not copy records from your local database.

A frontend with an external backend: keep its dependencies

A static website can use another service for login, file storage or data. Moving the frontend does not remove those dependencies. Review allowed authentication redirect URLs, permitted domains and variables for the new deployment.

If login breaks after changing domains

Update the site URL and the allowed destinations in your authentication provider. With OAuth, also check that the exact provider callback URL is allowed in the social provider’s console: your app’s return URL and the provider’s callback URL serve different roles. For example, Supabase recommends an exact production path, while Auth0 checks callback URLs against its allowlist. With Firebase, check the authorized domain and the authDomain used by its redirect flow (Firebase documentation).

Keep production and preview domains separate, and restrict wildcard rules to environments you control. Then use a private browser window to test sign-up, the OAuth callback, sign-out, password recovery and any confirmation links your app uses. Open a protected route directly and reload it too. If the flow returns to localhost, shows a callback error or loses the session, inspect the URL sent by the browser and the provider configuration; do not expose secrets while debugging.

For Lovable, inspect your specific project’s architecture before exporting it: projects do not all follow the same deployment path. Its hosting and ownership documentation explains the options. PostgreSQL alone does not replace Supabase authentication, storage and functions. If you built the app with Bolt or Replit, see our guides to moving Bolt Cloud to another host and hosting a Replit project elsewhere.

What to check before choosing a plan

1. List every component: frontend, server, data, login, files and third-party services.
2. Confirm a compatible destination for each component and calculate the total cost.
3. Check plans and limits. Activating Dev requires a card; custom domains and continuously running services have different conditions from free static deployment. Domain registration and renewal are billed separately.
4. Keep private credentials out of browser-delivered code and your repository.
5. After deployment, test on another device: open an internal route directly, then test login, forms and files where applicable.

For a project using the Git workflow, see Projects. For WordPress and web-hosting applications, see Sites. If you are unsure about the architecture, contact Hostbrid with your framework, backend and dependencies. Do not send passwords or private keys.

If you are choosing between managed web hosting and system access, compare shared hosting and VPS by runtime, control and the maintenance you can take on.

If your project uses WordPress, static files do not replace its database or media. Use the WordPress migration diagnostic to check SQL, uploads and URLs before choosing the destination.