Squid Router vs Jumper Exchange is the comparison most retail crypto users land on when they need to move tokens between chains. Both are user-facing bridge aggregator apps with web interfaces, both route through 15+ underlying bridges, and both target the same use case: a user with tokens on one chain who wants tokens on another chain in one signature. Squid sits on top of Axelar's General Message Passing layer with native Cosmos coverage. Jumper Exchange is built by the LiFi team and showcases LiFi's aggregator API behind a polished UI. The decision between them comes down to which chains the transfer involves, how much the user values UX polish, and whether the underlying aggregator's bridge whitelist matches the user's risk tolerance.
​

This comparison is for users picking a cross-chain UI, not for developers picking an SDK. For the developer-facing aggregator API decision, see our LiFi vs Socket guide. Squid and Jumper both expose APIs as well, but the consumer-facing UI is where they differentiate. Neither team publishes a direct head-to-head against the other, so the numbers below come from each project's own docs and live app, checked against each other rather than against either vendor's marketing copy.
​

Squid Router is a cross-chain swap and bridge interface built on Axelar GMP. The Squid team launched App Squidrouter in late 2022 as the canonical user-facing implementation of Axelar's cross-chain messaging. Squid integrates the bridges Axelar can route through (Stargate, Wormhole NTT via Axelar's interop layer, native Cosmos IBC, Squid's own multicall-based atomic swaps) and exposes them in a single quote.
​

Jumper Exchange is a cross-chain swap interface built on LiFi's aggregator API. Jumper launched in 2023 as a showcase of what LiFi's aggregator can do behind a consumer UI. Jumper queries LiFi's full bridge list (32 bridges, 24 DEXes per LiFi's GitHub) and presents the best route to the user. The two share architecture: a routing layer underneath, a chain-and-token picker on top, a quote-then-execute flow.
​

The product positioning differs. Squid leads with Cosmos and exotic-chain coverage. Jumper leads with EVM polish and a wider DEX-aggregation story. Both work for the same baseline transfer (USDC Ethereum to USDT Arbitrum). They diverge once the transfer involves Cosmos, Solana, or non-mainstream chains.
​

Squid now covers more raw chain count; Jumper covers more DEX-level liquidity depth on the chains both support. Coverage is the largest differentiator between the two, and it widened in 2026 rather than converging.
​

Per Squid's own supported-chains registry, Squid lists 100+ chains as of September 2026, including roughly 65 Cosmos SDK chains (Osmosis, Kava, Stargaze, Injective, Stride, Celestia, Neutron, Sei, Akash, Comdex, Crescent, Cosmos Hub, and dozens more) plus Bitcoin, Solana, XRPL, Stellar, Sui, and the major EVM chains. Squid's architecture FAQ confirms the 100+ figure and notes Squid is "not limited to chains with smart contracts" because execution runs offchain through Squid Intents. Cosmos coverage is native: Squid routes IBC directly, so a user transferring ATOM from Cosmos Hub to Ethereum gets a native asset on each end, not a wrapped IOU.
​

Jumper's own front end reports 69 chains, 34 bridges, and 41 DEXs as of September 2026, up from the 30-chain figure Jumper carried through 2025. Jumper's parent LiFi separately advertises 60+ chains at the API level, and LiFi's monthly changelog shows new chain and bridge integrations landing most months in 2026 (Somnia, Robinhood Chain, and expanded Solana support among them). Jumper still does not cover Cosmos natively: a transfer involving Osmosis on Jumper routes through Squid underneath, meaning the user pays Squid's spread plus LiFi's. That double-aggregation is invisible in Jumper's UI but visible in the cost.
​

For tokens, both aggregators support the major stablecoins (USDC, USDT, USDS, DAI, FDUSD, PYUSD) and the major bridge-able assets (ETH, WBTC, native tokens of each chain). Long-tail token support diverges: Jumper's 41 DEX integrations give it deeper EVM long-tail coverage. Squid covers fewer EVM long-tail tokens but is the only one of the two with native support for Cosmos-native tokens (TIA, INJ, OSMO) and non-EVM assets like XRP and SUI.
​

Neither Squid nor Jumper charges a protocol fee on top of the route. Both make money through revenue share with the underlying bridges, market makers, and DEXes they route through, and the user's total cost is gas plus whatever spread is embedded in the winning route.
​

