Updated: 3 hours ago
Make any AI project business-ready in one prompt. Try Wix Headless →

Hosting is easy to forget while you're building with AI, and then it's the only thing you're thinking about. The question shifts from "how do I build it?" to "where does it actually live?"
Getting your site online depends on what you built. A simple landing page can run on a free hosting plan, while an app with user accounts or a business site with payments and bookings needs additional services behind it. You can manage those services yourself or choose a platform that handles more of the setup for you.
Go from code to live site with Wix Headless. Upload or drag in your HTML, CSS and JavaScript files to get your site live with a shareable URL. Wix handles the hosting and infrastructure, and you can add ecommerce, bookings, CMS, payments and more with a single prompt.
TL;DR: how to host your AI-built site
An AI-generated website needs a host to serve its pages, plus a backend if visitors can buy, book appointments or read frequently updated content. Pick a host that fits how your project works, upload the right build, connect your domain and test everything before launch.
You'll learn:
Static vs dynamic websites and what each needs
Three approaches to hosting an AI-built website
Vercel, Netlify and Cloudflare Pages compared
Three ways to publish with Wix Headless
How to prepare your files, deploy updates and protect API keys
What to check before launch, including mobile performance and SEO
What kind of AI-built site do you have?
Before picking a host, it helps to know how your site works. Two questions cover most cases: does it need a server to run, and does it need business features behind it?
Static websites
A static website delivers prebuilt HTML, CSS, JavaScript and image files to the visitor's browser. Portfolios, landing pages and informational sites built with an AI website tool are often static.
Static sites can still include interactive features, such as contact forms or embedded booking tools, by connecting to other services. They're generally the simplest type of website to host.
Dynamic websites and apps
A dynamic website or web app does some of its work on a server, such as handling user accounts, personalizing content or retrieving information from a database. It needs a server that can run application code, such as Node.js or Python, or a managed backend service that provides those functions for you.
Business features
You can add ecommerce, bookings, payments and content management to either type of site. For example, a simple website can display products from an online store and let visitors book appointments by connecting to an external service.
Those services handle the work behind the scenes, such as processing payments or managing appointments. The important question is which services your site needs and who manages them.
Compare your AI website hosting options
There are three common approaches to hosting an AI-built site, and they aren't mutually exclusive.
Static describes how your site delivers content, managed describes who runs the hosting infrastructure, and headless describes how the frontend connects to the backend. The right combination depends on what you're building and how much control you want.
Approach | What it provides | Best for | What you need to manage |
Static hosting | Delivers prebuilt website files, with optional serverless functions | Landing pages, portfolios and frontend projects | Build files, deployment and any external services |
All-in-one website platform | Combines a website editor, hosting and built-in business features | Sites you want to build and manage in one platform | Content, design and business settings |
Headless hosting | Connects a custom frontend to a separate business backend | AI-built sites that need custom design and business functionality | Frontend development and, depending on the setup, hosting and authentication |
Learn more: What is web hosting?

