Federated posting, one instance or many
Connect any Mastodon instance, schedule toots, build threads, route replies into the unified inbox. Federation handled for you.
Character limit
500 per toot · auto-thread above (instance-dependent)
Auth method
OAuth 2.0 per-instance
You
@you@mastodon.social · 14m
Federation handled, multi-instance accounts welcome. Visibility set per toot before publish.
Boosts
249
Followers
61218
Any instance
Point at your home instance, authorise once, federation handled for you.
Threads + content warnings
Build a thread, set a CW per toot, mark sensitive media before publish.
Visibility per toot
Public, unlisted, followers-only, direct, picked per toot.
Boost + reply tracking
Boosts and replies from federated servers funnel into the inbox.
One tool, endless possibilities
Built for how you actually use Mastodon
Publish
Multi-instance, one workspace
Run multiple Mastodon presences across different instances? Unison registers a per-instance OAuth app the first time it sees one, and exposes each account as its own channel. Boosts and replies from federated servers preserve the original instance.
- Per-instance OAuth registration handled automatically
- Multi-account workspaces with instance hostnames preserved
- Visibility, content warnings and sensitive media per toot
You
@you@mastodon.social · 14m
Federation handled, multi-instance accounts welcome. Visibility set per toot before publish.
Boosts
249
Followers
61218
Resources
New to Mastodon on Unison? Start here
Any instance running standard Mastodon API. Unison registers an OAuth app on the instance the first time it sees one, then signs you in.
Sign up
Connect a channel
Schedule the first post
No demo call, no sales conversation, no contract. The composer opens, you connect what you publish to, you ship.
Just shipped Unison v1. One composer for every social network you actually post to. Scheduling, threading and replies, all from one workspace