Meteora vs Raydium for a volume bot

These two ecosystems solve the same problem in genuinely different ways, and the difference is not cosmetic. Meteora holds liquidity in discrete bins where a correctly sized trade has zero price impact. Raydium spreads it along a curve or concentrates it into tick ranges, where every trade moves the price at least a little. For a campaign built from thousands of small repeated trades, that distinction changes what a good trade size looks like, what slippage setting works, and what the whole thing ends up costing.

Volion Research Updated Jul 30, 2026 6 sections

Two different answers to the same problem

Meteora DLMM divides price into discrete bins and puts liquidity into them, so all trading inside a bin happens at one fixed price with no impact at all. Raydium offers constant-product pools, where liquidity covers every price and each trade moves it slightly, and concentrated pools, where providers pick tick ranges and trades move price continuously within them.

The consequence for a campaign is specific. On Meteora there is a discoverable trade size below which you have literally zero price impact. On Raydium there is no such threshold; impact simply gets smaller as trades get smaller, approaching zero without ever reaching it. For campaigns that want activity without price movement, having a hard line to stay under is easier to work with than a curve to minimise against.

Against that, Meteora's discreteness cuts both ways. Cross a bin boundary and the price steps by the full bin width in one move, which is a larger discontinuity than any single trade produces on a Raydium pool. Meteora is more forgiving when you size correctly and less forgiving when you do not.

The mechanics of each are covered in Meteora DLMM bin steps and Raydium CLMM vs CPMM.

What each costs, measured

The table reads finalized mainnet blocks directly, counting fees and outcomes for every transaction touching each program. Cost per landed swap is the median fee divided by the success rate, since failed transactions pay too.

Meteora against Raydium, measured Sep 15, 2026 at 4:02 AM UTC across 1 finalized mainnet blocks. Fees in lamports.
Program	Sampled tx	Failure rate	Median fee	Cost per landed swap
Meteora DLMM	109	69.7%	8,450	27,888
Raydium AMM v4 low sample	10	80%	12,604	63,020
Raydium CLMM low sample	49	65.3%	10,570	30,461
Raydium CPMM low sample	16	56.3%	5,129	11,737

Programs with small samples are flagged rather than presented as equal to the well sampled ones. Raydium CPMM in particular is often thinly represented in a short window despite being a significant venue, simply because the pools using it skew toward newer tokens with sporadic activity.

What the raw comparison cannot tell you is which venue holds your token's liquidity, and that overrides everything below. Volume generated where there is no depth moves the price instead of the chart, whatever the fee comparison said.

Fee structures behave differently under load

Raydium pools charge a fixed tier chosen at pool creation. Meteora DLMM charges a base fee plus a variable component that rises with recent volatility and decays as things calm. That means a Raydium pool costs the same during a violent move as during a quiet hour, while Meteora costs more precisely when conditions are worst.

For a campaign that runs continuously, this changes the pacing calculation. On Raydium, running through volatility costs more only through higher priority fees and more failures. On Meteora, the pool fee itself rises on top of both. Three cost lines move together instead of two.

The flip side is that Meteora is cheaper than its headline suggests during calm periods, which is when a well paced campaign should be doing most of its work anyway. If your schedule already avoids volatile windows, you spend most of your time in the part of the curve where the dynamic fee is low.

How priority fees behave across the same conditions is covered in how Solana priority fees work.

The same campaign needs different trade sizes on each

On Meteora, size below the active bin depth and you get zero impact and a clean fill. On Raydium constant-product pools, size so that impact stays invisible, which is a judgement rather than a threshold. On Raydium concentrated pools, size to stay well inside the active tick range, which is closer to Meteora but without the clean boundary.

In practice this means a size that is well tuned on one venue can be wrong on another, and copying settings across tokens is a reliable way to overpay. The threshold on Meteora is discoverable by quoting increasing sizes and watching for where impact stops being zero. On Raydium there is no such moment; you are looking for where impact becomes large enough to notice, which is a softer call.

