[verdict][curated prompt][source: outstand.so]
Can I vibecode Outstand?
// buildable in a weekend, but real gaps stay open
Writing your own posting service is a weekend build, and for the networks with open APIs (Bluesky, Mastodon, Telegram) it genuinely is: a queue, a cron tick, one adapter per network, done. The wall is not code. Instagram, TikTok, YouTube, LinkedIn, and Pinterest each require your own developer app and a platform review before they will accept a single post, X meters writes on a paid tier, and then eleven integrations keep changing under you: token refresh, media specs, rate-limit budgets, deprecated endpoints. You can build the API. You cannot one-shot permission to use it.
confidence: high
what it is: One API to post, schedule, and pull analytics across 11 social networks
Buildability index · an editorial game
- Price from 19 $ · usage-based weight: plus 2
- Time multi-day weight: plus 1
- Category developer tools no weight
- Moat integrations weight: minus 1
- Confidence high weight: plus 1
- What you lose 6 items weight: minus 3
- Site outstand.so (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Run a small self-hosted service that takes a post plus target accounts over HTTP, queues it, publishes on schedule through one adapter per network, and records per-account delivery status.
what you need
- your own developer app per social network
- paid X API tier for posting to X
- always-on box for the scheduler
- media storage
The rare entry where the moat is paperwork · the code is a weekend, the platform approvals are not.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a self-hosted unified posting API to replace Outstand. Requirements:
- Node + Fastify + better-sqlite3, one headless service on localhost:8080.
No web UI: my own apps are the only consumer, every key in .env.
- One normalized post shape in zod (text, media, targets, scheduledAt,
idempotencyKey) and one adapter per network mapping it onto that
platform's payload. Adapters export capabilities, publish, and metrics;
nothing platform-specific leaks into the core.
- A capability table per adapter (character limit, media count, mime types,
aspect ratios, max video seconds). POST /posts returns 422 naming which
target rejected what, before a single network call goes out.
- Ship the three networks that need no app review: Bluesky (@atproto/api),
Mastodon, Telegram. Adding a fourth must mean writing one adapter file
and touching nothing else.
- A token-bucket limiter per network seeded with their published limits so
calls queue instead of returning 429. POST /posts answers 202 with a job
id and a worker drains the queue.
- Idempotency: replaying a POST with the same idempotencyKey returns the
original job instead of posting twice, and every target gets its own
delivery row so partial success is readable.
- GET /posts/:id/analytics folds each platform's metrics into one shape
(impressions, likes, comments, shares) with null where a network does not
report a field. Never invent a number to fill a gap.
- An MCP server over stdio exposing create_post, list_accounts, and
get_analytics so Claude Code posts through it, plus an OpenAPI spec
generated from the zod schemas at /openapi.json.
- Out of scope: Instagram, TikTok, YouTube, LinkedIn, Pinterest. Each needs
my own developer app approved by the platform first, a review queue and
not code. Say that in the README next to the three token setups.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
- pre-approved platform apps for Instagram, TikTok, YouTube and LinkedIn
- eleven maintained integrations, kept alive as platforms change
- automatic token refresh and rate-limit queueing
- per-network media transcoding from a single upload
- cross-platform analytics in one shape
- the MCP server that hands all of it to an AI agent
Why people still pay
Every network you actually want is gated by someone else's approval queue. Getting an Instagram or TikTok app cleared to post takes review cycles and a real business case, and that is before you own token refresh, per-platform media specs, and rate limits for eleven APIs forever. Paying converts an approval problem and permanent maintenance into a bearer token, which is exactly the trade a developer shipping a product wants to make.
moat: Integrations what a moat is
platform app review + integration upkeep
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- Mixpost (si apre in una nuova scheda) — The free Lite edition covers three networks and a dashboard, not an 11-network posting API.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- postiz-app (opens in a new tab) — AGPL social scheduler with a public API and per-network adapters, self-hostable as a starting point (alive)
- mixpost (opens in a new tab) — self-hosted social publishing app (Laravel) you point your own platform apps at (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
