postqueen vs Sendible

postqueen is open source and built for AI agents to drive: the same account is reachable from a calendar, a CLI, a REST API and a built-in MCP server, and you can run the whole thing yourself. Agency-first social media management with client dashboards and a white label option. Which one fits depends on whether you want to automate publishing or manage it in a dashboard.

postqueen is. It is AGPL-3.0 licensed, the code that touches your accounts is public, and self-hosting is free with a Docker image or a Helm chart. Sendible is a hosted product, so the database, the OAuth tokens and the publishing history stay on their infrastructure.

postqueen publishes to 30 channels and Sendible covers 10 of the ones we track. The number matters less than the overlap: list the networks you actually post to, then check both against that list rather than against each other.

postqueen ships a built-in MCP server, a CLI on npm, a REST API, a Node SDK and an n8n node, so Claude Code, ChatGPT, Codex, Cursor, OpenClaw and Hermes can all drive it. Sendible has a public API you could build against, but no MCP server or CLI, so the agent integration is something you would write and maintain yourself.

postqueen cloud plans run from $20 to $99 a month with unlimited posts on every plan, four or five months free on yearly billing, and a 7-day free trial. Self-hosting is free. Sendible: tiered plans priced by users and connected profiles, starting around $29 per month, with agency and white label tiers costing considerably more. Prices move, so confirm both before deciding.

Plan for the reconnection, not the export. Scheduled posts rarely migrate between tools, so someone re-enters the queue by hand, and every channel needs its OAuth connection made again. The part worth checking first is whether Sendible lets you take your analytics history with you, because that is the piece that is gone for good if it does not.