Can Postiz be vibe coded?
Social media scheduler for 28+ channels with AI assistance and team features
The core loop (compose, queue, cron tick, publish) is one-shottable for networks with open APIs like Mastodon, Bluesky, and Telegram. What you cannot one-shot is the reason schedulers exist as products: OAuth apps for Instagram, LinkedIn, TikTok, and X are approval-gated or paid, and keeping 28+ integrations alive as platforms change policies is permanent maintenance. Postiz is also fully open source, so the honest DIY move for the full feature set is self-hosting it rather than rebuilding it.
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 open-API networks via per-network adapters, and log outcomes.
- 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
- 28+ maintained channel integrations
- pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok)
- per-network post previews
- analytics
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- Permissions, presence, and shared workflows are difficult to simplify.
Why people still pay
The hosted version ships with platform-approved OAuth apps, so connecting Instagram, LinkedIn, or TikTok is a click instead of a developer-app review process. Social APIs break and change terms constantly; paying outsources that upkeep plus analytics, teams, and AI features.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
Permissions, presence, and shared workflows are difficult to simplify.
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 Postiz
Context
**Postiz** — Social media scheduler for 28+ channels with AI assistance and team features. It currently costs $29/mo.
The core loop (compose, queue, cron tick, publish) is one-shottable for networks with open APIs like Mastodon, Bluesky, and Telegram. What you cannot one-shot is the reason schedulers exist as products: OAuth apps for Instagram, LinkedIn, TikTok, and X are approval-gated or paid, and keeping 28+ integrations alive as platforms change policies is permanent maintenance. Postiz is also fully open source, so the honest DIY move for the full feature set is self-hosting it rather than rebuilding it.
This brief describes a focused, single-operator replacement for the part of Postiz 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 open-API networks via per-network adapters, and log outcomes.
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 Postiz. Requirements:
Node + Express + better-sqlite3; a localhost page with a compose box,
image attach, and the queue ordered by send time.
Three targets: Mastodon (access token), Bluesky (app password via
@atproto/api), and a Telegram channel (bot token). Creds in .env, one
small adapter file per network so a fourth is addable later.
Slot-based queueing: 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.
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 ever double-posts.
Per-network character counter in the composer; attached images stored
in media/ next to the database, resized to each network's limits 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: Instagram, LinkedIn, TikTok, and X (approval-gated or
paid APIs, say so in the README), analytics, teams, and AI features.
README: getting a Mastodon token, a Bluesky app password, and a
Telegram bot token.
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:
28+ maintained channel integrations.
Pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok).
Per-network post previews.
Analytics.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
Permissions, presence, and shared workflows are difficult to simplify.
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 (open source)](https://github.com/gitroomhq/postiz-app) — The app itself is AGPL open source and self-hostable, which is the shortest path to the full feature set
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/postiz
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 Postiz be vibe coded?
Partly, if you narrow it. The core loop (compose, queue, cron tick, publish) is one-shottable for networks with open APIs like Mastodon, Bluesky, and Telegram. What you cannot one-shot is the reason schedulers exist as products: OAuth apps for Instagram, LinkedIn, TikTok, and X are approval-gated or paid, and keeping 28+ integrations alive as platforms change policies is permanent maintenance. Postiz is also fully open source, so the honest DIY move for the full feature set is self-hosting it rather than rebuilding it.
What can an AI coding agent reproduce from Postiz?
Compose posts into a slot-based queue, publish them on schedule to open-API networks via per-network adapters, and log outcomes. 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 Postiz replacement still be missing?
28+ maintained channel integrations; pre-approved platform OAuth apps (Instagram, LinkedIn, TikTok); per-network post previews; analytics; Connectors, OAuth flows, and vendor API changes require constant upkeep.; Permissions, presence, and shared workflows are difficult to simplify.
What do I still own after building a Postiz 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.