Pot să vibecodez Outstand?

Ce construiești

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.

ce îți trebuie

• 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.

Promptul

Un weekend cu un agent de coding. Golurile care rămân sunt mai jos, la „ce pierzi”.

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.

Ce pierzi

• 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

De ce se plătește în continuare

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: Integrări ce e un moat

platform app review + integration upkeep

Alternative gratuite

N-ai chef să ți-o construiești? Astea există deja, sunt gratuite sau open source, și le-am verificat una câte una.

Cine l-a construit deja

Să pornești de aici e tot vibecoding: promptul e pentru când o vrei exact în felul tău.

• postiz-app (se deschide într-o filă nouă) — AGPL social scheduler with a public API and per-network adapters, self-hostable as a starting point (alive)
• mixpost (se deschide într-o filă nouă) — self-hosted social publishing app (Laravel) you point your own platform apps at (alive)

Ești de acord?

Aplicații similare

Post Bridge 29 $ CAM AȘA Postiz 29 $ CAM AȘA Buffer 6 $ CAM AȘA