Fixes arrive the way your stack accepts them.
What can be delivered, and how honestly it can be verified, depends entirely on what your platform lets a third party write. That constraint is real, so it is the organising idea here rather than a footnote.
Read this first. The connectors below are not built. The delivery model is real and is what the product is designed around, but today the only thing you can run without granting any access is the free scorecard: Mode E on the ladder. Every page below carries its status, and none of them describes a connector you can authorise this afternoon.
The five delivery modes
Every platform lands on one of these rungs, and the verification label follows the rung rather than the marketing.
| Mode | What we get | How changes arrive | Verification | Status |
|---|---|---|---|---|
| A · Repo write | A connected repository we can push a branch to | Opens a pull request. You review the diff and merge it. | Build-verified | Not built yet |
| B · Read-only repo | Read access, plus somewhere to push | Pushes to a fork or a branch you own. | Build-verified | Not built yet |
| C · Cloud mirror | A one-time snapshot or export | Works on a clone in our cloud, returns a patch or a PR. | Build-verified (mirror) | Not built yet |
| D · CMS drafts | OAuth into a hosted CMS | Writes unpublished drafts. You publish them. | Preview-verified | Not built yet |
| E · URL only | Nothing: a public URL | A scorecard and a patch you apply yourself. | Advisory only | Available now |
Build-verified means a build actually ran. It applies to modes A, B and C and to nothing else. A hosted CMS has no build to run, so mode D is preview-verified and mode E is advisory. Those labels are never blurred, because the honesty of the verification is the product.
Build
Drive scans and read findings programmatically.
Mode A Not built yet Next.jsFixes arrive as a pull request, built before you see it.
Mode A Not built yet WebhooksGet told when a scan finishes or a fix is ready.
Mode A Not built yet ZapierRoute scan results into whatever your team already uses.
Mode D Not built yetPlatforms
Changes land as unpublished drafts for you to publish.
Mode D Not built yet WebflowCMS collection items updated as drafts.
Mode D Not built yet ShopifyProduct and page metadata written through the Admin API.
Mode D Not built yet SquarespaceAdvisory only: a checklist you apply by hand.
Mode E Not built yet GhostPost metadata and content updated as drafts.
Mode D Not built yetMore platforms
Why a CMS is never build-verified
A repository can be compiled. A hosted CMS cannot. There is no build step to run, so there is nothing to verify against. A change written into WordPress or Webflow is checked in preview and labelled preview-verified, and it never carries the build-verified badge.
This is the distinction the whole ladder exists to preserve. Blurring it would make the badge meaningless everywhere, including where it is earned.
Platforms with no content-write API
Squarespace, Framer and Unicorn Platform have no supported way for a third party to write page content or metadata. They sit on Mode E, and the findings arrive as instructions you apply in the editor. Claiming otherwise would be inventing a capability, and those pages say so plainly rather than implying a connector is coming.