AI NewsProductivityAnnouncement

CogSend is a self-hosted social scheduler for five platforms, running on your own Cloudflare account

CogSend is a self-hosted social media scheduler for Mastodon, Bluesky, LinkedIn, Threads and X, running on your own Cloudflare account with your own provider credentials.

AI News

Editorial2 min read

LinkedInX
The CogSend GitHub repository page

Image: GitHub

Why it mattersA founder or marketer can post to five networks from one draft, keep the credentials in their own Cloudflare account, and pay only what Workers, D1 and R2 charge.

A founder posting the same update to Mastodon, Bluesky, LinkedIn, Threads and X has, until this week, been paying a monthly fee to Buffer, Hypefury or a similar tool for that job, or copying and pasting the draft five times. CogSend, an MIT-licensed project that appeared on GitHub trending on 2026-09-24 with 127 stars in seven days, gives them a third choice: run the scheduler on their own Cloudflare account.

The project's README on GitHub describes CogSend as "self-hosted social scheduler for Mastodon, Bluesky, LinkedIn, Threads and X. Write a draft, customize it per platform, then publish it now or schedule it." The single-tenant design means one admin account per install, running against the operator's own Cloudflare account and their own social-network credentials.

What the editor does

The thread editor is one card per post, with images and alt text, and one Global tab plus a tab for each platform the user has selected. Pasting a long draft splits it into a thread that fits the tightest of the selected platforms, and the character count follows each platform's own rules, including graphemes and Mastodon's URL weighting. URLs in a post get link preview cards.

A post can be published immediately with per-destination results, or scheduled. From the Posts view, a scheduled post can be cancelled, rescheduled or retried, and a failed post backs off on its own for five attempts before parking in Failed. An Insights view shows published against failed over 7, 30 or 90 days, per-account stats and the reasons posts failed.

Where the data lives

Everything sits on the operator's Cloudflare account: the Worker runs the app, D1 stores the posts, and R2 stores the images. The README notes that R2 asks for a payment method on file even on the free tier. Credentials for connected accounts are encrypted at rest with AES-256-GCM, and the single admin account is protected by two-factor authentication.

The setup script is one command after the clone, and asks for a Node 22.12 or later runtime. Losing the password or the authenticator later is recoverable through an admin:reset command run from the local checkout, which the README documents. Updates run through deploy:release, and the operator's data stays in D1 and R2 rather than in the checkout, so a git pull cannot touch it.

A tool worth watching, with an install cost to weigh

CogSend is one person's project, published in September 2026, and 127 stars in seven days is early traction rather than proof at scale. A team that already pays for Buffer or Typefully gets a working answer for something like the cost of the underlying Cloudflare services, plus the time to set it up and keep it running. A team without a Cloudflare account, or without anyone comfortable running a Worker, is better served by the paid tools.

The interesting choice here is architectural: because the app is single-tenant and lives on the operator's Cloudflare account, the credentials for LinkedIn, X and the rest never sit on someone else's server. That is the trade a self-hosted scheduler exists to make.

Source

SourceGitHub

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX