Available
Studio
A place to make it yours.
Social publishing.
For you and your agents.
Write your next post, or let an agent prepare it. Review the content, adapt each destination and manage what goes live.
Prepare your next publication.
Prepare one post. Adapt each destination.
Connect your networks.
- Bluesky
- Discord
- Mastodon
- X
- TelegramComing soon
- FacebookComing soon
- InstagramComing soon
- YouTubeComing soon
- DEV.to
Write once.
Make each destination yours.
Start with one post. Adapt the text, media and schedule for each network, while keeping your source in one place.
Your tools.
Your way to publish.
Open the Studio. Bring your agent. Connect your workflows.
Planned
MCP
Your agent’s way in.
Prepare next week’s posts.
Model Context ProtocolPlanned
Workflow integrationn8n
Publishing, in your flow.
Available
CLI & API
Make it part of your toolkit.
postbot — terminal
bun run postdot --helpPostdot CLIResources:
projects listList projectsmedia listList mediaposts createCreate a draftLaunch target
Agent skills
Give your agent the know-how.
Future
Mobile
Take your workspace with you.
Studio and CLI/API exist today. MCP, skills, n8n and mobile show the direction ahead.
Room for every project.
Your content, media and collaborators, with a place for each.
Separate projects.
Bring people together.
A workspace groups your people and projects. Each project keeps its own posts, channels and media, with access you control.
Your workspacePeople & permissions
Your media.
Ready for the next post.
Keep images and videos in your library. Use local storage or connect your S3-compatible bucket.
Local or S3-compatible
Built-in channels.
Custom options, too.
Built-in
Custom
Connected, manual or custom.
Make it yours.
Text, emoji & media. Tools adapt to the network.
Hello.Bonjour.مرحبًا.
A multilingual interface
EN & FR today. More languages to come.
About running Postdot.
No. You can write, adapt and manage publications entirely in the web app. The CLI and REST API give your existing agents and scripts another way to work with the same posts.
Postdot does not contain a built-in AI writer. Your own agent can prepare content and create drafts through the CLI or API. You choose its access and what it is allowed to do.
Bluesky, Discord, LinkedIn, Mastodon, X and DEV.to, plus manual and custom HTTP destinations. Available content types and connection requirements vary by provider.
On infrastructure you manage. The installation guide uses Docker Compose from a source checkout, with local media storage by default and optional S3-compatible storage.
Yes, if they can run CLI commands or call a REST API. Give the integration a scoped API key. Postdot does not require a particular model or AI subscription. A dedicated MCP server is not available yet.
No. Draft creation and publication are separate actions. A destination must be explicitly promoted for delivery. Give agents only the actions they need when creating their API keys.
Yes. A post has shared source content and separate destination drafts. Text, media and scheduling can be adapted for each destination without changing a previous publication.
Some connections need provider application configuration or credentials. Requirements differ between networks, and a provider may apply its own access limits or charges. The connection guides explain what is needed.
Yes. Postdot supports S3-compatible media storage as well as local storage. Display previews are separate from the original files used for publishing.
You operate and back up your installation. The operations guide covers the database, media and configuration needed to restore a workspace. Postdot does not replace your infrastructure backup system.