[verdict][curated prompt][source: zernio.com]
Can I vibecode Zernio?
// the value is the network, the data or the infrastructure
The scheduler is the easy 10 percent and an agent can build it in a sitting. The other 90 percent is approval-gated: Instagram, TikTok, LinkedIn, Threads, YouTube, and Pinterest publishing all require a reviewed developer app (Meta App Review, TikTok audit, LinkedIn partner access), and X's API starts at $200/mo. Past the gate, the real product is upkeep: OAuth token refresh and revocation handling across 15 networks, per-platform media validation and transcoding, rate-limit cooldowns, and error remediation when platforms change behavior. Then there is the half that is not software at all: Zernio provisions real phone numbers across dozens of countries and runs WhatsApp Business, SMS, RCS, and voice calling on them, which means carrier relationships, per-country regulatory documents, and Meta business verification. No coding agent can conjure a phone number or pass KYC for you. Add the rest of the surface (unified DM/comment inbox, analytics, ads management across six ad platforms) and this is infra plus compliance, not a weekend of code.
confidence: high
what it is: Developer API for 15+ social platforms plus messaging infra: WhatsApp, SMS, RCS, voice calls, and provisionable phone numbers
Buildability index · an editorial game
- Price from 6 $ · usage-based weight: plus 1
- Time not a true replacement; consolation build in a weekend weight: minus 1
- Category social media no weight
- Moat integrations · compliance and regulation · infrastructure scale weight: minus 5
- Confidence high weight: plus 1
- What you lose 6 items weight: minus 3
- Site zernio.com (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Expose a small REST API that accepts a post with media and a schedule time, queues it, and publishes to networks with open APIs (Bluesky, Mastodon, Telegram, Discord, Reddit) with retries and per-target status.
what you need
- reviewed developer app per closed platform (Meta App Review, TikTok audit, LinkedIn partner program, Pinterest; X API paid tier)
- OAuth flows plus token storage, refresh, and revocation handling
- hosted scheduler, database, and job queue
- media storage with per-platform validation and transcoding
- webhook receivers for platform callbacks
- for messaging: WhatsApp Business API access, phone numbers with per-country KYC, and SMS/voice carrier contracts (or reselling Twilio, the kind of subscription you were replacing)
API infra play: the code is replaceable; the platform approvals, phone numbers, and carrier compliance are not.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
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.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
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
Why people still pay
You are not paying for scheduling code, you are paying for two things code cannot get you. First, publishing through someone else's approved platform apps without going through six app reviews yourself, plus the long tail those approvals unlock: DM and comment inboxes, analytics, ads creation and reporting across Meta, Google, TikTok, LinkedIn, Pinterest, and X. Second, telecom: phone numbers provisioned in dozens of countries with regulatory paperwork handled, running WhatsApp Business with templates and broadcasts, SMS, RCS, and voice calls behind the same REST API. Ironically its main buyers are vibe coders: people who build their own app in a weekend and mount Zernio for the parts that cannot be vibecoded.
moat: Integrations Compliance and regulation Infrastructure scale what a moat is
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.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Postiz (opens in a new tab) — Open-source social scheduler with an API; still requires bringing your own approved platform apps. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
