The Lemmy scheduler that runs itself

A Lemmy post is a title plus an optional link or image and an optional Markdown body, and postqueen schedules all of it. Pick the community, write or generate the submission, choose the time and it publishes through your instance. Markdown from the composer, including headings, lists and links, arrives exactly as you wrote it.

No. Lemmy has no app registration to go through: you connect the regular account you already post from and tell postqueen which instance it lives on. Publishing then happens through that instance's HTTP API under your own username, so anything your account can do in a browser it can do from the queue.

Both. Select several Lemmy communities and postqueen files a separate submission in each one, which is exactly how a Lemmy cross-post works, and the same draft can also go to Reddit, Mastodon or any of the 30 supported channels with per-platform wording. Space multi-community posts out rather than firing them in the same second: instances rate limit new posts, and moderators notice a wall of identical submissions. Because Lemmy federates over ActivityPub, Mastodon accounts can already follow a Lemmy community and see the post without a second submission.

Yes. The built-in assistant drafts titles and Markdown bodies from a short prompt and rewrites anything you highlight, and nothing publishes until you schedule it. Keep it grounded and specific: Lemmy communities are small and read closely, so generated filler gets spotted fast. Agents like Claude Code or OpenClaw can prepare a whole queue through the MCP server.

postqueen keeps a full history of what it published, in which community and when, so you can compare communities and time slots. Scores and comment threads live on Lemmy itself, since the network has no central analytics dashboard and every instance holds its own copy of the data. Reading your queue history next to the discussion is what tells you which communities actually want your posts.

The usual causes are an expired login on your instance, a community that restricts posting to moderators, an instance rate limit rejecting the submission, or a title over the 200 character maximum. Instance downtime counts too, since a volunteer run server goes offline for maintenance more often than a large corporate API does. postqueen marks the post with the error it got back so you can fix the cause and retry.

Yes. postqueen is open source under AGPL-3.0 and ships as a Docker image, so you can run it next to your own instance and keep the whole pipeline on your hardware. Self-hosting is free, and the CLI, REST API, webhooks and MCP server work 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. If you would rather not depend on a hosted service at all, the open source version is free to self-host.