Mayan started by making cross-chain swaps fast and simple.
Today, that same infrastructure powers products that need to move value across chains reliably, whether that’s a wallet executing a trade, a trading app funding an account, a market maker rebalancing inventory, or a payments app settling in the right stablecoin.
Cross-chain is still our specialty. What has changed is how much developers and product teams can build on top of it.
The gap products keep hitting
The problem is often the same: users start with one asset, on one chain, while the product needs something else somewhere else.
Mayan handles the movement and conversion in between.
That can mean:
a wallet letting someone trade without bridging first
a trading app letting users fund an account with whatever asset they already hold
a market maker moving inventory between chains
an onramp delivering the asset and chain a user actually wants
an offramp accepting assets from more chains without building every route individually
a payments or remittance app receiving one asset and settling in another
a stablecoin platform moving value across chains with predictable output
a chain connecting users and liquidity from ecosystems beyond its own
a merchant accepting one asset and receiving another
The user should not have to think about bridges, routes, gas, or where liquidity sits. And the product team should not have to design around those constraints.
Infrastructure you build on
Mayan is turning cross-chain execution from something users have to think about into infrastructure product teams can build on.
That infrastructure is flexible by design. Users can start with the asset they already have, and the product can receive the asset and chain it actually needs. There is no narrow list of supported pairs defining the experience. Mayan can move between supported assets and chains, converting along the way.
What you can ship with it
The same underlying execution now powers a broader set of primitives:
Swap. Trade across chains without making bridging a separate step.
Bridge. Move assets across chains quickly and securely.
Pay. Send stablecoins with predictable output, including 1:1 where supported.
Deposit. Let users fund an account from the asset and chain they already use.
Withdraw. Let users exit to the asset and chain they want.
Orchestrate. Move directly from one asset or chain into the next action.
For developers and PMs, that creates a much larger design space.
A wallet can make cross-chain trading feel native. A trading app can accept deposits from far more assets without forcing users through a bridge first. A ramp can expand what it delivers without integrating every token and chain combination individually. A market maker can rebalance capital across networks. A stablecoin or payments product can move funds to wherever settlement needs to happen.
All through the same underlying infrastructure.
Built to disappear
Mayan is built for products where execution needs to be fast, predictable, and reliable enough to disappear into the experience.
To date, more than $20B has moved through Mayan across 9M+ swaps and 3M+ wallets.
What started as a way to make cross-chain swaps feel simple is becoming the infrastructure behind a much broader set of products.
Products no longer need to design around where money starts. They can design around what users actually want to do.
Start building at docs.mayan.finance.
Want to talk through your integration first? Book a call with our team here.