One API to dispatch
your content
anywhere.
Open-source infrastructure for content distribution. Like Stripe for payments โ except for posting. One HTTP call, seven platforms, zero vendor lock-in.
No per-account fees. No paywalls. No vendor lock-in.
curl -X POST http://localhost:8000/dispatch \ -H "Content-Type: application/json" \ -d '{ "targets": ["twitter", "bluesky", "telegram"], "formats": { "twitter_thread": {"tweets":["shipped v0.4"]}, "bluesky_post": {"text":"shipped v0.4"}, "telegram_message":{"text":"shipped v0.4"} } }'
Get started in 60 seconds.
Five ways to install โ pick what fits your stack.
# Add the tap (formula lives in the main repo) brew tap matthew-selvam/open-dispatch \ https://github.com/Matthew-Selvam/Open-Dispatch brew install open-dispatch # Set up credentials $EDITOR ~/.open-dispatch/.env # Start (foreground) open-dispatch # Or run as a background service โ auto-starts on login brew services start open-dispatch
Why not just use a hosted scheduler?
Hosted tools rent you access to your own audience. Open-Dispatch hands you the keys.
Everything you need. Nothing you don't.
API-first
Every action reachable via one HTTP call. Automate from cron, n8n, AI agents, or your own app โ no dashboard required.
Web UI included
HTMX-powered dashboard: compose, retry, watch the queue live. Same port as the API โ zero JS build step.
3 queue backends
JSONL on disk, Redis, or Postgres. Swap the persistence layer with a single environment variable.
AI caption adapt
One source text โ per-platform rewrites. Ollama-first, OpenRouter fallback, heuristic safety net.
Media transcoding
10 platform image specs built in โ square, reels, 16:9, portrait. REST endpoint + Python API.
n8n node
Native integration: Dispatch, Adapt, Get Row, Retry, List Queue โ all 5 ops, zero JSON wiring.
Simple, stable API.
Every endpoint is reachable over plain HTTP. /queue/{id} content-negotiates โ browsers get the HTML detail page, API clients get JSON.
| Method | Path | Purpose |
|---|---|---|
| GET | /healthz | Liveness probe โ JSON for monitors, HTML dashboard for browsers |
| POST | /dispatch | Enqueue a ContentUnit for one or many platforms |
| GET | /queue?status=โฆ | List rows (queued / publishing / published / dead) |
| GET | /queue/{id} | One row โ JSON or HTML (content-negotiated) |
| POST | /queue/{id}/retry | Re-queue an errored or dead row |
| DELETE | /queue/{id} | Delete a single queue row permanently |
| POST | /ai/adapt | Rewrite a caption for each target platform |
| POST | /media/transcode | Resize image to a platform spec |
| GET | /media/specs | List all 10 platform image specs |
Architecture at a glance.
POST /dispatch
โ
โผ
Queue (JSONL โ Redis โ Postgres)
โ
โผ
scheduler/worker.py
โ
โโโถ adapters/twitter.py
โโโถ adapters/bluesky.py
โโโถ adapters/instagram.py
โโโถ adapters/telegram.py
โโโถ adapters/linkedin.py
โโโถ adapters/threads.py
โโโถ adapters/youtube.py
โ
โผ on publish / fail
webhook_urlAdd a platform in 80 LOC.
One function, one file. The worker handles retry, backoff, and webhooks for you.
def publish( unit: ContentUnit, account: str | None) -> tuple[bool, str, str]: """Returns (ok, post_id, error).""" ...
- 1.Write adapters/myplatform.py
- 2.Add it to ADAPTERS in adapters/__init__.py
- 3.Document the format key in README
Native n8n integration.
Community node ships in the repo. Build it once, use all five operations from the visual editor โ no JSON wiring.
Frequently asked questions.
Which install method should I use?
On macOS the quickest path is the macOS App โ one download, drag to /Applications, done. If you prefer the terminal, Homebrew gives you brew services for automatic startup at login.
How do I self-host on a Linux server or VPS?
Docker is the cleanest option for Linux โ zero Python setup, runs as a non-root user, and includes an optional Redis sidecar. Watch the Docker setup walkthrough โ
Is it really free?
Yes โ MIT licensed. Your platform credentials never leave your own machine. There's no cloud component, no telemetry, and no account to create.
How do I access the API?
Once Open-Dispatch is running, the API is available at http://localhost:8000 with no auth required by default (it's designed for trusted self-hosting). Hit GET /healthz to confirm it's live, then POST /dispatch with a JSON body to send content. See the API reference โ for the full endpoint list and request shapes.
Where do I get API keys for each platform?
See the Credentials Guide โ a step-by-step reference with direct links to Twitter, Instagram, Telegram, Bluesky, LinkedIn, Threads, and YouTube developer consoles. Open it in a browser for copy/paste instructions per platform.
Which credential format should I use for multiple accounts?
Use PLATFORM_FIELD_ACCOUNT (uppercase). Example: TWITTER_ACCESS_TOKEN_WORK and TWITTER_ACCESS_TOKEN_PERSONAL let you target twitter:work or twitter:personal in your dispatch requests. See the README for per-platform examples.
Can I add a new social platform?
Yes. The adapter contract is a single Python function โ about 80 lines of code. See CONTRIBUTING.md for a step-by-step guide. The worker handles retry, backoff, and webhooks automatically.
Ready to dispatch?
MIT licensed. Self-host forever free. Your platform credentials never leave your .env.
135 tests ยท 7 platforms ยท 3 queue backends ยท 5 install methods