The Nostr scheduler that runs itself

Text notes, notes with images or video linked in, and multi-part threads that clients render as a proper reply chain. You compose once, pick the time, and postqueen broadcasts the event to your relays. Nostr has no upload server of its own, so media travels as a URL and clients unfurl it inline.

Neither exists on Nostr. There is no signup and no OAuth server to authorize against: your identity is a keypair, and every note has to carry a signature from your private key, which is why connecting Nostr looks nothing like connecting Instagram. Because signing needs that key, treat it like any other credential: plenty of people keep a separate key purely for automated posting, and self-hosting keeps it on a machine you own.

Yes. Short-form posts map cleanly across all four, so write once, select the networks and adjust the wording per platform before scheduling. Nostr sets no character limit while X still caps you, so the composer keeps a separate version for each. Every network gets a native post rather than a bridged copy pointing somewhere else.

Yes. The built-in assistant drafts and rewrites notes in your voice from a short prompt, and nothing goes out until you schedule it. Agents like OpenClaw or Claude Code can prepare and queue a whole batch through the CLI or the built-in MCP server.

postqueen records every note it published and when, so your own history is complete. Engagement is a different matter: reactions, reposts and zaps are themselves events scattered across relays, so any count depends on which relays you read from and no number is authoritative. That is a property of the protocol rather than a gap in the tool, and your client will show you as much as any dashboard honestly could.

Usually it published fine and the relay you are reading from does not have it. Relays go down, prune old events, and some refuse writes from keys they do not know or ask for payment first. Publishing to several relays is the fix: if one rejects the event the others still carry it, and postqueen marks a failed publish with the error it got back.

Yes, and it is a sensible default if you would rather your key never sit on someone else's server. postqueen is open source under AGPL-3.0 and runs from a Docker image on your own hardware, next to your own relay if you run one. Self-hosting is free, and the CLI, REST API, webhooks and MCP server behave exactly as they do on the cloud.

Yes. Every cloud plan starts with a 7-day free trial with unlimited posts, and you can cancel anytime. Self-hosting the open source version stays free either way.