# Build and host your own design or app from an AI editor

> Vibe-code a site in Cursor, Claude Code, Codex or ChatGPT and host it on Sitesfare: the editor creates an own-code site, puts the files, deploys — and can start from a template’s design kit.

Web page: https://sitesfare.com/guides/host-your-own-app-from-an-ai-editor
Part of: https://sitesfare.com/guides

## Steps at a glance

1. **Add AI editor access and the category’s tool.** Dashboard → AI editors → add access for the kind of website; the site also needs that category’s tool with a free website slot (the same rule as Bring your own code).
2. **Ask the editor to build it.** Describe the site. It can read a design kit (kit_get) for palette, type, motion and voice, then write a static site: HTML, CSS, JavaScript, images, fonts — no server code, no build step.
3. **The editor creates the site and puts the files.** app_create makes an own-code site on your sitesfare.app address; app_put_files stores the files as a draft (up to 500 files / 25 MB, index.html at the top).
4. **Deploy.** app_deploy publishes the stored version with HTTPS, analytics and SEO files. Your own domain connects under Domain & email.
5. **Iterate.** app_get_file reads a file back; app_put_files replaces it; app_deploy publishes again. Every version is in the site’s History.

Sitesfare is made for the sites and small apps people now build by talking to an AI editor. Describe what you want in Cursor, Claude Code, Codex, ChatGPT or Claude; the editor writes it and hosts it on Sitesfare — with HTTPS, analytics, SEO files and your own domain — without you touching a server.

## What you need

- **AI editor access** for the kind of website (Dashboard → AI editors), and your editor [connected to Sitesfare](/guides/connect-ai-editors).
- The **category's tool** with a free website slot — the same rule as [Bring your own code](/guides/bring-your-own-code). A ceramics studio site is a *designer* site; a SaaS landing page a *developer* site; a shop an *ecommerce* site.

## How it goes

1. **Ask.** *"Build a one-page site for my ceramics studio in the spirit of the Atelier kit — hero, three collections, a contact form — and host it on Sitesfare at claystudio."*
2. **The editor builds it.** It can read a template's design kit with `kit_get` (or download it with `kit_download`) for the palette, type, motion and voice, then write an original static site: HTML, CSS, JavaScript, images, fonts.
3. **It creates the site and puts the files.** `app_create` makes an own-code site at `claystudio.sitesfare.app`; `app_put_files` stores the files as a draft. Nothing is live yet.
4. **Deploy.** Say "deploy": `app_deploy` publishes the stored version. Sitesfare adds HTTPS, privacy-friendly analytics, `robots.txt` and `sitemap.xml`, and your Search Console verification.
5. **Iterate.** `app_get_file` reads a file back, `app_put_files` replaces it, `app_deploy` publishes again. Every version is in the site's **History**.

## What the site can contain

- `index.html` at the top; HTML, CSS, JavaScript, images (PNG, JPG, WebP, AVIF, GIF, SVG, ICO), fonts, video, audio, PDFs, JSON and XML.
- Up to **500 files** and **25 MB** in total, **5 MB** per file. Large photos and videos belong in your media library (`media_upload`).
- Clean addresses: `about/index.html` opens at `/about`; a `404.html` becomes the not-found page.

**Not supported:** server code (PHP, Python, Ruby, Go, Java, Node servers), `package.json`, lock files, framework sources (`.ts`, `.tsx`, `.jsx`), `Dockerfile`, `.env` files, executables or archives. Built with React, Vue, Astro, Hugo or similar? Have the editor run the build locally and put the output folder (`dist`, `build`, `out`) on the site.

## Starting from a design kit

Every template has a kit — concept, palette, typefaces, shape and motion tokens, the scene, the voice it ships with, and its section map. An editor reads it with `kit_get` (or the resource `sitesfare://kit/<template>`) and can download the official kit files with `kit_download`: `README.md`, `tokens.css` / `tokens.json`, `sections.json`, `samples.json`, the theme document, a `LICENSE.md` fingerprinted to your account, and `AGENTS.md` / `CLAUDE.md` / `.cursorrules` that tell any editor how to build in that spirit and where to host. You can also download kits under **AI editors → Design kits** in the dashboard.

The kit describes the design; the template's own code stays on Sitesfare. What the editor builds from a kit is original work in the template's spirit, hosted on Sitesfare.

## The hosting licence

Ask the editor to deploy the site to Vercel, Netlify, GitHub Pages or any other host and it declines and says why: Sitesfare designs, templates and kits, and the sites and apps built with them or hosted through Sitesfare Connect, are licensed for hosting on Sitesfare only. For a custom address, [connect your own domain](/guides/connect-your-own-domain).

## Troubleshooting

- **"This is not a ready-to-serve static website…"** — the files include server code or a build-time project file; the message lists them. Build first, then put the output.
- **"index.html was not found at the top"** — put the home page at `index.html`, not in a sub-folder.
- **"needs … tool with a free website slot"** — add the category's tool, or free a slot by deleting an unused site.
- **The editor refuses to deploy elsewhere** — by design; see the licence above.

## Questions

**What can the site contain?**
HTML, CSS, JavaScript, images, fonts, video, audio, PDFs, JSON and XML — up to 500 files and 25 MB (5 MB per file). Server code, package.json, framework sources and archives are refused: build first, then upload the output.

**Can I use a React, Vue, Astro or Hugo project?**
Yes — have the editor run the build locally and put the built output (dist, build or out) on the site.

**Can I take the site elsewhere later?**
Sites built with Sitesfare kits or hosted through Connect are licensed for hosting on Sitesfare only, and the editor is told so. You can connect your own domain to it at any time.

**Does it count as a website on my plan?**
Yes, like any own-code site: it uses a website slot of the category’s tool, and each deploy counts against the daily deploy allowance.