What affects the cost of hosting an AI-built site?
The price depends on more than the hosting plan. Some providers charge based on traffic, bandwidth, serverless function usage or storage. You may also pay separately for a database, payment processing, a CMS or other services your site connects to.
Check the costs of these features together before choosing a setup, especially if you're building a site for a business. Comparing web hosting prices across providers helps you see what each plan includes.
Learn more:
Static hosting platforms compared
For static and frontend-heavy AI builds, developer platforms make deployment quick. Most connect to a GitHub repository and redeploy automatically each time you push a change.
Vercel
Vercel is particularly well suited to Next.js projects and also runs serverless functions. Its free Hobby plan is limited to personal, non-commercial use, so client and business sites need a paid Pro plan.
If a Hobby project reaches its free usage limits, Vercel pauses the relevant usage until the limit resets. Paid plans allow additional usage charges, with spending controls available to help manage costs.
Netlify
Netlify hosts static sites and frontend frameworks, and adds serverless functions, storage and database options. Its Free plan includes 300 credits per month, which cover several kinds of usage, such as deploys and bandwidth.
Once you reach that limit, your projects pause until the next billing cycle. Paid plans include more credits and offer optional automatic top-ups.
Cloudflare Pages
Cloudflare Pages hosts static websites on Cloudflare's global network. Requests for static files are free and unlimited, so it's a useful option for sites that don't need much server-side processing.
If you add server-side functions, those use Cloudflare Workers and have separate usage limits. The Free plan also allows up to 500 builds per month.
What these platforms don't include
These platforms focus on hosting and deploying your site rather than providing a complete business management system. You can connect payment providers, booking tools and other services through integrations or APIs, but you'll need to configure and manage those connections separately.
Learn more:
All-in-one managed hosting
This is managed hosting in its fullest form: the platform runs the infrastructure while you focus on content and customers. If you've been weighing website builder vs web hosting as separate decisions, all-in-one platforms combine them, since the builder and the host are the same product.
Convenience vs control
The main tradeoff is how much control you have over the frontend. With a traditional website builder, you create and edit your site inside the platform rather than managing a separate code project. In return, the platform handles hosting, infrastructure and the technical tasks of keeping your site online.
Wix is one example. It hosts sites on managed cloud infrastructure with a global CDN and automatic scaling. If you create a site with Wix's AI website builder, you can publish it directly from the Wix platform.
If you're comparing cloud infrastructure against cheaper shared servers, cloud hosting vs shared hosting breaks down the reliability and scalability differences.
Learn more: What is managed hosting?
Headless hosting explained
In a headless setup, your frontend (the part visitors see) is built and deployed separately from the backend that handles ecommerce, bookings, content and payments. The two connect through APIs, which let your frontend request information and services from the backend.
This means you can keep the website your AI tool built and connect it to features such as product catalogs, bookings and content management without rebuilding the frontend from scratch.
Wix Headless is one example. It connects your frontend to Wix business solutions, including ecommerce, bookings, events, a CMS and payments, which you manage from one dashboard instead of combining separate vendors.
Wix-managed vs self-managed headless
With Wix-managed Headless, Wix hosts and runs your frontend on its infrastructure, including a global CDN, automatic SSL and scaling. If you use Wix's recommended Astro setup, Wix also configures authentication and provides built-in SEO support.
You can also deploy other supported frameworks to Wix hosting. Wix still manages the hosting, but you configure authentication yourself and handle more of the SEO setup.
With self-managed Headless, you host your frontend with your own provider and manage deployment and authentication, while Wix provides the business backend and APIs.
Learn more:
How to host an AI-built website with Wix Headless
The steps depend on where your project is now: a finished set of static files, a project you're still building with an AI coding tool, or a frontend that already runs on another host.
Option 1: upload a finished static site
If your AI tool already produced a finished static site, you can publish it without installing anything.
If your site is plain HTML, CSS and JavaScript, you can upload those files as they are. If you built it with a framework such as React or Vite, run the project's build command first. This creates a folder with the finished website files, often named dist or build. Upload that folder, not the original project folder.
Go to Wix Headless Drop.
Drag your finished website folder or a ZIP file into the upload area. The upload can be up to 20MB in total.
Wait for Wix to upload and publish the site, then open the Wix URL it gives you to check it.
Log in or create a Wix account to save the project.
Add the business solutions you need, such as Wix Stores or Wix Bookings, and keep developing with an AI coding tool or the Wix CLI if you want to add functionality.
The upload publishes static files only. It doesn't deploy a server-side application or backend code. You can add Wix business features afterward, or keep developing the project locally and publish updates through the Wix CLI.
Learn more:
Option 2: build and deploy with an AI coding tool
If you're still building, you can work with Wix Headless from an AI coding tool such as Claude Code or Cursor.
Go to wix.com/headless and create a free account.
Open your AI coding tool, such as Claude Code or Cursor, and give it the Wix Headless skill (wix.com/headless/skill.md). This gives the AI instructions for connecting your project to Wix.
Describe the website you want to build and the business features it needs, such as product listings, bookings or member accounts.
Let the AI agent set up the project and connect the Wix services it needs. With the recommended Astro setup, Wix also configures authentication and provides built-in SEO support. Other supported frameworks require you to configure authentication yourself.
Preview your site, check that its features work and publish it to Wix hosting.
Manage business information such as products, bookings and content from your Wix dashboard. To change the design or frontend functionality, edit the code or ask your AI coding tool to make the changes.
You can also use the Wix CLI to preview and publish changes as you keep developing. With frameworks other than Astro, you build the project with that framework's own tools before releasing it.
"We wanted AI builders to be able to go from prototype to live product without context-switching into a completely different platform. With wix.com/headless/skill.md, you describe what you want to your AI tool of choice and you get a running site with the business layer already wired in. It's not a workaround, it's the intended path." - Tuvit Rubin Kaplan, Head of DevRel, Wix
Learn more:
Option 3: keep your own hosting (self-managed)
If your AI-built frontend is already deployed on Vercel, Netlify or another hosting provider, you don't have to move it to Wix. Self-managed Headless lets you keep your existing hosting and connect your site to Wix for business features.
Create a Wix Headless project and add the business solutions you want to use, such as Stores or Bookings.
Create a headless client for your site in the Wix dashboard. This sets up the connection between your frontend and Wix.
Set up OAuth authentication and your redirect settings. Login callbacks need exact authorization redirect URIs, while returns from Wix-hosted pages such as checkout use allowed redirect domains. If you added your frontend link during setup, Wix adds it to the allowed domains for you.
Connect your frontend to Wix using the JavaScript SDK or REST API, so your site can load products, bookings and CMS content.
Deploy your updated frontend through your existing hosting provider as usual.
What OAuth does
OAuth is a way for your website to connect to Wix securely and confirm who is making each request. You set it up once as part of the connection, then your site can use the Wix services you've enabled.
If your project uses private credentials, such as a client secret, keep them in server-side code or secure environment settings, never in browser JavaScript.
In this setup, Wix doesn't host your frontend. You stay responsible for deployment, authentication, frontend security and your own hosting account, while Wix runs the business backend.
"If you built your frontend on Cursor or Gemini, you don't need to move your project into a Wix editor. That's the whole point. You keep your stack, you keep your workflow, you just get a real backend behind it." - Gonen Jerbi, R&D Manager, Wix
Read more:
Connect business features to your AI-built site
Hosting your frontend doesn't automatically give your site business features. If you want visitors to buy products, book appointments, register for events or access regularly updated content, you need services that handle those tasks behind the scenes.
What Wix Headless connects to
You can connect each service separately through APIs, or use a backend that brings them together. Wix Headless connects your frontend to Wix business solutions, including:
Ecommerce: product catalogs, inventory, orders and checkout
Bookings: appointment scheduling and booking management
Events: event listings, ticketing and guest management
CMS: content collections your frontend retrieves through APIs
Payments: payment processing through supported payment providers
Learn more:
Who manages what
Each solution needs to be configured for your project. You manage business information from the Wix dashboard, while your frontend controls how the features appear to visitors. You can build those pages yourself or ask your AI tool to create them.
Learn more:
Connect a custom domain to your AI-built site
If you're unsure how domains and hosting relate, domain name and website hosting explains how they connect.
Register or connect a domain
There are two ways to put a domain on your site. You can register a new domain with Wix, or connect a domain you already own elsewhere by updating its DNS records.
DNS records tell browsers which server to contact when someone enters your domain. You don't need to transfer your domain to your hosting provider to connect it.
Point your domain to the right host
If Wix hosts your frontend, connect your custom domain to your Wix project by following the domain setup steps in your dashboard. If you host your frontend elsewhere, update your domain's DNS records to point to that hosting provider instead.
Your connection to the Wix backend is configured separately through its APIs, so your domain doesn't need to point to Wix for you to use Wix Headless.
DNS changes usually take effect within a few minutes to 48 hours, depending on your registrar, DNS caching and TTL settings. A Wix-managed site stays live at its Wix URL in the meantime.
Set up a professional email
One thing to sort before launch: email. If you want a professional address at your domain (e.g. hello@yoursite.com), does Wix provide email hosting? covers exactly what's available and what isn't.
Learn more:
SSL, CDN and auto-scaling explained
These three terms come up with every host. Here's what each one does and what Wix handles on Wix-hosted sites.
SSL certificates
SSL (the HTTPS padlock) encrypts the connection between your site and its visitors. Wix-hosted sites include a free SSL certificate that renews automatically once your domain is connected and verified.
If you host elsewhere, best free SSL certificate options and website hosting with free SSL compare what's available.
CDN (content delivery network)
A CDN (content delivery network) stores copies of your site's files on servers in different locations. When someone visits your site, those files can be delivered from a server closer to them, reducing loading time.
Wix's global CDN helps deliver content to visitors around the world, although actual load times also depend on your site's code, file sizes and network conditions.
Auto-scaling
Auto-scaling adjusts the hosting resources available to your site as traffic changes. If more people visit during a product launch or campaign, Wix manages the infrastructure needed to handle the increased demand, so you don't have to add servers or estimate capacity in advance.
Before you launch: files, security and testing
Deploy the right files
AI coding tools usually produce a project folder with source code, dependencies and configuration files, and that's not always what you upload. Plain HTML websites can usually be published by uploading their HTML, CSS, JavaScript and asset files directly.
If you built your site with a framework such as React or Vue, check how the project is configured. A static project usually needs to be built first. This creates an output folder, often named dist or build, containing the files your host needs to publish.
If your project uses server-side rendering or other server-dependent features, you'll need a host that supports those functions. Uploading a static build folder alone won't make those features work.
Set up automatic deploys from GitHub
Many AI coding tools can save your project to GitHub, a platform for storing and tracking code. Once you've connected your repository to a host such as Vercel, Netlify or Cloudflare Pages and configured automatic deployments, each push to the connected branch lets your host build and deploy the updated site.
GitHub tracks changes to your code, making it easier to review updates and restore an earlier version if something breaks. If you upload finished files directly instead, keep a copy of your original project files so you can make changes or restore the site later.
Keep API keys out of your frontend
AI-built websites often connect to external services, which may require API keys to work. Some keys are public and meant for browser code, but private keys must stay on the server.
Store private keys as environment variables in your hosting settings or a secure backend environment. Never hardcode them into frontend JavaScript or commit them to a public GitHub repository.
Also check your framework's configuration: variables with public prefixes, such as VITE_ or NEXT_PUBLIC_, are included in the code sent to browsers and should never contain secrets.
Protect user data
If your site collects user data, limit who can access admin areas, validate what users submit and keep your project's packages updated.
Test your live site
Once the site is live, run through a quick checklist:
Open every important page on the live URL
Check navigation, links, images and forms
Check that forms send information to the right place
Test on desktop and mobile
Confirm API connections and dynamic content load
Test login, registration and account permissions if your site has user accounts
Run checkout and booking flows in test mode
Check that HTTPS works and your domain resolves
A site can look fine on your computer and still load slowly on a phone. Test your live pages with Google PageSpeed Insights to check loading performance and Core Web Vitals, and pay attention to large images, unnecessary scripts and elements that delay the main content.
Prepare for search engines
Publishing your site doesn't guarantee that search engines will find or index it. Give each page a descriptive title and meta description, make sure search engines can access its content and submit your XML sitemap through Google Search Console.
Also check how your frontend delivers content. Some frameworks build pages in the browser after they load, while others send finished HTML from the server. Server-side rendering or prerendering can help search engines access your content more reliably.
Add canonical URLs when the same page is available at multiple addresses. If you're using Wix-managed Headless with Astro, Wix provides built-in SEO support. With other frameworks or self-managed hosting, you'll need to implement and maintain the relevant SEO elements yourself.
5 hosting mistakes AI builders make (and how to avoid them)
Choosing a host before understanding your project. A static hosting plan won't run every type of web application, and a managed business platform may be more than a simple portfolio needs. Check whether your site needs server-side processing, a database or business services before choosing, and see how to host a website for the basics.
Deploying the wrong folder. Uploading your original project files instead of the finished build can result in a blank page or a directory listing. Check your framework's deployment instructions and upload the correct output folder.
Exposing API keys. Private credentials in frontend code or a public GitHub repository can be copied and misused. Keep secret keys in server-side environment variables and check your code before publishing.
Ignoring free-plan limits. Hosting providers set different limits for bandwidth, builds, requests and commercial use. Check what happens when you reach your allowance and upgrade if your site needs more capacity.
Skipping launch testing. A site that looks correct in your AI preview may still have broken links, forms or mobile layouts after deployment. Test the live URL, including important user actions, before sharing it with customers.

