CoinRoutes vs Elwood

Both refuse the price; they do not refuse the same things

Neither publishes a figure. Neither has a trial. Both answer every call to action with a demo request, which is the ordinary state of this end of the category — the priced-on-request shelf has eight products that publish no number at all and these are two of them.

Past that, they are different purchases, and the difference is easiest to see in what each one does with a fill.

CoinRoutes is an execution management system and stops there. A dozen named algorithms, a smart order router over roughly sixty exchanges and liquidity providers, a consolidated book to route against, TCA attached to every order. It is bought by people whose problem is that one order is too large for one venue.

Elwood is an OEMS with four more modules on the same data layer — portfolio, risk, collateral and reconciliation. The execution half is one front end over centralised exchanges, OTC liquidity and CME. The argument is not that its router is better; it is that the fill lands once and every other view moves with it.

The decisive difference is who you are

CoinRoutes is built to be sold onward. Its white-label product lets an OTC desk or an agency broker put its own brand in front of the platform and add its own markup for its own clients. That is a product decision with a commercial consequence: if you are a broker, CoinRoutes is infrastructure you can resell, and the vendor has designed for exactly that. If you are the end client of such a desk, it also means the price you pay may include a markup the platform never sees.

Elwood will not sell to you unless you are an institution, and says so before the site loads. The interstitial names the FCA's professional-client test — a regulated firm, a large undertaking meeting two of three size thresholds, a public body, an institutional investor — and the footer adds that the site is not directed at the United States or any EU member state. A prop trader with their own money is not the buyer, and the vendor tells you that before you read a feature.

What neither will tell you, and they differ here too

CoinRoutes cannot keep its own venue count straight. Five pages on its own site say 75-plus, 60-plus, 60, 50-plus and 50-plus, counted as exchanges, custodians, liquidity providers, pairs and instruments in different combinations. They are probably different things measured differently and the vendor never says which, so the 34 venues named on the integrations page are the only figure you can check. Ask for the list, not the number.

Elwood does not publish where your exchange keys live. It is the first thing a multi-venue terminal should answer, and nothing on the platform pages, the solutions pages, the terms or the privacy policy addresses API key storage. For a system that routes across forty venues on your behalf, that is the question to put in writing before anything about modules.

Which one, and when

Take CoinRoutes if execution is the problem and the surrounding stack already exists — or if you are a desk that intends to resell the platform to your own clients, which is a use it was explicitly built for.

Take Elwood if the expensive part of your month is not the fill but everything after it: reconciliation against custodians, collateral across venues, risk that agrees with the portfolio. Buying the modules separately is possible, which makes it the less all-or-nothing of the two.

Take neither if you are trading your own money. Both will decline you, one of them before the homepage renders. Velo publishes a price list; Tealstreet and Insilico Terminal cost nothing at the point of use and are paid by a builder fee on the trades you route through them.

And if the comparison you actually want is against the other two institutional systems here, the same refusal from a different angle is in Talos vs Wyden.