Why We Built It
Because an API Still
Needs a Cockpit
SyncDock gave WordPress a secure, headless API — hashed keys, HMAC signing, block-aware editing, all of it built for AI agents and automation pipelines calling in programmatically. But not every publishing job is automated. Someone still has to sit down, write a post, pick a featured image, and decide when it goes live — and doing that meant logging into wp-admin anyway, once per site, exactly the workflow SyncDock was built to route around.
Every team running more than a couple of WordPress sites hits the same wall: a browser full of tabs, each one a different login, each one the same clunky block editor, and no single view of what's scheduled where. Writing tools outside WordPress solved the drafting problem but created a new one — getting that content into WordPress cleanly, as real blocks, without a manual copy-paste-and-fix pass.
SyncDock Client is the cockpit for the API SyncDock already built. It authenticates against the same plugin, respects the same per-site keys, and adds the piece that was missing: a single browser console where writing, scheduling, AI drafting, SEO checks, and publishing all happen in one place, locked behind a PIN instead of a dozen separate passwords.
Console-First
One panel for every connected site, instead of a dozen wp-admin tabs.
Local-Only Security
AES-256-GCM encrypted keys, unlocked by a PIN your browser holds, not a server.
Block-Native
Markdown and HTML in, valid Gutenberg blocks out — no manual cleanup.
AI Optional, Never Required
Bring your own key if you want AI drafting; publish entirely manually if you don't.
Built to Scale Out
Unlimited connected sites with no per-seat pricing, from day one.
Built on SyncDock
Talks to the same free plugin and API that automation pipelines already use.