// Client comparison
Agave vs Jito: which Solana validator client?
When you spin up a dedicated Solana node you choose a validator client. For almost everyone that's Agave, the mainline client. Jito is the MEV-focused fork — only worth it if you need simulateBundle. Here's the honest breakdown.
| Agave | Jito | |
|---|---|---|
| Maintainer | Anza (core team) | Jito Labs (fork) |
| Focus | Reference validator + RPC | MEV / bundles |
| simulateBundle | No | Yes |
| Yellowstone gRPC | Yes (Geyser) | Yes (Geyser) |
| Gets updates first | Yes | Tracks Agave releases |
| Best for | RPC, streaming, general | Searchers, MEV, arbitrage |
Agave — the default
Agave is a fork of the original Solana validator previously maintained by the Solana Labs team. Agave is now under active development by the core engineering team at Anza.For RPC nodes and Yellowstone gRPC streaming it's the right call: it's the reference implementation, receives protocol changes first, and has the widest operational track record. Unless you have a specific MEV requirement, pick Agave.
Jito — for MEV and bundles
Jito is an MEV-focused validator client. Only recommended if you need access to simulateBundle.If you're a searcher landing bundles through the Jito block engine, or you need simulateBundle to test bundle outcomes before submission, Jito is the client you want. For everything else, the extra surface area isn't needed.
Either way, you get Yellowstone gRPC
Both clients expose the Geyser interface the Yellowstone gRPC plugin hooks into, so your streaming setup is identical. Learn how to consume it in the Yellowstone gRPC tutorial and the Geyser plugin guide. On a dedicated node you choose the client at checkout and can switch later.
Agave vs Jito — FAQ
What's the difference between Agave and Jito?
Agave is the mainline Solana validator client, maintained by Anza (the core engineering team that span out of Solana Labs). Jito is a fork of the Solana validator focused on MEV — it adds the block-engine integration and the simulateBundle RPC method. For pure RPC and Yellowstone gRPC streaming, Agave is the default. You only need Jito if your workload specifically depends on bundle simulation or MEV-flavoured behaviour.
Which client should I run on a dedicated node?
Agave for the vast majority of cases — it's the reference client, gets updates first, and covers all standard RPC and Yellowstone gRPC needs. Choose Jito only if you need simulateBundle or want MEV-aware behaviour. On a Subglow dedicated node you pick the client during checkout and can switch later on request.
Is Jito faster than Agave for trading?
Not inherently for data streaming. Both expose the same Geyser/Yellowstone interface, so gRPC streaming performance is comparable. Jito's advantage is access to bundle simulation and the Jito block engine for landing MEV bundles — relevant for searchers and arbitrage strategies, not for general data ingestion or copy-trading.
Does the Yellowstone gRPC plugin work with both?
Yes. The Yellowstone gRPC Geyser plugin hooks the validator's Geyser interface, which both Agave and Jito expose. You get the same streaming surface — slots, blocks, transactions, account updates — regardless of client. See our Yellowstone guides for how to consume it.
Can I change clients after provisioning?
On a Subglow dedicated node, yes — request a client switch and we'll handle it. Because the gRPC/RPC interface is the same across clients, your application code doesn't change when you switch between Agave and Jito.
Pick your client. We run the node.
Agave or Jito on a single-tenant AMD EPYC 7543p with Yellowstone gRPC included. From $2,900/mo — first month 50% off ($1,450 to start).