SMF·POSTIZ
Can a prompt replace Postiz?
Social media — social scheduling
Exhibit tracking slip
Verdict
The core scheduling loop — compose, queue, publish on a schedule — is a real one-sitting build for networks with open, developer-friendly APIs like Mastodon, Bluesky, and Telegram. What isn't one-sitting is the reason schedulers exist as a product at all: platform-approved OAuth apps for Instagram, LinkedIn, TikTok, and X are approval-gated or paid, and keeping dozens of integrations alive as platforms change their policies is permanent, ongoing maintenance. Postiz is also genuinely open source, so for the full feature set, self-hosting it directly is the more honest move than rebuilding a smaller version.
Exhibit A — The prompt
Received on30.07.2026Build a personal social post scheduler for a couple of networks with open, stable APIs — Mastodon and Bluesky are both good candidates, and a Telegram channel via a bot token is a reasonable third. A compose view with image attachment and a slot-based queue: define posting times per weekday and new posts fill the next free slot, or pin a post to an exact time. A background job on a short interval publishes anything due, marking each post as sending before the network call completes so a crash never double-posts, retrying failures a few times with backoff. Show a per-network character counter, since limits differ, and keep a history of recently sent posts linking to the live post.
Do not build support for Instagram, LinkedIn, TikTok, or X — their APIs are approval-gated or paid for third-party tools, and the README should say so plainly rather than half-building broken integrations. Skip analytics, team features, and AI content generation entirely; if the full multi-network feature set genuinely matters, self-hosting the real, open-source Postiz is the honest move instead of rebuilding a smaller version of it.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 dozens of maintained channel integrations
- B.2 pre-approved OAuth apps for platforms that gate third-party posting
- B.3 per-network post previews and analytics
- B.4 team collaboration
Prior art
Exhibit C — Why people still pay: social API/integration upkeep
The hosted version ships with platform-approved OAuth apps already in place, so connecting Instagram, LinkedIn, or TikTok is a click instead of a developer-app review process — and social APIs change their terms constantly, so paying outsources that ongoing upkeep.
Questions
Can I import my existing Postiz queue?
Since Postiz is open source, its own database schema is inspectable, and a determined export is possible — but there's no built-in one-click export. For most personal use, recreating an active queue by hand is faster than writing a migration script.
Will it work on my phone?
The compose page works in a phone browser, but there's no dedicated app and no push notification if a post fails — check the history page to confirm a post actually went out.
What does it cost to run?
Hosting and a database, typically a few dollars a month — the social APIs themselves are free for personal-volume posting on the networks this build targets.
What's the one thing that doesn't survive the rebuild?
Broad platform coverage. The hosted product's real value is dozens of pre-approved integrations, including the platforms that actively resist third-party posting; this build only ever covers the handful of networks with genuinely open APIs.
Related tools
Receipt