Self-hosted social media schedulers, compared (2026)
The open-source social media schedulers you can self-host and that are still actively maintained in late 2026 are Postiz, Mixpost, TryPost, CogSend and pendpost. They come in three shapes. Postiz, Mixpost and TryPost are server apps with a database and a job queue, so you run them on a VPS that stays on. CogSend runs inside your own Cloudflare account, so you keep no machine running. pendpost is a single local process with no database; some platforms fire with your computer off, others need it running at the due time. Pick by which of those you are willing to operate.
I build pendpost, so read this with that in mind. Every fact about the other tools below comes from their own repos, docs and pricing pages, checked at the end of October 2026.
Which open-source social media schedulers can you self-host?
Five projects pass two tests: you can run them on infrastructure you control, and they shipped a release in 2026.
| Tool | License | Latest release (late Oct 2026) | Runs as | Networks | MCP server | Approval step |
|---|---|---|---|---|---|---|
| Postiz | AGPL-3.0 | v2.25.3, 24 Oct 2026 | Docker: app, Postgres, Redis, Temporal | 30+ | Yes, also self-hosted | None built in; requested in an open issue |
| Mixpost Lite | MIT | 2.6.0, 16 Mar 2026 | Docker: app, MySQL, Redis | Facebook Pages, X, Mastodon | No | No |
| Mixpost Pro | Paid, one-time license | Licensed builds, not on GitHub | Docker: app, MySQL, Redis | 12 networks listed | Yes | Yes, approval flow |
| TryPost | AGPL-3.0 | v2.0.0, 10 Oct 2026 | Docker: app, Postgres, Redis, Caddy | 13 | Yes, plus a REST API | Yes, members submit and admins approve |
| CogSend | MIT | v1.20.2, 21 Oct 2026 | Your Cloudflare account: Workers, D1, R2 | Mastodon, Bluesky, LinkedIn, Threads, X | Yes | None found |
| pendpost | MIT | v2.8.0, 27 Oct 2026 | One Node process (npx, Docker or the macOS app), local JSON files | 9 social plus WordPress and Ghost, 4 more in beta | Yes, MCP-native | Yes, fail-closed by default |
Postiz is the incumbent here and the most mature: the widest network list, a large community, and the same core features on its cloud and self-hosted editions. It is a different shape from pendpost, a dashboard-first server app, and for many teams that is the right shape. pendpost vs Postiz covers the product differences in detail, and the Postiz alternatives page compares the wider field.
TryPost and CogSend are young. TryPost’s repo started in January 2026 and CogSend’s in September 2026, so weigh their pace against their track record.
What does each one need to run?
The server apps need a real host. pendpost and CogSend can start on a laptop or a Cloudflare account.
Postiz is the heaviest. Its docs put the floor at 2 GB of RAM and 2 vCPU for a light all-in-one install, and recommend 8 GB with 4 vCPU for a team of up to 20. It needs PostgreSQL 14 or newer, Redis 6 or newer, and Temporal, which has been required since v2.12.0 and ships in the official Compose file. The system requirements page has the full table.
Mixpost’s Docker guide runs the app with MySQL 8.0 and Redis, behind a domain whose A record points at the server. TryPost’s production Compose file pairs the app with Postgres 16, Redis 7 and Caddy for TLS. Neither project publishes a RAM figure that I could find.
CogSend has no server of yours at all. It deploys to Cloudflare Workers, with D1 for data and R2 for media. Its README says a single-admin instance normally stays within Cloudflare’s free plans (R2 still wants a payment method on file), and that on the free plan a backlog of due posts drains a post or two a minute.
pendpost is one zero-dependency Node process (Node 22 or newer) serving the dashboard and the MCP server on 127.0.0.1:8090. There is no database, because plans and state are JSON files. You start it with one command, the repo’s Docker Compose file, or the desktop app.
Does the machine have to be on when a post is due?
For the server apps, yes, for every platform: they publish from their own background workers (Temporal for Postiz, a Redis queue under Laravel Horizon for Mixpost and TryPost), and that is why you put them on a VPS. CogSend moves the clock to Cloudflare’s cron trigger, so nothing of yours has to be on.
pendpost is the odd one out, because it splits by platform. Where a platform’s API accepts a future publish time, pendpost hands the post over ahead of time and the platform fires it. Where it does not, pendpost publishes at the due time itself.
| Platform | How pendpost delivers | Fires with your computer off? |
|---|---|---|
| YouTube | Native: the API’s status.publishAt, which only works on a private video |
Yes |
| Mastodon | Native: scheduled_at, which must be at least 5 minutes ahead |
Yes |
| WordPress | Native: status future, fired by wp-cron |
Yes |
| Ghost | Native: status scheduled |
Yes |
| At the due time (the publishing API has no scheduled-time field) | No | |
| Facebook, LinkedIn, X, Telegram, Discord, Nostr | At the due time | No |
The YouTube and Mastodon rules are in the YouTube videos resource and the Mastodon statuses API. Instagram’s content publishing guide leaves scheduling to your own app and caps accounts at 100 API-published posts in a moving 24 hours. The full matrix, including the beta lanes, is in the scheduling docs.
So if you only post to YouTube, Mastodon and a blog, a laptop that sleeps is fine. If Instagram or LinkedIn is in the mix, run pendpost on something that stays on: a small VPS, a Raspberry Pi or a NAS. Or pay for the optional 24/7 cloud, which sells uptime and nothing else.
How do you expose a self-hosted scheduler safely?
Keep the publish API off the public internet and put access control in front of it. A scheduler holds tokens that can post as you, so an open port is a real risk.
pendpost binds to loopback by default, and its Compose file maps the port to 127.0.0.1 only. The always-on guide recommends reaching it over Tailscale or a Cloudflare Tunnel with an Access policy, so the server never changes. On hosts that hand you a public URL (the repo has templates for Fly.io, Railway and Render), set a bearer token: the gate turns on only when you bind a non-loopback address and set the token. CogSend documents Cloudflare Access for the same job and turns on two-factor login for the admin account. The security page lists what pendpost does and does not expose.
What do you have to back up?
The database, the uploaded media, and the file that holds your secrets. How many moving parts that is differs a lot:
| Tool | What holds your data |
|---|---|
| Postiz | Postgres, the uploads volume, plus Temporal’s own Postgres |
| Mixpost | MySQL and the app’s storage |
| TryPost | Postgres and the storage volume |
| CogSend | D1 and R2 (its docs cover D1 Time Travel and exports) |
| pendpost | One folder: .env, config.json, state.json and data/ |
pendpost’s whole workspace is files, so a backup is a copy of one directory (architecture docs). With Docker, that is the pendpost-data volume plus your mounted .env. Encrypt the copy, because .env holds live tokens.
Do you still need your own developer apps?
Yes, for every tool on this list. Self-hosting means your instance talks to Meta, LinkedIn, X and the rest with credentials you register yourself. The Postiz README says it plainly: on the self-hosted edition you create your own developer app on each platform and go through its review, and Meta, YouTube and TikTok can take weeks. That applies to pendpost too, where each lane’s setup page walks you through it. CogSend offers a sponsor service as a shortcut for X, Threads, LinkedIn and Bluesky. Budget the time. Docker is the quick part. The app reviews are what take weeks.
Which one fits whom?
Pick Postiz if you want the most networks and a mature team dashboard, and give it a server with room for the heavier stack. Pick Mixpost Lite for a lean dashboard covering Facebook Pages, X and Mastodon; if you later need more networks or approvals, Mixpost Pro is a one-time license on the same stack.
TryPost fits a team that wants approvals and an agent API in one self-hosted tool, provided a project under a year old does not worry you. CogSend fits anyone who wants no server at all and posts to its five networks.
And pendpost fits the person who wants an AI agent to draft while a human approves, on their own machine, under MIT. I am obviously biased on that last one, so try it in mock mode with no credentials before you believe me.
For the wider field, including the hosted tools, see all alternatives or the social media MCP server comparison.
Frequently asked questions
What is the best self-hosted social media scheduler?
It depends on the shape you want. Postiz has the widest platform coverage and a mature dashboard. Mixpost Pro and TryPost suit teams that want approvals in a self-hosted dashboard. CogSend needs no server at all because it runs on Cloudflare. pendpost suits people who want an AI agent to draft while a human approves, on their own machine.
Can I self-host a social media scheduler for free?
Yes. Postiz (AGPL-3.0), TryPost (AGPL-3.0), Mixpost Lite (MIT), CogSend (MIT) and pendpost (MIT) are all free to self-host. You pay for whatever runs them, from nothing on a laptop to a small VPS. Mixpost's other networks, approvals and MCP server need its paid Pro license.
Does a self-hosted scheduler need to run 24/7?
A server app like Postiz, Mixpost or TryPost publishes from its own background workers, so it has to be running whenever a post is due. pendpost hands YouTube, Mastodon, WordPress and Ghost posts to the platform ahead of time, so those fire with your computer off; Instagram, Facebook, LinkedIn, X, Telegram, Discord and Nostr need pendpost running at the due time.
How much RAM does Postiz need?
Postiz's own docs list 2 GB of RAM and 2 vCPU as the floor for a light all-in-one install, and 8 GB with 4 vCPU as the recommendation for a team of up to 20 users. Building from source is the most memory-hungry step.
What should I back up on a self-hosted scheduler?
Back up the database, the uploaded media and the file that holds your secrets. For Postiz and TryPost that is Postgres plus the uploads volume, for Mixpost it is MySQL plus storage, for CogSend it is D1 and R2, and for pendpost it is one folder: .env, config.json, state.json and data/.
Sources
- Postiz on GitHub (gitroomhq/postiz-app)
- Postiz docs: system requirements
- Postiz feature request: approval workflow (issue #1758)
- Mixpost pricing and editions
- Mixpost Lite docs: install with Docker
- Mixpost Pro docs: install with Docker
- Mixpost Lite on GitHub (inovector/mixpost)
- TryPost on GitHub (trypostit/trypost)
- CogSend on GitHub (cogsend/cogsend)
- pendpost releases on GitHub
- Mastodon API: POST /api/v1/statuses (scheduled_at)
- YouTube Data API: videos resource (status.publishAt)
- Instagram Platform: content publishing
pendpost is free and open source. Try the whole draft, approve and publish loop in mock mode, with no real API calls.