Squid's architecture FAQ states Squid charges no protocol fees and that users pay gas on the source chain only, with Squid Intents' RFQ auction model cutting gas costs by up to 90% versus traditional AMM-based routing because market makers, not the user's wallet, execute the destination-chain leg. Jumper does not publish an equivalent gas-savings figure; its cost is whatever LiFi's routing engine selects across its 34 aggregated bridges, disclosed per-quote in the app rather than as a standing benchmark.
​

For any transfer that involves a Cosmos chain, the cost structure still favors Squid on a mechanical basis: Jumper has no native Cosmos route, so a Cosmos-involving Jumper transfer executes through Squid underneath, which means the user's quote embeds both LiFi's routing markup and whatever Squid charges upstream. Exact dollar costs move with gas prices and market-maker competition at request time, so neither aggregator's app-based quote is stable enough to cite as a fixed number here; check the live quote in each app before a Cosmos-involving transfer.
​

Speed-to-finality varies more by underlying bridge than by aggregator. The fastest routes Jumper offers run through Across (10-30 seconds) or CCTP V2 fast transfer (sub-30-second). Squid no longer routes primarily through Axelar's General Message Passing; per Squid's architecture docs, Squid Intents settles through an offchain RFQ auction where market makers fill the order and a Cubist-powered TEE verifies the fill, with no fixed expiry window and, per Squid's own description, no slippage at execution.
​

For a transfer with finality preference on standard EVM-to-EVM routes, Jumper's Across and CCTP V2 options are the faster documented paths. For a transfer involving Cosmos or a chain Jumper doesn't cover, Squid is the only native option since Jumper would route through Squid anyway. Both aggregators still inherit some risk and timing profile from whichever underlying bridge or market maker fills a given route.
​

Failure handling on both aggregators is similar: a status page polls the underlying bridge and surfaces any failure to the user with a transaction hash. Recovery is bridge-specific. Squid's documented recovery path is an automatic refund on the source chain within roughly 15 minutes, with no manual intervention. Jumper's recovery surfaces LiFi's status API and the user manually claims refunds where applicable.
​

The choice of which bridges each aggregator routes through shapes both cost and risk. Knowing the bridge list matters for any team integrating Squid or Jumper at scale, since a paused or compromised bridge propagates through the aggregator to the user.
​

Squid no longer publishes a bridge list in the usual sense. Per Squid's architecture docs, Squid Intents is an offchain intent protocol: market makers compete in a request-for-quote auction to fill the order, the fill is verified in a Cubist-powered trusted execution environment, and only a token transfer ever touches the chain. Squid's own FAQ states that Squid integrates with both Axelar and LayerZero for routing and settlement, is not exclusively built on either, and has completed 9 audits with no reported security breach or hack to date.
​

Jumper routes through 34 aggregated bridges per Jumper's own app metrics, including Across, Stargate, CCTP, Hop, Symbiosis, Allbridge, Mayan, and Squid itself for Cosmos routes. LiFi's monthly changelog shows the bridge list changes most months as new integrations (Layerswap, Glacis, Relay V2) go live and older ones are deprecated. The breadth means Jumper has multiple routes for most EVM transfers, and the aggregator picks the best one at quote time.
​

For risk management, Jumper exposes an "advanced" mode where the user can see which bridge their route uses and switch to an alternate. Squid's UI shows the route detail by default and discloses its audit count in its own FAQ; Jumper's public docs do not surface an equivalent audit tally for the aggregator layer itself, only for individual bridges it routes through. For teams worried about a specific bridge, the right pattern is to set bridge whitelisting at integration time when using these aggregators' APIs, the consumer UI does not currently expose that filter directly.
​

