Social media decision
Post Bridge
The core loop (compose, queue, cron tick, publish) is one-shottable for networks with open APIs like Bluesky, Mastodon, and Telegram. What you cannot one-shot is the reason Post Bridge exists: one-click posting to TikTok, Instagram, YouTube, Facebook, Threads, Pinterest, LinkedIn, and Google Business Profile. Those APIs are approval-gated behind Meta App Review, TikTok's Content Posting API, YouTube quota, and business verification, which as an individual you often can't even qualify for. On top of that sits per-platform video transcoding, constant token-refresh babysitting, and an API plus MCP server so an agent can post for you. You can vibecode a personal cross-poster for the open networks in a sitting; you cannot vibecode the approvals.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Compose posts into a slot-based queue, publish on schedule to open-API networks via per-network adapters, and log outcomes, with a push-to-post-by-hand fallback for the approval-gated platforms.
What it still won’t have
- one-click connect to approval-gated platforms (TikTok, Instagram, YouTube, Facebook, Threads, Pinterest, LinkedIn, Google Business Profile)
- pre-approved platform OAuth apps you often can't obtain as an individual
- per-platform video transcoding and format handling
- token-refresh babysitting as platforms expire and change policies
- the hosted API and MCP server that lets a coding agent post for you
What remains hard
- Integration maintenance
First-year cost
The build hours below are a category default, not an estimate for this product. Change them to your own numbers and the comparison follows.
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build me a personal social post scheduler to replace Post Bridge. Requirements: - Node + Express + better-sqlite3; a localhost page with a compose box, image/video attach, and the queue ordered by send time. - Targets with open APIs only: Bluesky (app password via @atproto/api), Mastodon (access token), and a Telegram channel (bot token). Creds in .env, one small adapter file per network so a fourth is addable later. - For the approval-gated platforms people actually want (TikTok, Instagram, YouTube, Facebook, Threads, Pinterest, LinkedIn), do NOT fight their APIs: at post time send me an ntfy.sh push with the caption and media path so I can post by hand in a minute. Say clearly in the README that these need approved developer apps and business verification you cannot one-shot. - Slot-based queue: I define posting times per weekday in my timezone and new posts fill the next free slot; a post can also be pinned to an exact datetime or duplicated across networks with per-network text and counts. - A node-cron tick every minute publishes due posts, marks each row sent or failed, retries failures 3 times with backoff, and marks before sending so nothing double-posts. - Attached media stored in media/ next to the database, images resized per network with sharp. - A history page of the last 100 sent posts linking to the live posts. - Runs on my always-on box; localhost only, no accounts, no telemetry. - Out of scope: cross-network analytics, teams, and per-platform video transcoding. - README: getting a Bluesky app password, a Mastodon token, and a Telegram bot token, plus an honest note that social APIs drift and this needs occasional patching.
