Can PostFast be vibe coded?
Schedule and auto-publish to 11 social platforms, with analytics, approval workflows, an API, and an MCP server for AI agents
The core loop is the one every scheduler shares and it is genuinely one-shottable: a compose box, a slot queue, a cron tick, one adapter per network. Two things sit outside what a coding agent hands you in a session. The first is paperwork. Only Bluesky and Telegram give you working credentials on signup; the other nine of PostFast's eleven destinations wait behind Meta App Review for Instagram, Facebook, and Threads, a TikTok audit before an app may post publicly rather than to a private draft, YouTube's default 10,000-unit daily quota against 1,600 units per upload, approval flows at LinkedIn, Pinterest, and Google Business Profile, and X, where the free tier is capped tightly enough that real volume means paying. The second is video. Every platform enforces its own container, codec, aspect ratio, duration, and size rules, so anything past text and a JPEG turns into a transcode pipeline with somewhere to actually run the jobs and a retry story for the upload that dies at 90 percent. Build the text-and-image version for the two open networks in a sitting; the rest is review forms and a transcode queue.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Compose posts into a slot-based queue, publish them on schedule to the open-API networks via per-network adapters, and expose the same queue over MCP so a coding agent can schedule too.
- Draft, queue, and track content for the few networks you actually use.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- nine of the eleven destinations, which need app review or a paid API tier rather than more code
- pre-approved OAuth apps for Instagram, TikTok, YouTube, LinkedIn, Pinterest, and Google Business Profile
- the video pipeline: per-platform container, codec, aspect ratio, duration, and size rules, plus async processing and the retries for when a large upload fails partway
- token refresh and the steady patching as platform policies move
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- Reliability at the vendor's scale is an operations problem, not a prompt.
Why people still pay
Connecting Instagram or TikTok here is one click because the OAuth app behind it already passed Meta App Review, TikTok's audit, and Google's business verification, a process that takes weeks and that a solo builder often cannot qualify for at all. Video is the other half of the bill: each platform enforces its own container, codec, aspect ratio, duration, and size rules, so a working scheduler runs a real transcode pipeline with async jobs, retries, and honest failure states rather than one hopeful upload call. The subscription also absorbs the work that never finishes: tokens expiring, per-platform media rules changing, endpoints deprecating on someone else's schedule. Above that sits the part a rebuild would not reach anyway, which is cross-account analytics and follower history, approvals and workspaces for running client accounts, and an API plus MCP server so your agent schedules through it instead of you maintaining a poster forever.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
Reliability at the vendor's scale is an operations problem, not a prompt.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to PostFast
Context
**PostFast** — Schedule and auto-publish to 11 social platforms, with analytics, approval workflows, an API, and an MCP server for AI agents. It currently costs $33/mo.
The core loop is the one every scheduler shares and it is genuinely one-shottable: a compose box, a slot queue, a cron tick, one adapter per network. Two things sit outside what a coding agent hands you in a session. The first is paperwork. Only Bluesky and Telegram give you working credentials on signup; the other nine of PostFast's eleven destinations wait behind Meta App Review for Instagram, Facebook, and Threads, a TikTok audit before an app may post publicly rather than to a private draft, YouTube's default 10,000-unit daily quota against 1,600 units per upload, approval flows at LinkedIn, Pinterest, and Google Business Profile, and X, where the free tier is capped tightly enough that real volume means paying. The second is video. Every platform enforces its own container, codec, aspect ratio, duration, and size rules, so anything past text and a JPEG turns into a transcode pipeline with somewhere to actually run the jobs and a retry story for the upload that dies at 90 percent. Build the text-and-image version for the two open networks in a sitting; the rest is review forms and a transcode queue.
This brief describes a focused, single-operator replacement for the part of PostFast 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 them on schedule to the open-API networks via per-network adapters, and expose the same queue over MCP so a coding agent can schedule too.
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.
Ffmpeg and somewhere to run transcodes for anything past text and images.
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 scheduler my coding agent can drive, to replace PostFast. Requirements:
Node + Express + better-sqlite3 on my always-on box. Two interfaces over one core:
a localhost page (compose box, media attach, queue by send time) and a stdio MCP
server via @modelcontextprotocol/sdk with create_post, list_posts, and delete_post,
so Claude Code can schedule without me opening the page.
Open-API networks only: Bluesky (app password via @atproto/api), Mastodon (access
token), Telegram channel (bot token). One adapter file per network, creds in .env.
For the gated platforms (Instagram, TikTok, YouTube, Facebook, Threads, LinkedIn,
Pinterest, Google Business Profile) do not fight the APIs: at send time push me an
ntfy.sh alert with the caption and media path and I post by hand. The README says
plainly that these need reviewed developer apps, not more code.
Slot-based queue: posting times per weekday in my timezone, new posts take the next
free slot or pin to an exact datetime; one post fans out to several networks with
per-network text.
A node-cron tick every minute sends what is due, marks the row sending before it
calls anything so a crash never double-posts, retries 3 times with backoff, then
records sent or failed with the error.
Media in media/ beside the database, images resized per network with sharp. Video:
accept MP4 only and check duration, aspect ratio, and size against each network's
limits at attach time, rejecting with the limit in the message rather than fixing it.
A history page of the last 100 sends linking to the live posts.
Binds to localhost only. No accounts, no telemetry, everything stays on my box.
Out of scope: video transcoding, analytics, approval workflows, and workspaces.
Do not build auth.
README: Bluesky app password, Mastodon token, Telegram bot token, wiring the MCP
server into Claude Code, and a warning that social APIs drift and need 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:
Nine of the eleven destinations, which need app review or a paid API tier rather than more code.
Pre-approved OAuth apps for Instagram, TikTok, YouTube, LinkedIn, Pinterest, and Google Business Profile.
The video pipeline: per-platform container, codec, aspect ratio, duration, and size rules, plus async processing and the retries for when a large upload fails partway.
Token refresh and the steady patching as platform policies move.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
Reliability at the vendor's scale is an operations problem, not a prompt.
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) — AGPL social scheduler, self-hostable, covers the DIY core for the open-API networks
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/postfast
You still own the product
- 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.
Open-source prior art
Before you start
Can PostFast be vibe coded?
Partly, if you narrow it. The core loop is the one every scheduler shares and it is genuinely one-shottable: a compose box, a slot queue, a cron tick, one adapter per network. Two things sit outside what a coding agent hands you in a session. The first is paperwork. Only Bluesky and Telegram give you working credentials on signup; the other nine of PostFast's eleven destinations wait behind Meta App Review for Instagram, Facebook, and Threads, a TikTok audit before an app may post publicly rather than to a private draft, YouTube's default 10,000-unit daily quota against 1,600 units per upload, approval flows at LinkedIn, Pinterest, and Google Business Profile, and X, where the free tier is capped tightly enough that real volume means paying. The second is video. Every platform enforces its own container, codec, aspect ratio, duration, and size rules, so anything past text and a JPEG turns into a transcode pipeline with somewhere to actually run the jobs and a retry story for the upload that dies at 90 percent. Build the text-and-image version for the two open networks in a sitting; the rest is review forms and a transcode queue.
What can an AI coding agent reproduce from PostFast?
Compose posts into a slot-based queue, publish them on schedule to the open-API networks via per-network adapters, and expose the same queue over MCP so a coding agent can schedule too. Draft, queue, and track content for the few networks you actually use. A responsive interface with real empty, loading, success, and error states.
What will a DIY PostFast replacement still be missing?
nine of the eleven destinations, which need app review or a paid API tier rather than more code; pre-approved OAuth apps for Instagram, TikTok, YouTube, LinkedIn, Pinterest, and Google Business Profile; the video pipeline: per-platform container, codec, aspect ratio, duration, and size rules, plus async processing and the retries for when a large upload fails partway; token refresh and the steady patching as platform policies move; Connectors, OAuth flows, and vendor API changes require constant upkeep.; Reliability at the vendor's scale is an operations problem, not a prompt.
What do I still own after building a PostFast alternative?
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.