Echowide compared with Ferryman
The four things they do better, first.
Ferryman is the reason this product exists, and most of what we know about cross-posting we learned by reading what they published. If you are choosing between us today, there are real reasons to choose them. Here they are, before anything else.
Observed on their public site and pricing page, 27 August 2026. Usage figures are their own counters.
They are shipping, and we are new
Ferryman is in production with paying customers and publishes its own counters: 616 accounts and 37,797 posts cross-posted, as shown on their site in August 2026. That is a real operating history against real platform APIs, and it is the single strongest reason to choose them over us today.
More integrations are live for them right now
Publishing to X, Meta, TikTok, YouTube and LinkedIn requires each platform to review and approve a developer application. Ferryman has been through that. Our Bluesky and Mastodon paths need no approval and work today; the rest are built and waiting on review we cannot rush. We will not list a platform as live before it is.
They support Substack and we refuse to
If Substack is where your writing goes, they can post there and we cannot. We think the only available method — storing your session cookie — is a risk we should not take on your behalf, but that is our judgement, and the practical effect for you is a platform we do not cover.
Their rules engine came first
The list of cases that must not be cross-posted — replies to other people, quotes, paid posts, edits of something already sent, Instagram trial reels — is theirs. They learned it the expensive way and published it. Ours behaves the same way because we read it, and pretending otherwise would be dishonest.
Where we differ
One architectural decision explains most of this table.
They run on serverless functions, which cannot hold a connection open, so every origin account has to be asked on a timer — and the hosted services that make that arrangement work show up in the price. We run one long-lived process on a machine we rent. That choice is why the sync is faster on two platforms, why the bill is smaller, and also why our media queue can back up. It cuts both ways and the table says so.
| Topic | Ferryman | Echowide | Stronger |
|---|---|---|---|
| How a new post is noticed | Polled on a timer. Their functions are serverless, so no connection can be held open. | A socket held open on Bluesky and Mastodon; adaptive polling everywhere else. | Echowide |
| Delay before the first echo | Minutes, set by the poll interval on your plan. | Under a second where the platform pushes. Not a plan feature. | Echowide |
| Entry price | $30 a month, per their published pricing in August 2026. | $0 for fifty cross-posts a month, then $9. | Echowide |
| Top price | $100 a month. | $39 a month. | Echowide |
| Free plan | Their published tiers begin at the $30 monthly plan. | One flow, two destinations, fifty cross-posts a month, no card. | Echowide |
| Platforms live today | The full set, approved and running, including Substack. | Bluesky and Mastodon end to end. The rest await platform review. | Ferryman |
| Substack | Supported, via a stored session cookie. | Not supported, on purpose, for that reason. | Ferryman |
| Track record | A live product with published counters: 616 accounts, 37,797 posts. | None yet. Read the architecture and judge the reasoning instead. | Ferryman |
| Preview before publishing | Available, but as a preview-on-write option in their MCP endpoint. | A dry run is the default path in the product, before a flow is ever switched on. | Echowide |
| What a failure looks like | A per-destination status you interpret yourself. | A sentence naming the destination and the reason, in the ledger. | Echowide |
| Duplicate protection | A dedup ledger, and edits matched so an already-sent post is not re-sent. | The same idea, enforced by a uniqueness constraint in the database. | Level |
| The eligibility rules | Comprehensive, and published openly. | The same rules, resolving toward not publishing whenever a case is unclear. | Level |
| Where it runs | Vercel functions and a hosted Postgres, with hosted media and realtime services. | One long-lived process and a MySQL 8.4 database on a server we rent. | Level |
| Media handling | A hosted media pipeline, which scales without our thinking about it. | Our own ffmpeg, one job at a time, on shared cores. Cheaper, and it can queue. | Level |
Their figures are taken from material they publish themselves. We have not tested their product against ours under load, and we do not claim a benchmark we have not run.
The price gap
Their own comparison page raises this before we do.
Ferryman compares itself with Buffer and concedes that thirty dollars a month is a lot next to six dollars per channel. That is a fair thing to admit, and the reason behind it is structural rather than greedy: a hosted media pipeline, a hosted realtime service and a per-request compute bill all have to be covered before the first dollar of margin.
We do not have those bills, so we are not passing them on. That is the entire explanation for the numbers on the right. It is not an introductory rate and there is no step change waiting at renewal.
Ferryman, published tiers
$30 · $60 · $100
Per month, as listed on their pricing page in August 2026.
Their published tiers begin at the first of those three.
Echowide
$0 · $9 · $19 · $39
Per month. Instant sync, threading and the fail-closed rules engine are on every one of them, including the free plan.
What we would rather you heard from us
The costs of our own decisions.
- Video transcoding runs one job at a time, because we share eight cores with other tenants on the same machine. A long clip can wait behind another long clip. We show the queue position rather than a spinner.
- We run on one MySQL instance shared with other tenants on the same box, with a small connection pool because taking more would be rude to them. That is correct at the size we are and it is a deliberate choice, but it is not a dedicated database and we are not going to describe it as one.
- Billing is not switched on yet, so the paid plans above are prices rather than purchases. The free plan is real and works now.
- One machine, one process. We publish a health endpoint and we will publish uptime, but we are not going to claim a redundancy we have not built.
Choosing
Pick them if this is you.
Ferryman is the better choice
If Substack is part of your posting, if you need X, Instagram, TikTok or LinkedIn publishing working this week, or if an established operating record is what you are actually buying. Those are good reasons and we are not going to argue you out of them.
Echowide is the better choice
If you post primarily on Bluesky and Mastodon and want the echo to land in the same conversation rather than several minutes later. If thirty dollars a month is more than the job is worth to you. If you want to see exactly what would be published, everywhere, before anything is.
Try it against the tool you already use.
The free plan costs nothing and needs no card, so you can run both for a month and compare the timestamps yourself. That is a better test than anything on this page.