Execution Engines

Pick how each trade lands — by speed, MEV protection, or landing rate. Same flat platform fee on every path.

Overview

Subslot gives you five execution paths, chosen per trade: pump, beam, metis, jito, and helius. Beam is the default and works on any token; the others trade venue, protection, and landing rate for specific situations.

In the side panel, select the engine from the tabs above the buy/sell buttons — JUP expands to Beam and Metis, and PUMP, JITO, and HELIUS are their own tabs. The choice persists across side-panel refreshes. In the full-page terminal, a quick Route dropdown in the TRADE header offers pump, beam, and metis, remembered between sessions.

Engines are free. There is no token to hold, no tier, and no gating — every path is available to everyone. The only difference between them is on-chain cost (tips and priority fees) and how they route.

Beam — the default

Jupiter Beam (/swap/v2/build) aggregates routing across every Solana venue — Raydium, Orca, Meteora, and more — for the best price, with sub-second, MEV-protected landing. Subslot assembles the transaction itself for tight control and appends a private address-lookup table so complex routes still fit the packet limit, retrying with fewer accounts if a route is too large.

Pump — direct pump.fun

Pump trades the pump.fun bonding curve directly (pre-bond) or the PumpSwap AMM (after graduation), with no aggregator in the path and a fast Sender-tip landing. It only applies to pump.fun coins.

Never reroutes silently. If a token has no pump pool, the trade fails with NO_PUMP_ROUTE rather than quietly switching venues, fees, and slippage behind your back. The PUMP option then disables for that token, and you re-fire deliberately on an engine you pick.

Metis — alternate aggregated quote

Metis routes via Jupiter's /swap/v1 quote and lands through Helius (with an automatic Jito fallback). A reliable alternate aggregated path when you want a different quote engine than Beam.

Jito — atomic bundles

Your transaction is bundled and sent directly to Jito's block engine, which forwards it to validators. Bundles are atomic and MEV-safe — your trade cannot be sandwiched.

In the side panel, Jito exposes an Atomic Bundle checkbox: with it on, a multi-wallet buy from a group (up to 5 wallets) is sent as one atomic Jito bundle — all of them land in the same block, all-or-nothing, so your wallets never end up half-filled at different prices. One Jito tip covers the whole bundle.

Jito Settings

Open the preset bar (shown when Jito is selected) to configure:

Helius — highest landing rate

Helius Sender is the most aggressive path. Your transaction is submitted through two routes at once, and whichever lands first wins:

  1. Staked connections (SWQOS) — Direct validator connections through Helius' staked infrastructure.
  2. Jito bundle — Simultaneously submitted to Jito's block engine.

This dual-routing gives the highest probability of inclusion on contested launches.

Helius Settings

Helius uses the same preset fields as Jito — slippage, priority fee, and tip. The tip is used as the Jito bribe when the Jito path is the one that lands.

Engine Comparison

EngineRoutingMEV protectionUSDCOn-chain extras
Beam (default)AggregatedYesYesSmall Beam tip
PumpDirect curve / AMMNoNoSender tip
MetisAggregated (V1)NoNoPriority fee
JitoJupiter build + Jito bundleYes (atomic)NoPriority fee + Jito tip
HeliusJupiter build + dual-pathPartialNoPriority fee + tip
Platform fee: a flat 0.4% on every engine, with 90% returned as cashback — a net 0.04% per trade (about 0.08% round trip). No token, no tiers; installs running a developer key pay 0. See Fees & Cashback.