# Flaghand vs Postiz for posting with AI agents

Postiz and Flaghand both let an AI agent (Claude, ChatGPT, Claude Code, Cursor or your own) draft your posts through an
API or an MCP server. The difference that matters is who can make a post go live. A Postiz API key acts as you and can
publish. A Flaghand agent token can't.

Every Postiz fact here comes from Postiz's own [pricing page](https://postiz.com/pricing),
[documentation](https://docs.postiz.com/mcp/introduction) and
[source repository](https://github.com/gitroomhq/postiz-app), read on October 25, 2026. Prices and features change, so
check them before you choose.

## The short answer

- **Choose Postiz** for open source and self-hosting, many more networks, AI images and video, or a team and clients
  working in one place.
- **Choose Flaghand** if your agent writes the posts and you want a rule the server enforces: nothing goes out until you
  approve the exact post with your passkey.

## Where Postiz is better

- **It's open source.** The code is on GitHub under the AGPL-3.0 license. Self-hosted, it has no plan limits ("every
  install behaves as the top tier") and runs on your own infrastructure; you register each network's developer app
  yourself. Flaghand is closed source and hosted only.
- **Many more networks.** Its docs list 34 platforms, among them X, LinkedIn and LinkedIn Pages, Instagram, Facebook,
  Threads, TikTok, YouTube, Pinterest, Reddit, Bluesky and Mastodon. Flaghand posts to X and LinkedIn personal profiles.
- **AI media built in.** AI images and videos, and clipping long YouTube videos into captioned vertical clips, with
  monthly allowances on each cloud plan.
- **Teams and clients.** Unlimited team members from the Team plan up, client groups, and preview links clients can
  comment on without an account.
- **A public CLI.** `npm install -g postiz`, beside the API, webhooks and an MCP server with 13 tools, on every cloud
  plan. Flaghand has no public CLI package; agents use its API or its hosted MCP server.

## Prices

Postiz Cloud has four plans: Standard $29 a month (5 channels, no team members), Team $39 (10 channels), Pro $49 (30) and
Ultimate $99 (100). Every plan has unlimited posts, and yearly billing costs less. Each plan starts with a 7-day free
trial that needs a card; Postiz authorizes it and releases the hold. There's no free cloud plan, and self-hosting the
open-source code needs no subscription.

Flaghand has no free plan, and it's in early access: sign-up isn't open yet.

## Who can publish

Postiz's developer settings say an API key acts as you. Creating a post takes a `type` of `now` (publish at once),
`schedule` or `draft`, and the MCP server's `schedulePostTool` can "Schedule, draft, or immediately publish posts".
OAuth tokens "work the same way as API keys" on every Public API endpoint, and neither expires: you rotate the key or
revoke the app. Postiz's documentation, read on October 25, 2026, describes no key or token limited to drafts. An agent
that holds your Postiz key can publish.

Flaghand doesn't hand an agent that power. No API token scope can approve, schedule or post, on any plan. Those routes
refuse every token and accept only an owner of the workspace, signed in with a passkey. Apps that connect to Flaghand's MCP
server by OAuth, such as Claude and ChatGPT, get a draft-only token: `read`, `drafts`, `media` and `request-approval`.

## What you approve

Postiz's review flow is to save posts as drafts, send a preview link, read the comments, then schedule the posts
yourself. Its docs are plain about the limit: "Approval is a conversation, not a state: there is no 'approved' flag that
blocks publishing." The preview link isn't password protected.

In Flaghand, approval is a state the server enforces. The agent checks its drafts and asks you to approve them.
Approving freezes each post into a snapshot: the account, the time, the text, every media file and its alt text, and the
exact request that will be sent. Flaghand hashes it with SHA-256 and records your passkey signature over the hash.
Nothing posts without that signature. Changing the text, media, account or time needs a new approval, and the scheduler
checks the signed snapshot again right before posting.

## After it posts

Flaghand reads each X post back and compares it with what you approved: normalized text, author, hidden reply mentions,
media count, available alt text, reply chain and quote. It doesn't verify link destinations or the media files
themselves, and LinkedIn posts aren't read back. Postiz's documentation, read on October 25, 2026, describes no
comparison like this.

## Side by side

| | Postiz | Flaghand |
|---|---|---|
| Source | Open source (AGPL-3.0): self-host it or use Postiz Cloud | Closed source, hosted |
| Free option | Self-hosting; Postiz Cloud has a 7-day trial | No free plan |
| Paid plans | $29, $39, $49 or $99 a month, less billed yearly | Early access; sign-up isn't open yet |
| Networks | 34, including Instagram, TikTok and YouTube | X and LinkedIn personal profiles |
| Agent access | API, CLI, MCP (13 tools), webhooks | API, MCP (OAuth or API token), agent skill, webhooks |
| Can the agent's credential publish? | Yes: API keys and OAuth tokens act as you | No, on any plan |
| Approval | Preview links for comments; no approved state blocks publishing | Your passkey signature over the exact post |
| Check after posting | Not described in the docs | X: text, mentions, media count, alt text, thread and quote. LinkedIn: none |

## Moving your posts over

Flaghand's [migration recipe](https://app.flaghand.com/docs/agents#migrate-from-another-scheduler) reads Postiz's public API: its post
list and saved create requests. The list has only top-level posts, without their media or thread replies, so add those
before you import; the importer warns about it every time. An agent with read access to Postiz can read your
queued posts and create them in Flaghand. From a saved file, `flaghand import FILE --dry-run` shows what it would
create, and the same command without `--dry-run` creates it (the CLI isn't on npm yet). Either way it only creates
drafts: nothing is approved or scheduled, Postiz's dates come over as proposed times, and Postiz keeps posting its queue
until you change it there.

## Try Flaghand

The [agent documentation](https://app.flaghand.com/docs/agents) covers the API and the MCP server.
[How to let an AI agent post on social media safely](/docs/guides/let-an-ai-agent-post-safely) has nine checks to run on
any tool, this one included. [Get access to Flaghand](/schedule).

[All guides](/docs/guides.md)