Can I vibecode posterly?

What you build

A local API and compose queue that publishes to open-API networks on a schedule, with a caption endpoint an agent can call directly instead of a UI-only AI button.

what you need

• OAuth/API access per social network
• always-on box for the scheduler
• database
• media storage
• LLM API key for caption generation

Submitted by the maker. The agent-native MCP layer and learned voice are the honest moat, not just the OAuth approvals every scheduler shares.

The prompt

A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.

Build me a personal social scheduler an AI agent can drive, to replace posterly. Requirements:

- Node + Express + better-sqlite3, with both a localhost compose page and
  a small local HTTP API (list_slots, create_post, get_recent_posts) so a
  coding agent can call it directly instead of only a human using the UI.
- Three open-API targets: Mastodon (access token), Bluesky (app password
  via @atproto/api), and a Telegram channel (bot token). One adapter file
  per network so a fourth is addable later.
- A /caption endpoint: given a topic, call an LLM API (key in .env) with
  my last ~20 published posts as style examples, so drafts sound like me
  instead of a generic AI voice. Cache the examples so it's not refetching
  the DB on every call.
- Slot-based queue: posting times per weekday in my timezone, new posts
  fill the next free slot, or pin an exact datetime; duplicate a post
  across networks with per-network text.
- A node-cron tick every minute publishes due posts, marks each row sent
  or failed before sending (no double-posts), retries failures 3 times.
- Attached images in media/ next to the database, resized per network
  with sharp; a history page of the last 100 sent posts linking out.
- Runs on my always-on box; localhost only, no accounts, no telemetry.
- Out of scope: Instagram, LinkedIn, TikTok, Facebook, and Google Business
  Profile (approval-gated APIs, say so in the README), review management,
  client approvals, video transcoding, and analytics.
- README: getting a Mastodon token, a Bluesky app password, a Telegram
  bot token, and pointing a coding agent at the local API.

What you lose

• 18 maintained platform integrations, including approval-gated ones (Instagram, LinkedIn, TikTok, Facebook, Google Business Profile)
• a voice model trained on your actual post history and what performed well, not a static prompt template
• Google Business Profile review replies and photo management
• client approval portal and content-plan review for agencies managing multiple brands
• per-platform video/image transcoding tuned to each network's limits
• a hosted MCP server + REST API built for agents, not bolted on after the fact

Why people still pay

Anyone can wire an LLM to a caption box; keeping a voice model current against real engagement data, holding pre-approved OAuth apps for the platforms that gate access behind business verification, and exposing a stable MCP/API surface an agent can drive reliably are all ongoing work, not a one-time build. Agencies additionally pay for the client-review layer, which needs its own auth and approval state machine.

moat: Integrations Switching costs Collaboration what a moat is

agent-native API/MCP surface + learned brand voice + platform upkeep

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, self-hostable, covers much of the DIY core for open-API networks. (alive)

Do you agree?

Related apps

Postiz 29 $ KIND OF Post Bridge 29 $ KIND OF Buffer 6 $ KIND OF Later 25 $ KIND OF