workbench/postbot

postbot

My own social post scheduler, so I stop renting one. Queue a post once and it goes out to each channel on time, after I approve it.

StatusIn Development
TimelineOct 2026 — present
TechnologiesTypeScript · Cloudflare Workers · D1 · R2 · MCP
ReplacesBuffer · Software you own
Build clock
  1. Started, plan written Oct 31, 2026
  2. First post published by postbot not yet
  3. Buffer cancelled not yet

Overview

postbot is the social post scheduler I’m building to replace Buffer for GVX Digital. I started it on October 31, 2026. For now I’m its only user. It’s also the showcase for Software you own: the part of a rented tool I actually use, built around how I work and kept.

Challenge

Schedulers like Buffer charge per channel, so each new account I post from raises the monthly bill. Everything a scheduler does for me can run on the Cloudflare account I already pay for.

Solution

The plan is one Cloudflare Worker with a queue page, an API and an MCP server, so I can schedule from a browser, a script or an AI agent. A job runs every minute, publishes whatever is due, and retries on its own when a platform has a bad moment. If a post fails, I get one email about it.

One rule is built in: nothing posts without my OK. Posts an agent writes start as drafts and wait for me to press Approve, and editing an approved post clears the approval.

Current status

In development, started October 31, 2026. The build clock above logs each milestone with the date it actually happened; it’s done when I cancel Buffer. Bluesky, X, LinkedIn and Threads are the planned channels.

Vision

A scheduler I own, that costs close to nothing to run, and that an agent can help with while I still decide what goes out.

← All projects