Across vs Hyperlane: bridge or messaging framework? (2026)

Across is built around token transfers: users choose a route, receive a quote and bridge through its app. Its intent-based design uses relayers to fill transfers on the destination chain. Across says the average time from confirmation to funds in the wallet is 1.2 seconds; treat that as a project claim rather than a guarantee for every route.

Hyperlane is a broader interoperability framework. Its Nexus interface supports bridging, while the underlying system can send arbitrary messages between chains, not just tokens. Developers can deploy without approval from the core team or governance, and choose their own validators, relayers and contract extensions. That flexibility is useful for building custom cross-chain applications, but it means route setups can differ in security and complexity.

Both projects cover a wide range of networks, but their published coverage claims describe different things. Across lists more than twenty networks, including Ethereum, several rollups, Solana, Tron and Hyperliquid. It also supports bridge-and-swap flows and offers an API for applications that want to add cross-chain bridging.

Hyperlane says its framework reaches more than 150 chains across seven VM environments, including EVM, Solana and Cosmos-style environments. It supports messaging as well as token transfers, with examples such as cross-chain swap routing, multichain asset issuance and governance. Those capabilities make it more adaptable for developers. For a user who mainly wants to move tokens, Across’s narrower focus and dedicated transfer app may be easier to assess. The chain lists do not guarantee that every asset or route is available; check the route you intend to use before transferring.

Neither publishes a fee schedule, so the two cannot be compared by a fixed published rate. Across says it has no aggregator markup or hidden fees and that the app quote shows what you pay. Its costs can include the relayer fee, destination-chain gas covered by the relayer and any swap pricing. Your own origin-chain gas is separate, so review the full quote before signing.

Hyperlane says bridge costs can include source-chain gas and an interchain gas payment for the relayer. The amounts should appear in Nexus or in the wallet confirmation. Pricing for Hyperlane-as-a-Service support for deployers is also not published. In both cases, costs can depend on the route and transaction. Compare the actual quote for the same route and amount rather than assuming one protocol is cheaper.

Across says transfers are verified onchain and that it has no multisig custody or single point of failure. Two audits are listed, but the auditors, dates and scope are not published. Across also says no user funds have been lost; that is the project’s claim, not a guarantee against future losses. Transfers still involve smart contracts, relayers, an optimistic verification process and liquidity pools.

Hyperlane has no audits listed, and its homepage names none. This does not establish that its code has never been audited, but public audit information is limited. Its permissionless model gives deployers control over validator and relayer choices, so the security of one route may not describe another. Both involve contracts and multiple chains, where a failure can affect a transfer. Start with a small amount if you choose to use either bridge, and do not treat past claims or TVL as proof that a route is safe.

Choose Across if your main goal is moving tokens through a purpose-built bridge app, and you value features such as transfer history, pools and bridge-and-swap flows. Its listed coverage includes more than twenty networks, and its two listed audits give it more public audit information than Hyperlane, though their scope and dates are not published. Review the quote and route before sending funds.

Choose Hyperlane if you are a developer or chain builder who needs arbitrary cross-chain messages, permissionless deployment or support across multiple VM environments. Nexus also gives bridge users an interface and Explorer, but users should pay close attention to the validator and relayer setup for their route. Hyperlane’s coverage claim is broader, while its audit information is less clear. For either project, check that your exact asset and destination are supported and confirm the displayed costs before signing.