MARKDOWN IN,
POSTS EVERYWHERE.
Write once, publish everywhere. Your posts are files you own. No vendor lock-in.
LAUNCHING APRIL 21. NO_SPAM. JUST A LAUNCH NOTIFICATION.
THE_PROBLEM
PUBLISHING_IS_BROKENCOPY_PASTE_HELL
One post, six platforms. Each with different formatting, image sizes, and character limits. Every. Single. Time.
VENDOR_LOCK_IN
Your content lives in someone else's database. If the service shuts down, your publishing history vanishes.
$29/MONTH_FOR_A_QUEUE
Social scheduling tools charge a premium for basic functionality. You're paying rent on your own workflow.
NO_SOURCE_OF_TRUTH
Published a thread last March? Good luck finding the original. There's no single place where your content history lives.
FILES_YOU_OWN
Posts live as markdown files on your filesystem. No database lock-in. If Blurt disappears, your content doesn't.
SYSTEM_OF_RECORD
After publishing, permalinks are written back into your files. Your markdown becomes the source of truth.
6_PLATFORMS,_1_FILE
Bluesky, Mastodon, LinkedIn, Medium, Dev.to, Substack. One markdown file targets all of them.
SIMPLE_BY_DESIGN
A MARKDOWN FILE IS ALL YOU NEEDTHE_PROCESS
WRITE
Markdown file with frontmatter. Pick your platforms, set a schedule.
QUEUE
Drop it in the folder, or use the API, CLI, MCP, or web UI.
PUBLISH
Blurt publishes everywhere in parallel, resizing images per platform.
RECORD
Permalinks saved back to your file. Markdown is now the system of record.
SUPPORTED_PLATFORMS
PUBLISH FROM A SINGLE FILE