Website Governance
Connect your repository and host, and every change, human or AI, becomes visible, approvable, and reversible. Dispatch finds what slipped and drafts the fix.
Site versions
Meta description on /about
9b02d77
Pricing FAQ: annual plan
a41f09c
New case study published
5c88e12
Nothing deleted, everything recorded
The hard part moved from writing code to deciding what ships, who approves it, and how it stays right.
Any agent can build a page this afternoon. That is no longer the advantage.
Brand, judgment, and taste live in your team and your approved context, not in the tool.
Reviews, roles, and a record are what let you say yes faster. Redoing the work is what slows you down.
This isn’t a concept. It’s the loop running in production on real business websites today, shown here exactly as it works. A request can start with a person, or with a finding Dispatch drafted on its own.
“Update the footer tagline to our new positioning line.”
Anyone on the team describes the change, or Dispatch drafts it from a finding on a governed page. Either way it becomes 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.
Proactive by default
Available todayAgents don’t wait to be prompted. Dispatch finds the work, drafts the fix, and puts it in front of the right person. You keep the approve moment.
Every governed page re-crawled on the cadence you set per site, with a score history you can read.
A failing check, a score drop, a crawl error, or an orphaned page opens a finding with the change request already written.
Let low-risk requests go live on the record, keep a second approver on high-risk work, and restore anything in one click.
Slack and email messages include what changed, the page, the risk tier, and the next step.
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.
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.
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
Platforms keep you by holding your site. Dispatch keeps you by being useful. Leave tomorrow and you take everything with you.
Code, content, and history live in your repository and your host, not in Dispatch. Switch Dispatch off and nothing about the live site changes.
Every change ships as a normal commit. Restore points, branches, and previews are yours whether or not Dispatch is watching.
Prompts, context, agents, workflows, documents, and the full request and approval record download from Settings as JSON and Markdown, any time.
Bring Claude Code, Codex, or Gemini today and something else next year. Dispatch governs the work; it never owns the tool.
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.
Quick answers on running a website that AI agents build and your team governs. More in the Knowledge Center.
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.
Add your website, connect the agent you already use, and run your first governed change today. Dispatch finds what’s next from there.