The fastest way to land a transaction on Solana.

On Solana, whether your transaction lands often comes down to how it reaches the leader. Stake-weighted quality of service gives staked connections priority, and keeping those connections open removes the handshake and TCP slow start that cost you on every send.

swqos is that path, and only that path. You sign locally, hand over the bytes, and they go unchanged over persistent QUIC connections to the leader. There is no blockhash fetch, no simulation and no status polling in between. You keep control of the transaction; swqos is a route, not a middleman.

Visit swqos.com Documentation

0

RPC calls in the hot path

0.0002 SOL

per accepted send, refusals cost nothing

90s

dedupe window, resent signatures are free

What it does

Zero hops to the leader

Transactions go from the relay directly to the current leader over staked connections, bypassing the general RPC layer and its queues entirely.

Connections already warm

Staked QUIC connections are opened at startup and kept alive, with round-robin and retry across them, so no send pays for a handshake.

Nothing in the hot path

No blockhash fetching, no simulation, no status checks. The relay does one job: get your bytes to the leader as fast as physics allows.

Two ways to send

HTTPS for the simplest integration, a single JSON POST per transaction. QUIC for the fastest, one persistent connection with authentication only at the handshake.

Honest accounting

You pay 0.0002 SOL for each accepted send. Refused submissions cost nothing, and a duplicate signature within 90 seconds is free.

You stay in control

swqos never holds keys and never edits a transaction. A receipt means the bytes were forwarded and the upstream acknowledged the stream.

Who it’s for

Trading bots where landing rate is the strategy
Market makers and arbitrage systems
Wallets and apps that already build their own transaction flow
Teams that want a relay without a subscription

How it works

1Top up a prepaid balance in SOL and get your credentials
2Build and sign the transaction locally, exactly as you do today
3POST the serialized bytes over HTTPS, or stream them over QUIC, and confirm landing with your own RPC

A receipt from swqos means the transaction was forwarded and acknowledged upstream. Inclusion in a block is the network's decision, so confirm landing separately through your own RPC.

The team behind swqos is the team you hire.

CLR3 designs, builds and operates swqos end to end. When we take on consulting and product work, it is this same team, with the same habits: measured latency, monitored systems and documentation people can actually use.

Work with us