LocalShred Lite is a Solana shredstream and it is free. It is served from Amsterdam. It is open to anyone and it needs no DedicatedNodes server. The free Jito ShredStream closed on 5 September 2026. Jito ShredStream itself still runs and access to it now sits behind DoubleZero.
Your LocalShred™ stream does not change
LocalShred comes with every DedicatedNodes bare metal server at no additional charge. It is part of the server you already have rather than something sold beside it. It runs 3ms ahead of Jito ShredStream, measured in Amsterdam. LocalShred Lite is a different service. Lite is tuned to the speed Jito ShredStream delivered, which is parity rather than an advantage. It does not carry the lead your server already has. There is nothing for you to do.
What LocalShred™ Lite is
A free Solana shred stream served from Amsterdam. The client is open source under Apache-2.0 and it is a fork of jito-labs/shredstream-proxy at github.com/dedicatednodes/shredstream-proxy. The binary is localshred-lite-proxy. Migrating from Jito ShredStream changes one line of the command. The binary jito-shredstream-proxy becomes localshred-lite-proxy and --block-engine-url becomes --localshred-url:
localshred-lite-proxy shredstream --localshred-url http://localshred-lite.nlams.dedicatednodes.io:9999
Every other flag on the command stays the same, including the flags that say where shreds are delivered. The key goes in the API_KEY environment variable and not on the command line. A key passed as a flag is visible in ps to any local user on that machine.
Addresses are learned from the connection
The client takes no destination and there is no --public-ip flag. The source address of the heartbeat connection is registered on sight. A key holds up to three distinct IPv4 addresses.
Signing up
Registration is open to anyone at www.dedicatednodes.io/jito-shredstream-alternative.
Rollout
A shred stream is a fan-out. Every subscriber multiplies the egress leaving Amsterdam. What everybody already on the stream receives depends on that fan-out staying inside what the network carries without queueing. Onboarding in controlled batches is how the newest subscriber gets the same stream as the first. Accounts are enabled in the first batch. Further batches follow as capacity allows.
