Who this is for

Four shapes of the same problem: more accounts than attention.

Running several brands

A workspace per brand, unlimited channels in each. Compose once, adjust per network, publish to all of them from one screen. Because pricing is per workspace, connecting the seventh account to a brand costs nothing — which is the opposite of how per-channel pricing works.

An agency with client accounts

Keep each client in its own workspace so nothing crosses over: a workspace API key can only ever act on its own workspace, enforced in the API rather than in the UI. Delivery receipts give you something to show a client when they ask whether a post went out.

Automating from your own code

Everything the dashboard does is a REST call. Post from CI when a release ships, from a cron job on a schedule, or from an export hook when a video renders. See the API, or the CLI.

Handing it to an agent

The MCP server exposes your channels as tools, so Claude can draft, queue and report back without scraping a UI. The workspace key scopes it to one brand, so an agent cannot reach further than you intended. See the MCP server.

Where it is a poor fit

If what you need is social listening, an engagement inbox or follower analytics, PostWharf does not do those and is not planning to. It publishes.