HostNexFlow › Library › Jupiter vs Raydium
Jupiter vs Raydium: the aggregator and one of the pools it routes through
They are not competitors in the usual sense. Raydium is a Solana automated market maker — pools of liquidity that trades execute inside. Jupiter is a router that finds the cheapest path across pools, very often Raydium's. The real question is which surface you should touch, and when.
Searches for 'Jupiter vs Raydium' usually hide a category error: Jupiter is an execution layer, Raydium is a liquidity layer, and a Jupiter swap frequently is a Raydium trade — executed inside a Raydium pool, paying Raydium's pool fee, because the router decided that pool was cheapest. Understanding that turns the comparison into something more useful: when do you touch each surface directly, and what does each layer actually charge and risk?
Every row below names its source and date.
The parameter table
| Parameter | Jupiter | Raydium |
|---|---|---|
| What it is | Swap aggregator and trading suite — routes orders across Solana AMMs; also perps (JLP), DCA, limit orders, launchpad (Jupiter docs, as of 2026-09-28). | Automated market maker — liquidity pools (CLMM, CPMM, legacy AMM) plus farms and the LaunchLab launchpad (Raydium docs, as of 2026-09-28). |
| Launched | 2021; became Solana's dominant route layer (Jupiter docs/history). | February 2021; one of Solana's original AMMs, originally Serum order-book hybrid (documented). |
| Relationship | Routes through Raydium pools — along with Orca, Meteora, PumpSwap and the rest — whichever prices best (router mechanics). | Supplies liquidity Jupiter routes to; a Raydium pool may be the venue your Jupiter fill lands in. |
| Platform fee on swaps | No protocol platform fee on aggregation; you pay the underlying pools' fees and Solana gas (Jupiter docs, as of 2026-09-28). | Pool fees set per pool tier — paid to LPs and the protocol; what your fill pays regardless of front-end (Raydium docs). |
| Who provides liquidity | Nobody — Jupiter holds no pools; it composes other venues' liquidity. | Liquidity providers depositing into CLMM/CPMM/legacy pools, earning the fee share (Raydium docs). |
| Direct UI purpose | Best-execution swaps and its other products; the front-end is the product. | LP management, pool analytics, LaunchLab — direct trading exists but routing users usually arrive via Jupiter. |
| Incident file | No custodial pool to drain; the risk class is front-end and dependency — routing integrity and the interfaces fronting it. | December 16, 2022: a compromised owner authority drained ~$4.4M from pools (documented exploit); pools continued under revised authority. |
| Tax/reporting | No forms; its billion-JUP airdrop wave(s) were income at receipt (our does-jupiter-report-to-IRS file, 2026-09). | No forms; LP fees and yield events are user-side accounting. |
The layer confusion
Treating Jupiter and Raydium as alternatives is like comparing a flight search engine to an airline. Jupiter's product is the route: it splits your order across whichever pools price it best — Raydium, Orca, Meteora, PumpSwap, and the long tail — and composes one transaction your wallet signs once. Raydium's product is the liquidity: pools of deposited tokens that any trade — including a Jupiter-routed one — executes against.
That means a 'Jupiter swap' can settle entirely inside a Raydium pool and pay Raydium's fee to Raydium's LPs while Jupiter takes nothing on the leg. The two coexist by construction; the real choice is which interface you open, not which protocol you back.
When the surfaces differ
Use Jupiter's surface when you want execution: it finds the cheapest route across the whole pool surface, including splits across several pools in one fill, and it's where perps, DCA, and limit orders live. Use Raydium's surface when you want the pool itself: providing liquidity, managing CLMM positions, claiming farming rewards, or launching through LaunchLab — things a router doesn't do.
The exception worth knowing: a trader who wants a specific pool's price without aggregation — say, deliberately routing inside one pool to control the fill — is a Raydium-UI user by intent. For the ordinary 'swap token A for token B' case the router wins on expected price almost by definition.
The money each makes
The revenue models differ as much as the layers. Raydium earns when its pools are used: a slice of each pool's fee plus LaunchLab activity — its business is the liquidity itself. Jupiter took no platform fee on aggregation historically; its revenue lives in the products around the router — perps, limits, launchpad services — which is why the aggregator can afford to route to a competitor's pool without blinking.
For the user that collapses to a simple fact: the fee your swap pays is set by the pool the route lands in either way — using Raydium's own front-end doesn't skip Raydium's pool fee, and using Jupiter doesn't add a Jupiter toll on top. Liquidity providers see the mirror image: depositing into a Raydium pool is opting into being the inventory a router feeds on — your pool earns fees precisely when Jupiter decides your curve is the cheapest fill, which is most of Solana's retail volume on busy days.
The record each carries
Raydium has the incident file: on December 16, 2022, a compromised owner authority was used to drain roughly $4.4 million from its pools — an admin-key failure, not an AMM flaw, but a real loss and a permanent entry in its security record. Jupiter's risk profile is different in kind: with no pools and no custody, there is no vault to drain — its exposure lives in routing integrity and front-end supply chain, the surfaces you verify rather than the funds it could lose.
Both, of course, ride Solana's own availability: a congested or halted chain freezes both the route and the pool equally. There is also a shared dependency worth naming: most users reach Raydium pools through a third-party surface — Jupiter, a wallet's built-in swap, a terminal — so the pool's own front-end downtime matters less than the liquidity beneath it, which lives in the program and answers to no website.
Who should pick Jupiter, who should pick Raydium
Pick Jupiter's surface to trade: better expected execution across the whole liquidity surface, one signature, and the product suite around swaps. Pick Raydium's surface to provide liquidity or to run pool-level operations — CLMM positions, farms, LaunchLab — or when you specifically want a single pool's book rather than a route.
And recognize the overlap honestly: most Solana users do both without noticing — trading on Jupiter while their fills settle in Raydium pools is the normal path, not an edge case. The two even share a launchpad rivalry downstream, where Raydium's LaunchLab competes for the same new-token flow Jupiter routes — layers cooperating at fill time while their businesses compete for the next launch.
Frequently asked
Is Jupiter or Raydium better for swapping?
They aren't substitutes: Jupiter is a router that includes Raydium pools in its search, so for execution Jupiter's surface wins by construction — your fill may still settle inside Raydium. Raydium's own UI is for pool-level work.
Does Jupiter charge a fee?
No platform fee on aggregation per its docs — you pay the underlying pool's fee and Solana gas. Revenue lives in its other products (perps, limits, launchpad).
Has Raydium been hacked?
Yes — December 16, 2022: a compromised owner authority drained roughly $4.4 million from pools. It was an admin-key failure, not an AMM exploit; pools continued under revised authority.
Can I provide liquidity on Jupiter?
Not as pools — Jupiter holds no liquidity; its liquidity-adjacent product is JLP, the perp-counterparty token. Providing pools for trading pairs is a Raydium-side activity.
Which is safer?
Different risk shapes: Raydium's pools carry smart-contract and admin-key risk (with the 2022 drain on record); Jupiter's exposure is routing and front-end integrity since it never holds funds. Neither custodies your assets between trades.
Do Jupiter or Raydium report to the IRS?
Neither — both are non-custodial Solana protocols with no US reporting layer. Jupiter's airdrop waves were still taxable income at receipt; LP fees on Raydium are user-side accounting.