Solana transaction send services compared (2026): tips, limits and preflight
Last updated:
Disclosure: We sell one of these (Triport); its row is marked (ours). Triport also forwards a transaction that tips Helius Sender or Jito to those services, as our docs describe, so those rows are not independent alternatives to ours. This is a dated comparison, not a speed ranking.
Send services: tips, limits and preflight
"Not stated" means the vendor's pages we read did not say; it does not mean the feature is missing. Rate limits have different units between vendors.
| Service | Tip | Minimum tip | Rate limit | Regions | Preflight | Price (as published) | Source |
|---|---|---|---|---|---|---|---|
| Helius Sender | Required, with a priority fee | 0.001 SOL (Sender Max); 0.000005 SOL (SWQOS-only) | 1 req/s per IP and region keyless; 50 req/s per key and region | slc, ewr, lon, fra, ams, sg, tyo | Optional | No API credits; you pay the tip. On every plan | Vendor page, read 2026-11-01 |
| Jito block engine | Required for bundles | 1,000 lamports for bundles | 1 req/s per IP and region by default | Amsterdam, Dublin, Frankfurt, London, New York, Salt Lake City, Singapore, Tokyo | sendTransaction always skips it | You pay the tip | Vendor page, read 2026-11-01 |
| QuickNode Lil' JIT | Priority fee and Jito tip required on sendTransaction | Its docs say Jito no longer has a minimum; Jito's docs state 1,000 lamports | Not stated | Not stated | Always skipped | From $89/mo as an add-on | Vendor page, read 2026-11-01 |
| Triton Cascade | Not stated | Not stated | Per IP, by tier; figures not stated | Not stated | Advises skipPreflight true: sends with preflight on are billed twice | Usage: per million requests plus per GB | Vendor page, read 2026-11-01 |
| Nozomi (Temporal) | Required on every transaction | 0.001 SOL; below it, transactions are silently dropped | Not stated | Pittsburgh, Newark, Ashburn, Los Angeles, Frankfurt, Amsterdam, London, Tokyo, Singapore | Does not simulate | You pay the tip; not charged if the transaction fails. Plan price not stated | Vendor page, read 2026-11-01 |
| Astralane Iris | Required | 0.00001 SOL | 5 TPS by default | fr, fr2, lax, jp, ny, ams, lim | Recommends skipPreflight true | Not stated | Vendor page, read 2026-11-01 |
| Chainstack Warp | Not stated | Not stated | Not stated | Not stated | Not stated | Paid add-on, billed separately. Chainstack plans to deprecate it on December 1, 2026 | Vendor page, read 2026-11-01 |
| Triport (ours) | Optional: a tip adds that service's path | None of ours; the tipped service's rules apply | By plan, in the key facts above | Frankfurt direct lane; triport.io/sol falls back across regions | On by default, your choice | Part of the flat plan; no per-transaction fee | API reference, checked 2026-11-01 |
How to read the table
Tip first. A required tip is the real price of these services, and it is paid per transaction, so a bot sending many transactions should do the arithmetic. At a 0.001 SOL minimum, 10,000 landed transactions cost 10 SOL in tips. Plans that charge nothing per transaction change that sum, but they do not include a paid route's tip if you choose to use one.
Silent failure. Nozomi states that a tip below its minimum is dropped with no error, and Helius rejects a transaction with no tip or priority fee. Your monitoring has to tell a rejected transaction from a slow one, which means tracking every send by signature.
Preflight. Solana's documentation recommends keeping it on; Triton and Astralane advise turning it off; Jito's route always does. With it off, a broken transaction reaches the chain and pays, or disappears without an error. See what preflight reports.
Who retries. Nozomi says it retries until the transaction confirms or the blockhash expires. Solana, Helius and Triton guidance is to set maxRetries: 0 and retry from your client. Do not stack an aggressive client retry on a service that says it retries for you without reading its rules.
What vendors claim about routing
These are the vendors' statements, not our measurements:
- Helius says Sender Max routes across several pathways simultaneously.
- Astralane says it routes through partner SWQoS clients and to block builders.
- Nozomi says it uses staked connections across the cluster.
- Chainstack says Warp transactions go to the current leader through a staked validator connection.
For what a staked connection does, read the stake-weighted QoS definition.
Which one fits
- Small volume, no contention. A normal endpoint with a correct fee: see the send guide.
- Competing for hot accounts near Frankfurt. Triport's direct lane, with a tip when it is worth paying.
- Competing from Tokyo, Singapore or the US. A service with a region next to you. Our direct lane is in Frankfurt only.
- Atomic groups of transactions. Bundles: sendBundle. Limits differ: Jito allows 5 transactions, while Helius and Nozomi state 4.
FAQ
- Which Solana send service lands the most transactions?
- We cannot tell you, and we are wary of anyone who can without a method. Landing depends on your fee, the accounts you touch, your distance from the leader and the moment you send. Test with your own transactions and count what lands, per route, over the same period.
- Do I need a send service at all?
- Often not. If your transactions are not competing with others for the same accounts, a correct priority fee, a compute limit and a retry loop through a normal RPC endpoint is usually enough. Fix those first.
- Why do so many services want skipPreflight true?
- Preflight costs time and a simulation. Solana's documentation still recommends keeping it on, and the two positions fit different cases: skip it when you have already simulated and timing decides the outcome, not by default.
- Can I use several of these at once?
- Yes. A signed transaction can be sent to several routes, and Solana processes it at most once. Each route's tip is a transfer inside the same transaction, so tipping two services pays both if it lands.