Connect the intended instance
Enter the Mastodon server used by your account and complete its authorization flow. Verify both the account name and instance; the same local name can exist on different servers.
Plan a post for the instance your audience uses. Account context, text conventions and instance rules matter when adapting a campaign for the fediverse.
Compare plans ↗Enabled account types: Mastodon Profile
Enter the Mastodon server used by your account and complete its authorization flow. Verify both the account name and instance; the same local name can exist on different servers.
Prepare the status and media, then check the connected instance rules and the composer validation. Do not use a fixed character assumption for every server.
Inspect delivery on the selected instance. Report the account, instance and observation period together when comparing posts, because visibility and metric availability can differ.
Confirm the selected instance and supported format before publishing. Interpret remote activity using the metrics actually returned by that connector.
Publish to the authorized account on the intended instance and keep local rules with the draft checklist.
An operating example, not a customer case study or a performance promise.
| Task | Separate preparation | With MeDash |
|---|---|---|
| Instance identity | Identify an account only by its local username. | Keep the connected instance and identity together. |
| Length and media | Apply one server’s rules to every Mastodon destination. | Validate content against the actual connected instance. |
Limits and policies can differ by instance. Use the actual server rules and connected composer validation.
Review connected accounts, team seats, monthly publishing volume, storage and included credits. Feature availability follows your plan and workspace permissions.
Choose by your account count and publishing needs.
For solo creators and small brands starting with consistent Facebook and Instagram publishing.
Monthly payment
Annual payment, paid upfront
One payment covers 12 months. Equivalent to $10.00 per month.
Annual limits differ from monthly limits. Review the annual allowance below.
Choose by your account count and publishing needs.
For teams running recurring campaigns, queues, bulk publishing, and smarter content workflows.
Monthly payment
Annual payment, paid upfront
One payment covers 12 months. Equivalent to $30.00 per month.
Annual limits differ from monthly limits. Review the annual allowance below.
Choose by your account count and publishing needs.
For agencies and high-volume operators managing multiple brands, workspaces, and publishing pipelines.
Monthly payment
Annual payment, paid upfront
One payment covers 12 months. Equivalent to $65.83 per month.
Annual limits differ from monthly limits. Review the annual allowance below.
Network capabilities depend on account type, permissions and platform APIs. AI and paid API usage consume credits. Renewal, taxes and payment terms are shown at checkout.