What shipped, and when.

The homepage has a new Multiplayer panel showing people and agents working on the same website at once, each request on its own branch and every action attributed, and the Website Governance page opens with three short truths about why building is cheap now and scaling it is the job.

Two new questions in the Knowledge Center cover working in parallel and what keeps an agent inside its request, and a new post, Governance is speed, makes the case that reviews remove redo rather than adding delay.

Teams that want an AI-native website but still run on a CMS can now have the Dispatch migration team, with partner agencies, assess the site, recommend the framework, host, and content model, rebuild it pixel for pixel, and hand it back connected to Dispatch with approvals on. Scoped, fixed quotes for most business sites; a paid assessment is credited against the migration.

The offer has its own page with the options table, the five-step process, recent migrations by type, and a quote form, and the homepage carries a new panel for it under How it works.

Dispatch now finds work instead of waiting for it. Every governed page is re-crawled on a schedule you set per site, with a score history kept per page, and a finding opens whenever a check that used to pass now fails, a score drops, a page stops answering, or a page falls out of the sitemap. Each finding carries a drafted change request, so the fix arrives already written.

The Inbox is the page where that work waits for you: requests with a preview ready for your approval, findings with a drafted fix, pages that slipped since the last crawl, and the work you have in flight. Approvers land on it after login; operators land on requests; owners on the overview.

Autonomy levels let a site auto-approve low-risk requests on the record, with the policy named as the actor and restore one click away. Slack and email alerts now carry what changed, the page, the risk tier, and the next step. A note-to-request box on every page drafts a request with the page context attached, and the agency handoff playbook is public.

Every question in the Knowledge Center now has its own indexable page, and a free tool scores any public URL for answer-engine readiness with the same checks Dispatch runs on governed pages.

Approval records are stored as a structured history, and the rule that a high-risk request needs two distinct approvers is enforced in the database rather than in the interface. Login, signup, and contact are rate-limited durably; restores carry the full commit identity and check ancestry before they run.

The homepage shows the most recent governed changes to this website, live, as proof the loop runs on our own site.

Separation of duties is now a database rule: the person who filed a request cannot approve it, and high-risk requests require a second approver, whatever the interface shows. Invite links are bound to the invited email and validated on the server.

Every response carries a standard set of security headers, and every change to Dispatch runs lint, type checks, tests, and a production build before it can merge.

The automatic link between an agent's commits and the request that asked for them was rebuilt and verified in production.

Deploys on Cloudflare Workers are tracked by a scheduled poll, so a site hosted there gets the same build history as one on Vercel or Netlify. Every outbound call Dispatch makes now has a timeout, so a slow provider can never hold a request transition.

The data layer is fully typed end to end, every website action validates its input, and the marketing site gained per-post social images, a metadata helper that keeps canonicals consistent, and a lighter blog index.

dispatchvault.com moved to a dark-first design: black stages alternating with white and grey panels, a single accent reserved for buttons and highlighted phrases, and a navigation bar that stays out of the way while you read.

The copy rules that govern the site are now in force everywhere: no invented proof, sentence-case headlines, and the same category line, the management layer for AI-powered websites, in every title and description.

When a request reaches preview-ready, is sent back, is approved, or goes live, Dispatch posts to a Slack channel you choose and emails the organization's approvers. Each message links to the preview and to the request.

Slack delivery uses an incoming webhook per site, validated before it is stored, and notifications are queued and retried so a slow channel never blocks the change that triggered them.

Plans are now counted in governed websites: one on Free, three on Starter, ten on Team, unlimited on Enterprise. The governed loop, previews, approvals, attribution, and restore, is free on one site by design; safety is never paywalled, and scale and enforcement are what the paid tiers add.

Sites hosted on Cloudflare Workers can now be governed alongside sites on Vercel and Netlify. Builds appear in the activity feed with branch and commit metadata, agent attribution, and automatic linking to the request that asked for them.

The same day, two flagship solution pages went live for marketing teams and agencies, and the product page for Website Governance walks through a governed change end to end.

Commits, pull requests, and preview deploys now attach themselves to the request that asked for them, and the request advances to preview-ready on its own. Approval stays with a person.

A request can be filed as a GitHub issue, and every request carries a risk tier: low, standard, or high. High-risk requests require a second approver, and the tier is written into the agent's instructions.

The Activity page lists recent versions of a governed site, and an owner or admin can restore to any of them. The restore is a new commit that preserves history, so the mistake and the recovery both stay on the record.

Signup gained bot protection after a run of automated registrations, and the first agency client site was onboarded with two design directions delivered as live preview links.

Write what should change in plain language. Dispatch turns it into a scoped handoff for your coding agent, carrying the organization's approved context, then previews the result, gates approval by role, and records the change when it goes live.

The marketing site, blog, and FAQs were rewritten around the category Dispatch occupies: the management layer for AI-powered websites.