Start free. Scale as your websites do.

The management layer is the organization-facing system above your coding agent, repository, and hosting platform. It holds what those tools don't: who requested each change, what brand context governed it, who approved it, what it did to your pages, and how to undo it. Dispatch gives marketing teams the visibility, context, approvals and control they need to operate a website built and managed by AI.

Dispatch is agent- and host-agnostic. It works with any coding agent (Claude Code, Codex, Gemini, and whatever comes next), GitHub for version control, Sanity as a headless content backend where content lives outside git, and Vercel, Netlify, or Cloudflare for hosting and deploys. Approval alerts reach your team in Slack and by email. Because Dispatch sits above the execution tools rather than replacing them, every improvement they ship makes your setup better.

Connect your site's GitHub repository and your hosting platform (Vercel, Netlify, or Cloudflare) from the Websites section. Dispatch syncs your pages, scores each one for AEO readiness, and starts recording every commit, pull request, and deployment in the activity feed with attribution. From there, add your brand context and set roles so approvals are enforced from the first change.

Traditional CMS platforms solved a real problem: structure, permissions, publishing controls, and a safe interface for non-technical teams. AI changes how the work is produced: an agent can create pages, improve content, and make sitewide changes directly against modern website code. Dispatch preserves the CMS's safety net (visibility, approvals, roles, history) without constraining what AI can do. Where a site needs structured content outside the codebase, a headless content backend like Sanity stores it, and Dispatch governs those changes the same way. Keep the safety net; remove the dependency on the CMS.