Getting started / Hosting & deploys

Hosting & deploys

The assistant doesn't host your site — it works with whatever you already have. This step is about one thing: how your site rebuilds when something changes.

When you're already covered

If your site rebuilds automatically when the repository changes (the default on Netlify, Vercel, Cloudflare Pages, Amplify and most CI pipelines), code changes deploy themselves — nothing to configure. Likewise, live-API CMSes like Sanity show published content immediately without any build.

Deploy hooks by provider

A build/deploy hook URL additionally lets the assistant trigger a rebuild directly when you ask it to. Where to create one:

Netlify — Site configuration → Build & deploy → Build hooks
Vercel — Settings → Git → Deploy hooks
Cloudflare Pages — Settings → Builds → Deploy hooks
AWS Amplify — App settings → Build settings → Incoming webhooks
Azure Static Web Apps — builds run via your repo's pipeline; no hook needed
Anything else — any https hook URL that starts a build works

The hook URL is stored encrypted like every other credential, and the assistant won't fire it on its own after code commits — commits already rebuild the site. It triggers a build only when you explicitly ask.

Static-build sites

If your site is statically built from CMS content (common with Contentful + a static site generator), make sure something rebuilds it when content publishes — either your CMS's own webhook into the host, or the deploy hook above. Publishing from the assistant then goes live after the rebuild, typically 1–2 minutes.

← Connect your repository Chat basics →