Raydium

Raydium alternatives are split Between Aggregator Routing and Direct AMM Pools

Raydium alternatives are Solana swap paths that either search multiple liquidity sources or send an order straight to one automated market maker. Jupiter supplies broad routing, while Orca, Meteora and PumpSwap expose distinct pool mechanics. The better choice is the path with the highest protected output for the exact token pair and trade size.

July 27, 2026 Last updated

A Quote-to-Settlement Workflow for Comparing Venues

A venue comparison begins with identical mints, input size, slippage tolerance and quote timing across every route.

Start by entering the input and output mint addresses rather than relying on symbols. Ask Jupiter for its routed quote, then request direct quotes from the relevant Orca Whirlpool, Meteora DLMM pool and PumpSwap canonical pool. Capture the expected output, minimum output, pool fee, platform or referral fee, price impact and route composition at the same moment. One basis point equals 0.01% and 100 basis points equal 1%. Any split allocation shown by a router must total 100%, even when it crosses several venues.

Compare the minimum received first because that amount incorporates the route's slippage protection. Next, confirm that the wallet holds SOL for execution and has the required output account. The original Token Program and Token-2022 use different program IDs, while extensions can add transfer fees or extra accounts. A route that cannot build valid instructions has no executable advantage, even when its indicative output looks larger.

Refresh the candidates once, keep the same settings and submit the route that still protects the greatest net output.

What Can Break Between Quote and Settlement?

A Solana swap fails when its protected output, account list or compute demand no longer matches executable state.

Pool reserves keep changing after the quote arrives. If the available output falls below the signed minimum, the transaction rejects rather than settling at a worse amount. Aggregator paths also touch more programs and accounts than a direct swap. Solana caps each serialized transaction at 1,232 bytes and caps execution at 1,400,000 compute units. The default compute allowance is 200,000 units per non-builtin instruction unless the transaction requests another limit. Those constraints explain why a theoretically attractive multi-hop route sometimes cannot be assembled or landed.

Version 0 transactions use Address Lookup Tables to compress account references. A stored address becomes a 1-byte index instead of a 32-byte public key, and one lookup table holds up to 256 addresses. The documented account reach rises from 32 addresses in a legacy message to 64 with lookup tables. This compression expands routing room without changing the 1,232-byte transaction ceiling. After a rejection, refresh the quote and compare a shorter route with the direct pool. The rest of that story sits in Raydium in practice.

Direct Pools Trade Reach for Transparency

Among Raydium alternatives, direct AMM pools trade routing breadth for a visible mechanism and a single venue's liquidity. Orca Whirlpools concentrates capital inside price ranges; Meteora DLMM divides liquidity into fixed-price bins and PumpSwap provides canonical pools for graduated Pump coins. Jupiter remains stronger when its engine finds a better multi-venue fill. Lifinity used an oracle-led proactive market maker, but it is winding down and requires asset claims by December 31, 2026, so it does not belong on a forward-looking shortlist.

Fee Layers and Minimum Output Drive the Real Cost

A complete cost comparison combines venue fees, route fees, network fees, price impact and the protected output amount.

Solana sets the base transaction fee at 5,000 lamports per signature, while one SOL contains 1,000,000,000 lamports. An optional priority fee adds the requested compute-unit limit multiplied by its micro-lamport price, rounded up after division by 1,000,000. Jupiter's meta-aggregator adds its platform fee to the selected route. Its Metis Router path has no Jupiter swap fee, although an integrator can set a platform fee in basis points. Direct venues still charge the fee that the chosen pool defines.

Orca makes that pool charge explicit through initialized Whirlpool fee tiers. The nine distinct mainnet rates are 0.01%, 0.02%, 0.04%, 0.05%, 0.16%, 0.30%, 0.65%, 1.00% and 2.00%. A lower tier does not automatically produce more output; concentrated depth at the active price and trade size determine price impact. Compare the pool's quoted minimum after its stated tier rather than choosing by percentage alone.

Meteora DLMM combines a configured base fee with an optional volatility-responsive component. Its fee rate uses 1,000,000,000 precision, where 10,000,000 represents 1%, and the program caps the total trading fee at 100,000,000 units or 10%. The cap is a boundary, not the routine charge. For PumpSwap, fee schedules differ between canonical and non-canonical pools, so the signed quote supplies the relevant total. Finish with one number: minimum output after pool, platform and network charges.

A Worked Route Comparison From Quote to Minimum Output

A worked comparison should convert each quoted output into the minimum amount protected by the signed transaction.

Every changing input and route setting here is hypothetical: the trade is exact-input, the input is 10 SOL, the direct Orca quote is 1,980 USDC, the Jupiter quote is 1,992 USDC, Jupiter splits 60% through Orca and 40% through Meteora, slippage tolerance is 50 basis points and both quotes include venue or routing charges but exclude Solana fees. Fifty basis points equals 0.50%, so multiply each quote by 0.995. The Orca floor is 1,970.10 USDC and the Jupiter floor is 1,982.04 USDC.

The routed minimum is therefore 11.94 USDC higher. Convert each route's SOL-denominated network charge into USDC at the same comparison moment; routing wins only if its added network cost stays below that 11.94 USDC output advantage.

How Do Pool Designs Change the Route?

Pool design changes where liquidity sits, how price moves and which accounts a router must touch.

PumpSwap gives a graduated Pump coin a canonical AMM pool, so a direct trade targets that pool's reserves and configured fee path. Orca Whirlpools uses concentrated liquidity instead. Each Whirlpool tick represents a 1-basis-point price change, while each tick array stores 88 physical tick slots in a 10 KB account. A swapV2 instruction accepts as many as 6 tick arrays, although the program processes no more than 3 for the swap. Crossing beyond the reachable active range stops execution instead of silently changing the quoted terms.

Meteora DLMM places liquidity into bins that each trade at one fixed price. A fill has zero price impact while it stays inside one bin; price changes when it consumes that bin and advances to another. The bin step uses basis points, with 10,000 basis points equal to 100%. Dynamic positions begin with a 70-bin layout and expand as far as 1,400 bins. That structure gives a router discrete liquidity segments to compare against Orca ranges and PumpSwap reserves.

Jupiter sits above these venue programs. Its documented meta-aggregator compares 4 routing engines: Metis, JupiterZ, Dflow and OKX. Metis handles multi-hop and multi-split swaps across Solana decentralized exchanges, while JupiterZ requests quotes from market makers. A direct Orca or Meteora transaction removes that search layer and targets the selected pool. Choose direct execution for a known deep pool and a shorter account path; choose routing when combined sources produce a higher protected output after every charge.