Jumper Exchange has the more polished consumer UI. The chain picker is searchable, the token picker shows balances across chains automatically (Jumper queries the user's wallet for cross-chain holdings), and the quote display shows route details (which bridges, which DEXes, which chains transit) on a single screen. Wallet connection works through RainbowKit with support for 20+ wallets.
​

Squid's UI is functional and clean but less aggressive on convenience features. The chain picker requires the user to know which chain the asset is on. The wallet support is similar (RainbowKit). The route display is similar in detail. For Cosmos transfers, Squid's UI is the only choice, Jumper does not surface Cosmos chains in its picker.
​

For mobile, both apps work in mobile browsers rather than shipping a native app. Wallet connection on mobile uses WalletConnect, which is reliable on iOS and Android. Neither team publishes a mobile-specific usage breakdown, but since neither offers a dedicated app, mobile-browser parity is the only mobile experience either one has, and both meet it equally.
​

Both aggregators expose APIs underneath their consumer apps. Squid's REST API mirrors the consumer UI: a quote endpoint returns the route, an execute endpoint returns calldata, a status endpoint reports in-flight transfer state. Jumper does not expose a separate API, it uses LiFi's API directly, which means a developer who likes Jumper's UI but wants programmatic access integrates LiFi instead of Jumper.
​

This is a meaningful distinction. A team that wants the Squid Router routing logic in their backend can call Squid's API directly. A team that wants the Jumper experience in their backend integrates LiFi (and gets every bridge LiFi supports, not just Jumper's curated subset). The consumer-vs-developer split affects how each aggregator's product roadmap evolves: Squid invests in API parity, while Jumper's API surface is LiFi's.
​

Use Jumper Exchange for transfers between EVM chains, EVM and Solana, or any transfer where the user's source and destination assets are on the most common chains. Jumper's price and speed are better for that use case, and the UI handles edge cases (auto-swap on each end, balance discovery) more gracefully.
​

Use Squid Router for any transfer involving Cosmos, exotic chains (Squid's 100+ chain list includes many chains Jumper doesn't cover), or when the user wants the same aggregator that powers Travala's checkout and other Axelar-anchored integrations. Squid is the right choice for any cross-VM transfer that crosses Cosmos.
​

Use neither if the flow is recurring stablecoin movement at scale. Both aggregators are point-in-time consumer interfaces; neither handles the recurring-treasury-rebalance, payment-gateway, or programmatic-deposit-address use cases that production stablecoin teams need. Eco sits one layer above Squid and Jumper as an orchestration layer for stablecoin flows that need scheduling, automation, or reconciliation.
​

Squid Router and Jumper Exchange are user-facing front ends for bridge aggregation. They are the right product when a user is making a one-time transfer. They are not the right product when a stablecoin flow is recurring, programmatic, or needs to integrate with an off-chain accounting system.
​

Eco's Routes infrastructure handles the layer above. An app integrating Eco for a stablecoin payments flow can submit an intent and get a settlement event without picking a bridge or an aggregator. Behind Eco the network might use CCTP, Across, deBridge, or any of the routes Squid and Jumper expose to consumers, but the integrating app does not pick. For consumer one-off transfers, Squid and Jumper remain the right tools. For programmatic stablecoin orchestration, Eco replaces both.
​

This is the same orchestration-vs-aggregation pattern that distinguishes payment processors from acquiring banks in traditional finance. The aggregator (Squid, Jumper, LiFi, Socket) is the acquiring bank, it routes the transaction. The orchestrator (Eco) is the payment processor, it owns the policy, the retry logic, the reconciliation, and the SLA.
​

Jumper is cheaper for transfers between EVM chains and Solana, typically 20 to 40 cents less on a $1,000 stablecoin transfer because LiFi's bridge list includes Across, which is the lowest-cost route between L2s. Squid is cheaper for any transfer involving Cosmos chains because Jumper would route through Squid anyway, paying both spreads.
​

Squid supports 100+ chains including roughly 65 Cosmos chains, per Squid's own registry. Jumper supports 69 chains, 34 bridges, and 41 DEXs per Jumper's app. For Cosmos transfers, only Squid is native. See our cross-chain bridging guide.
​

Both aggregators inherit the security model of the underlying bridges they route through. Both have been audited by reputable firms. The risk surface is the bridge whitelist, a route through a compromised bridge would impact both aggregators. Use them for amounts you can afford to lose to a smart contract risk event.
​

Yes. Squid is the canonical user-facing aggregator for Cosmos transfers. It supports 12 Cosmos chains via Axelar's IBC integration, with native asset transfers (not wrapped IOUs). For Cosmos-to-EVM transfers, Squid is the only aggregator that doesn't route through wrapped tokens.
​

Jumper works for one-off consumer stablecoin transfers but is not designed for programmatic flows. For recurring stablecoin payments, treasury automation, or production stablecoin orchestration, an orchestration layer like Eco Routes handles the SLA and retry logic that consumer aggregators leave to the user.
​