Meteora: find the bin edge, work meaningfully below it, re-check as depth changes.
Raydium constant-product: keep impact under a threshold you have chosen, and accept that it is never zero.
Raydium concentrated: stay inside the active range with margin, since leaving it produces failures rather than merely worse prices.

Where tokens actually end up, and why it is rarely a choice

Most tokens do not select a venue. They inherit one from whatever launchpad or migration path created their liquidity. By the time anyone is planning a campaign, the token already lives somewhere, and the useful question is how to trade well in that venue rather than which venue would have been better.

This is worth stating plainly because venue comparisons invite a decision that usually is not available. A token that graduated from a bonding curve landed wherever that curve deposits liquidity. A token launched through a Meteora-based launchpad starts life in a Meteora pool. Liquidity added deliberately by a team goes wherever that team chose, often for reasons unrelated to how a campaign will trade.

What follows is that the comparison matters most in two specific situations. The first is when a token genuinely has meaningful depth on both, which happens as a token matures and market makers add liquidity in more than one place. The second is when a team is deciding where to add liquidity themselves and can pick with campaign mechanics in mind, which is rare but is the moment where this page is worth the most.

For everyone else, the practical value is knowing which set of rules applies to the venue you are already in. Sizing against bin depth when you are actually in a constant-product pool, or watching for range exits when your pool has no ranges, means managing the wrong risk. Both venues are workable; the mistake is running one venue's playbook on the other.

The graduation path specifically, and what changes when a token moves, is covered in what changes the day your token migrates.

Which venue to run a campaign on

Pick the venue where your token holds real depth at the current price. When both hold meaningful depth, Meteora suits campaigns that can size trades precisely and pace around volatility, while Raydium suits campaigns that value predictability over the last few basis points and would rather not manage bin boundaries.

The genuine tie-breakers are practical rather than theoretical. If your trades comfortably fit inside a Meteora bin, that venue gives you something no Raydium pool can: zero price impact, repeatedly, at a fee that is low when you run during calm periods. If your trade sizes are variable or your schedule cannot avoid volatile windows, Raydium's fixed fee and continuous curve are easier to reason about and harder to get badly wrong.

Most tokens do not present this choice at all, because liquidity is concentrated in one place and that place is the answer. When a token does have real depth on both, comparing cost per landed swap on the day rather than relying on a general ranking is the correct approach, and that is what a Solana volume bot campaign should be doing on your behalf rather than defaulting to a favourite venue.

The full cross-venue picture is on which Solana DEX is cheapest for a volume bot. To model a specific budget, the calculator converts a target volume into cost at current measured rates, and campaigns are set up in the dashboard.

Questions

Is Meteora or Raydium cheaper for a volume bot?

It changes with conditions and with your trade size. The measured table on this page gives fee and failure rate for both so you can compare cost per landed swap directly. Meteora has a structural advantage when trades fit inside the active bin, because impact is then genuinely zero rather than merely small.

What is the main difference between Meteora DLMM and Raydium CLMM?

Meteora uses discrete price bins with zero slippage inside each one and a step change when crossing between them. Raydium CLMM uses continuous tick ranges where price moves smoothly with every trade. Meteora gives you a hard size threshold to stay under; Raydium gives you a gradient to minimise against.

Does Meteora charge more during volatile periods?

Yes. DLMM adds a variable fee component that rises with recent volatility and decays as conditions calm. Raydium pools charge a fixed tier regardless. Running a campaign through a volatile window therefore costs more on Meteora than the headline fee suggests.

Can I use the same trade size on both?

Not reliably. The right size on Meteora is set by the active bin depth, while on Raydium it is set by how much price impact you are willing to accept. Copying a size across venues is a common way to overpay or to generate unnecessary failures.

Which venue should a newly graduated token use?

Whichever one the graduation actually placed its liquidity in. A new token rarely has meaningful depth on multiple venues at once, so the choice is usually made for you, and running volume against a thin pool moves the price rather than producing useful activity.

Meteora DLMM bin steps Raydium CLMM vs CPMM Cheapest DEX for a volume bot Meteora DLMM routing Raydium volume bot routing How priority fees work