Can Post Bridge be vibe coded?

Build brief — a focused alternative to Post Bridge

**Verdict:** Partly, if you narrow it · **Buildability:** 67/100 · **Category:** Social Media

**Source:** https://www.canitbevibecoded.com/post-bridge

Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Post Bridge. Verify current pricing and capabilities before acting.

Context

**Post Bridge** — Schedule and cross-post to every major social network from one place, with an API and MCP server. It currently costs $29/mo.

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.

This brief describes a focused, single-operator replacement for the part of Post Bridge that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

What you are building

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.

Draft, queue, and track content for the few networks you actually use.

A responsive interface with real empty, loading, success, and error states.

Requirements

Functional

Always-on box for the scheduler.

Database.

Media storage.

Data and integrations

OAuth/API access per social network.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

Non-functional

Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.

Security: server-side secrets, validated input, and no credentials in the client bundle.

Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.

Portability: the operator can export their data and leave without losing it.

Implementation brief

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.

Delivery standard

Inspect the repository first, then write a short implementation plan before writing code.

Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.

Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.

Include responsive layouts plus genuine empty, loading, success, validation, and failure states.

Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.

Add structured logs around every external call and return actionable errors without leaking sensitive details.

Write unit tests for the core logic and one automated test of the main user journey.

Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

Acceptance criteria

A clean install starts the app using only the README and .env.example.

The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.

Invalid input, missing configuration, provider failure, and an empty database each have a usable state.

The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.

Tests, type checking, linting, and a production build all pass with no ignored failures.

No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

Non-goals

Do not build these, and do not claim to have replaced them:

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.

Connectors, OAuth flows, and vendor API changes require constant upkeep.

What you still own after launch

Secure credentials, rotate secrets, and handle provider rate limits.

Run migrations, backups, restores, and dependency updates.

Test the critical journey after every model, API, or hosting change.

Monitor failures and fix the edge cases a first prompt will miss.

Maintain every third-party integration as APIs and OAuth rules change.

Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

Prior art

Working open-source software you can read, fork, or borrow from before starting:

[Postiz](https://github.com/gitroomhq/postiz-app) — Open-source social scheduler, self-hostable, covers much of the DIY core for open-API networks

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/post-bridge