Social mediaCAN I VIBECODE
Postiz?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Postiz is an open-source (AGPL-3.0) social media scheduling and management platform, self-hostable or cloud-hosted, built by gitroomhq (repo created 2023, ~35k GitHub stars). It connects 30+ networks (X, LinkedIn, Instagram, TikTok, YouTube, Reddit, Discord, Bluesky, Mastodon, WordPress), lets users compose once, cross-post with per-platform previews, and schedule via a visual calendar. Distinctive features: evergreen repeating posts; a built-in AI agent that drafts platform-tuned copy (hooks, captions, hashtags), generates images via a Canva-like editor, and short videos, with tiered monthly allowances (Standard 20 images/3 videos up to Ultimate 500/60); agentic control via CLI and an MCP server exposing ~8 tools so Claude/ChatGPT/Cursor/Codex can list channels and schedule posts; automation via public API, n8n, Make, Zapier; analytics (impressions, likes, comments, shares, engagement);
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for Postiz, the open-source agentic social media scheduler. Core workflow: a user connects social accounts via OAuth, composes one post, previews and tweaks it per channel, and schedules it on a visual calendar; evergreen posts repeat on a cadence; an AI agent drafts platform-tuned copy and images; an MCP/CLI surface lets external agents list channels and schedule posts; analytics and team collaboration round it out.
User-facing requirements: (1) connect at least 5 networks (X, LinkedIn, Instagram, Bluesky, Mastodon) via OAuth; (2) unified composer with per-channel preview/edit and cross-posting; (3) calendar view with draft/scheduled/published states and recurring posts; (4) AI assistant for platform-aware copy (tone, hashtags) and image generation with per-plan monthly allowances; (5) analytics dashboard (impressions, engagement); (6) team workspace with roles and comments; (7) automation via REST API and webhooks.
Technical requirements: Next.js (React) frontend, NestJS backend, PostgreSQL via Prisma, a job queue (BullMQ or Temporal) for scheduled publishing, encrypted OAuth token storage, an MCP server exposing tools (list channels, get platform schema, schedule post, generate image), a CLI wrapper, and Docker Compose for self-hosting.
Implementation approach: pnpm monorepo; queue-driven publisher with per-platform adapters; drafts and schedule persisted in DB; provider-agnostic AI client with rate limits and usage caps.
Do not copy Postiz branding, logo, marketing copy, or UI layout; use original naming and a distinct visual design. Out of scope: video generation, auto-like/auto-comment bots, post marketplace, mobile apps, multi-tenant billing. Deliver a README covering setup (env vars, OAuth app creation, Docker), architecture, and known limitations (platform API rate limits, OAuth refresh, AI cost).