The management layer for AI-powered websites

Let AI scale your website,
without losing control.

Dispatch gives marketing teams the visibility, context, approvals and control they need to operate a website built and managed by AI.

No credit card needed ✦ Free plan available

In production

Governing live sites for real businesses

Hours, not weeks

From plain-language request to live

Safe by design

Every change previewed, approved, reversible

No lock-in

Your code, repo, and hosting stay yours

The shift

Your CMS is holding back what AI can do.

Traditional CMS platforms solved a real problem: structure, permissions, publishing controls, and a safe interface for the whole team. But AI coding agents now produce the work itself: building pages, improving content, and making sitewide changes directly against modern website code. Move beyond the limitations of your CMS without giving up the visibility, control, and governance your team depends on.

The CMS model

Idea
Brief
Designer
Developer
CMS
QA
Publish

The AI-powered model

Intent
AI builds
Preview
Review
Approve
Live

AI removed the production bottleneck. Dispatch provides the management layer.

How a governed change works

From request to live with every step on the record.

This isn’t a concept. It’s the loop running in production on real business websites today, shown here exactly as it works.

01

Request in plain language

“Update the footer tagline to our new positioning line.”

Standard riskContext attached

Anyone on the team describes the change. Dispatch turns it into a scoped, rule-bound handoff for the AI agent, carrying your approved brand context.

02

The agent does the work

dispatch/req-28b8544e
Commit pushedPR #14 linked

Any coding agent executes the handoff. Commits and pull requests link themselves to the request as the work happens.

03

Preview attaches automatically

Preview readyAuto-attached

preview-req-28b8544e.example.app

Every change produces a live preview before production. The link lands on the request the moment the deploy finishes.

04

Send it back, or approve it

Approve changeApprover: Owner

Requesters can’t approve their own high-risk work.

Not right? Send it back with a note and the agent's instructions regenerate with your revision. Right? Role-gated approval, recorded. High-risk changes require a second approver.

05

Live, on the record

LiveCycle time: 4h 06m

The change ships. Who asked, what context governed it, who approved, what shipped, and how long it took: all permanent, all human-readable.

06

Undo, any time

Restore this versionHistory preserved

One click restores the site to any prior version. Nothing is deleted; the mistake and the recovery both stay on the record.

Run your website like a team, even when AI does the work.

Dispatch gives marketing teams the visibility, context, approvals and control they need to operate a website built and managed by AI.

See

Every page, change, deployment, and open request in one feed. AI changes are attributed to the agent that made them; humans to what they requested and approved.

Direct

Write the change in plain language. Dispatch turns it into a scoped agent handoff carrying your approved brand context.

Review

Every change produces a live preview before production, attached to its request automatically. Not right? Send it back with a note.

Approve

Role-gated sign-off recorded on every change. High-risk changes require a second approver, enforced by the system.

Know

A permanent record of who asked, what context governed the work, who approved, what shipped, and how long it took.

Undo

Restore the site to any prior version in one click. Nothing is deleted; the mistake and the recovery both stay on the record.

The composer

Plain language in. Governed instructions out.

Nobody on your team writes agent prompts. They write what they want, in their own words. Dispatch composes the handoff: scoped to the request, bound by your rules, and carrying your approved brand voice and messaging automatically, so the output stays on brand.

  • Revisions carry forward: send a change back with a note and the instructions regenerate with your feedback built in.
  • Risk tiers shape the work: low, standard, or high. High-risk changes, like pricing and legal claims, require a second approver, enforced by the system rather than a policy document.
  • Works with any coding agent. The handoff is the contract; Claude Code, Codex, or whatever your team runs executes it.

Your request

“Refresh the pricing page FAQ to mention the new annual plan. Keep our usual tone.”

## Agent handoff · req-7c21e0d4

SCOPE: pricing page FAQ only. No other files.

CONTEXT: approved brand voice v3, pricing messaging (auto-attached)

RISK TIER: HIGH (pricing content). Second approver required before this change can go live.

RULES: preview before production. Mark the commit with its request so it links back automatically.

The safety net

The undo button for your website.

Speed is only trustworthy when it’s reversible. Every version of your site stays restorable: pick any point in its history and bring it back with one click, at 5pm on a Friday, without calling a developer.

