SOLANA gRPC · YELLOWSTONE GEYSER

Solana gRPC,
executed at shred speed.

A Yellowstone-compatible Geyser stream fed by our own execution engine. Transactions, account updates and slots, sub-millisecond from shred arrival. Bring the client you already use.

HOW IT WORKSNO VALIDATOR IN THE WAY.

Straight from
the shreds.

A Solana Geyser stream without a validator and plugin in front of it

Most Geyser endpoints sit behind a validator: it receives shreds, replays the block, and a plugin forwards the results. We run our own execution engine directly on the shred feed. Transactions execute as their shreds arrive, and the resulting account writes and transaction results go to subscribers straight from execution.

What we publish is one defined interval, live: from a shred arriving to the update leaving on the gRPC stream. Current p50, p90 and p99

WHAT YOU CAN SUBSCRIBE TOPROCESSED COMMITMENT.
ACCOUNTS

By address or by owner program, with memcmp, datasize and data slices, so you receive only the bytes you need.

TRANSACTIONS

By accountInclude, accountRequired and accountExclude, with a failed filter. Lookup-table keys count, not only the static ones.

SLOTS

Slot statuses on the same stream, so you know which slot an update belongs to and when the leader moves on.

Filters are named and can be replaced on a live stream. Filters that would match the whole chain are refused. Streaming docs

YOUR CLIENT, OUR ENDPOINTPLAINTEXT HTTP/2. ONE TOKEN.

Change two lines.
Keep the rest.

Works with Yellowstone gRPC clients in TypeScript, Rust and anything built on the Geyser proto

Examples in TypeScript and Rust
import Client from "@triton-one/yellowstone-grpc";

const client = new Client("http://fra.no-name.io:10000", process.env.NONAME_TOKEN, {
  grpcMaxDecodingMessageSize: 64 * 1024 * 1024,
});
const stream = await client.subscribe();
stream.on("data", (update) => console.log(update.filters, update.transaction?.slot));
stream.write({ transactions: { swaps: { accountInclude: ["pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA"] } } /* … */ });
LOCATIONENDPOINT
Frankfurthttp://fra.no-name.io:10000
Amsterdamhttp://ams.no-name.io:10000

Solana gRPC pricing

PAID IN USDC. NO CONTRACTS.
TRIAL
Free3 hours

Full feed, both streams. Measure it against your current best source.

1 DAY
50USDC

For a proper benchmark run.

1 WEEK
200USDC

About 29 USDC a day.

30 DAYS
650USDC

About 22 USDC a day.

Every plan also includes the deshred stream: every transaction before it executes. Sign up through a referral link and pay 5% less. Billing

THE DETAILS

Solana gRPC, answered.

The questions teams ask before they switch.

Is it compatible with Yellowstone gRPC?

Yes. It serves the Yellowstone geyser.Geyser/Subscribe stream, so existing clients only need our endpoint and your token, sent as the x-token header. Unary calls such as GetVersion are not served. Streaming docs

Which commitment levels are served?

Processed. Updates are produced as transactions execute, on whichever fork the leader is building, so a small share of processed state is later abandoned when a fork is dropped. Pair it with a confirmed source where that matters.

What do the latency numbers measure?

The time from a transaction's last shred reaching our node to its executed update leaving on the gRPC stream, over a rolling one-minute window. Your network hop to us is not in it; host your client in or near the location you buy.

Which locations can I use?

Frankfurt and Amsterdam. Each plan is for one location and one registered server IP address; the endpoint only accepts connections from that address.

Do I also get the deshred stream?

Yes. Every plan and the trial include SubscribeDeshred on the same endpoint and token: every transaction as soon as it is rebuilt from shreds, before it executes. Solana deshred stream

ALSO IN EVERY PLANBefore execution

Solana deshred stream →

The same transactions, about 0.35 ms earlier: rebuilt from shreds, before they execute.