Can I vibecode Zernio?
price $6/moyou'd save $72/yrbuild time not a true replacement; consolation build in a weekendcategory social-mediareplaced by 0 people
NOT REALLY
MOATintegrationscompliance regulatoryscale infra
Developer API for 15+ social platforms plus messaging infra: WhatsApp, SMS, RCS, voice calls, and provisionable phone numbers
The Build Prompt
copy it and go buildready to paste · 1,621 chars
Build me a personal social publishing API to replace Zernio. Requirements: - Node + Fastify + better-sqlite3, single API key from .env, runs on my always-on box. - Adapters ONLY for networks that hand out credentials on signup: Bluesky (app password via @atproto/api), Mastodon (access token), Telegram channel (bot token), Discord (webhook URL), Reddit (script app). One small adapter file per network so a sixth is addable later; scaffold nothing I don't use. - POST /posts accepts text, image URLs, scheduledFor (ISO, my timezone), and a list of target accounts; media is downloaded once to media/ and checked for type and size before the post is accepted. - A node-cron tick every minute publishes due posts: mark a row as sending before publishing so nothing ever double-posts, per-target status, 3 retries with backoff, partial failures don't block other targets. - GET /posts and GET /posts/:id return queue state and per-network permalinks; a plain localhost page lists the queue and recent failures. - Optional webhook: POST to a URL from .env on published and failed. - Binds to localhost only. No accounts, no telemetry. - Out of scope: the approval-gated networks (Instagram, TikTok, LinkedIn, Threads, YouTube, Pinterest), DMs, comments, analytics, and ads. Skip anything that needs a phone number (WhatsApp, SMS, calls): numbers, carrier access, and KYC cannot be vibecoded. - README: how to get each credential (Bluesky app password, Mastodon token, Telegram bot via BotFather, Reddit script app), plus an honest note that the closed networks need app review or paid API tiers.
What you lose
- ✕publishing to approval-gated networks at all (Instagram, TikTok, LinkedIn, Threads, YouTube) without your own reviewed apps
- ✕token lifecycle handling: refresh, revocation detection, reconnect flows across 15 networks
- ✕platform error remediation, retry logic, and rate-limit cooldowns that keep queues alive
- ✕the media pipeline: per-platform validation, compression, transcoding, re-hosting
- ✕the entire messaging stack: phone numbers provisioned per country with KYC handled, WhatsApp Business templates and broadcasts, SMS, RCS, and voice calling
- ✕everything else beyond posting: unified DM/comment/review inbox, contacts, analytics, ads APIs, conversion tracking
Prior art / alternatives
Why it still works
Approved platform apps and their review processes gate the social side; phone numbers, carrier contracts, and per-country KYC gate the messaging side. Ongoing multi-network API maintenance is the tax on both.