Restores preserve history rather than rewriting it. The mistake and the recovery both stay on the permanent record, which is exactly what your next audit, handover, or post-mortem needs.

Site versions
a41f09c

Homepage hero refresh

Today, 2:14 PM

Current
9b02d77

New case study published

Yesterday, 4:52 PM

Restore
5c88e12

Pricing FAQ update

Aug 24, 11:03 AM

Restore

The audience nobody designed for

Your next customers ask AI. AI reads your website first.

A growing share of your visitors aren’t human: AI crawlers and buying agents read, compare, and cite websites on your customers’ behalf. Dispatch scores every page 0–100 on answer-engine readiness, so “will AI recommend us?” becomes a number your team can improve instead of a mystery.

AEO readiness

/
96
/pricing
88
/blog/announcing-annual-plans
62

Titles, descriptions, structured data, and indexability, checked per page.

Machines reward depth and freshness

AI answer engines cite pages with extractable answers, accurate structured data, and content that's current today. Stale sites don't get recommended.

Only AI production can keep up

Being citable across the questions your buyers ask means more pages, kept fresher, than any manual workflow produces at a real-world budget.

Only governance makes that safe

High-cadence AI publishing without previews, approvals, and undo is a brand risk. With them, it's a growth engine.

Use the best tool for the work. Dispatch stays above it.

Dispatch doesn't replace your coding agent, repository, or hosting platform. It gives your organization a consistent management and governance layer across them, whichever you choose, today or next year.

As the agents and infrastructure get better, your website gets better. Dispatch makes sure your organization stays in charge of what they do.

Management layerDispatch
Coding agents
Claude CodeCodexGemini
Frameworks
Next.jsAstro
Version control
GitHub
Hosting & deploys
VercelNetlifyCloudflare

The company brain

The knowledge base your AI tools remember from.

Assistant memory lives inside each tool and each person's account. Your team uses ChatGPT, Claude, Gemini, and Grok, and none of them share what they know. Dispatch is the knowledge base the company owns: approved brand voice, messaging, prompts, agents, and workflows in one governed place, served to every AI tool through a governed connection and fed into every website change automatically.

  • Brand voice and messaging
  • Company context and approved source materials
  • SOPs, playbooks, and image direction
  • Reusable prompt standards
Approved

Brand Voice

Approved

Messaging Framework

Approved

Product Details

Approved

Approved Claims

Approved

Image Style Guide

Approved

AI Usage SOP

Proof, not promises

Running in production on real business websites.

We run on it

Our own websites are governed by Dispatch

ZINC's sites were migrated off their CMS onto this exact stack. Every change we ship, including AI-authored ones, flows through the same feed, approvals, and restore path we sell. If the loop broke, we'd feel it first.

Real migrations

Businesses moved off their CMS in days

Law firms and consultancies rebuilt with pixel-level fidelity, SEO carried over and improved, and governance recording from the very first commit. One client got two full design directions as live preview links for their decision meeting.

The loop, timed

Request to live in a single sitting

A production change on a governed site went from plain-language request through a human revision cycle to approved and live in hours, not weeks. The full audit trail exists to show for it, and cycle time is displayed on every request.

AI-powered website questions, answered.

What is an AI-powered website?

An AI-powered website is a site whose day-to-day changes are produced by AI coding agents, like Claude Code, Codex, or Gemini, working directly against the site's real codebase, instead of by hand through a CMS. The tools to build and run a website this way already exist; Dispatch makes them manageable for your organization by adding the visibility, context, approvals, and history around every change.

What is the management layer for AI-powered websites?

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.

Is it safe to let AI change my production website?

It is safe when the same controls a CMS provided still exist: every change previewed before it ships, approvals owned by named roles, AI-authored work attributed to the agent that made it, and a restore path back to any prior version. Git-based sites make each of these stronger than most CMS workflows. What makes AI unsafe is not the agent; it is running one with no management layer around it.

Do I still need a CMS?

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. Keep the safety net; remove the dependency on the CMS.

How do I get started with website governance in Dispatch?

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.

More questions? Visit the Knowledge Center

Your website is ready for AI. Now your organization is too.

The tools to build and run your website with AI already exist. Dispatch makes them manageable for your organization.