How to host an AI-built website FAQ
Can I host an AI-built website for free?
Yes, you can host an AI-built website for free, within the limits of your hosting plan. Netlify and Cloudflare Pages offer free plans for hosting websites, while Vercel's free Hobby plan is limited to personal, non-commercial projects. Wix Headless also lets you create and test a project before upgrading. A paid Wix plan is required to connect a custom domain and accept payments, and some additional features may require an upgrade.
What’s the difference between static hosting and headless hosting?
Static hosting serves prebuilt website files, such as HTML, CSS and JavaScript, directly to visitors. Headless architecture separates the frontend from the backend, so you can build the customer-facing site independently and connect it to business services through APIs. A headless website can have a static frontend, a dynamic frontend or a combination of both.
Do I need coding skills to deploy an AI-built website?
Not always. Some platforms let you publish a website without writing code, and AI coding tools can help prepare and deploy more complex projects. However, you may still need to understand basic deployment steps, troubleshoot errors, configure authentication and check that API connections work. The more custom functionality your site has, the more technical setup it may require.
What is Wix Headless and how is it different from regular Wix?
Regular Wix combines the website editor, hosting and business features in one platform. Wix Headless separates the frontend from the backend. You build the frontend with your own code or an AI coding tool, then connect it to Wix business solutions such as ecommerce, bookings, events, a CMS and payments through APIs. This gives you more control over your frontend while Wix manages the business services behind it.
Can I keep my frontend on Vercel and still use Wix as a backend?
Yes. That's what self-managed Wix Headless is for. Your frontend stays on Vercel, Netlify, AWS or another host, and it connects to Wix business data through the Wix REST API or JavaScript SDK. You'll still need to configure the connection, authenticate requests, add the Wix API calls your frontend needs and keep your own hosting account active.

























