Website Governance
Connect your website’s repository and hosting, and every change, human or AI, becomes visible, reviewable, approvable, attributable, and reversible. This is the flagship of the management layer, and it runs in production today.
How a governed change works
This isn’t a concept. It’s the loop running in production on real business websites today, shown here exactly as it works.
“Update the footer tagline to our new positioning line.”
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.
Any coding agent executes the handoff. Commits and pull requests link themselves to the request as the work happens.
preview-req-28b8544e.example.app
Every change produces a live preview before production. The link lands on the request the moment the deploy finishes.
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.
The change ships. Who asked, what context governed it, who approved, what shipped, and how long it took: all permanent, all human-readable.
One click restores the site to any prior version. Nothing is deleted; the mistake and the recovery both stay on the record.
Dispatch gives marketing teams the visibility, context, approvals and control they need to operate a website built and managed by AI.
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.
Write the change in plain language. Dispatch turns it into a scoped agent handoff carrying your approved brand context.
Every change produces a live preview before production, attached to its request automatically. Not right? Send it back with a note.
Role-gated sign-off recorded on every change. High-risk changes require a second approver, enforced by the system.
A permanent record of who asked, what context governed the work, who approved, what shipped, and how long it took.
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
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.
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
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.
Homepage hero refresh
Today, 2:14 PM
New case study published
Yesterday, 4:52 PM
Pricing FAQ update
Aug 24, 11:03 AM
The audience nobody designed for
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
Titles, descriptions, structured data, and indexability, checked per page.
AI answer engines cite pages with extractable answers, accurate structured data, and content that's current today. Stale sites don't get recommended.
Being citable across the questions your buyers ask means more pages, kept fresher, than any manual workflow produces at a real-world budget.
High-cadence AI publishing without previews, approvals, and undo is a brand risk. With them, it's a growth engine.
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.
Dispatch connects to your site's repository and hosting platform. Every commit, pull request, and deployment appears in a live activity feed, with AI-authored changes attributed to the agent that made them. Pages are inventoried and scored for answer-engine readiness (AEO), and roles control who can request, approve, and publish. Dispatch governs the work; your coding agent, GitHub, and your hosting platform execute it.
A change starts as intent, a request written in plain language. Dispatch turns it into a scoped agent handoff, the agent produces the work on a branch, and the deploy platform builds a preview. The approver reviews the preview and either approves or sends it back with a revision note, which regenerates the agent's instructions on the same request. Roles are enforced so editors cannot approve their own work, and every decision is recorded next to the change it authorized.
You restore it in one click. Dispatch lists every prior version of your site, and an owner or admin can restore to any of them. A new commit puts the site back exactly as it was; nothing is deleted, and both the mistake and the recovery stay on the record. Deploy previews catch most problems before production; for anything that slips through, the activity feed shows exactly which change caused it and the Versions panel undoes it.
Coding agents sign their commits with attribution trailers: Claude Code, Codex, and Gemini all identify themselves in the commit message. Dispatch reads those trailers and badges each change in the activity feed with the agent that made it, alongside the human who requested and approved it. Attribution is what turns AI website work from a black box into an auditable record.
Dispatch is agent- and host-agnostic. It works with any coding agent (Claude Code, Codex, Gemini, and whatever comes next), GitHub for version control, and Vercel, Netlify, or Cloudflare for hosting and deploys. Because Dispatch sits above the execution tools rather than replacing them, every improvement they ship makes your setup better.
More questions? Visit the Knowledge Center
The tools to build and run your website with AI already exist. Dispatch makes them manageable for your organization.