LavenderFive vs PublicNode

LavenderFive leads on 2 of 8 shared benchmarks, PublicNode on 6. LavenderFive wins on Fastest free Celestia RPC, live no-key Cosmos SDK endpoint latency (265 ms vs 399 ms), Fastest free Terra RPC, live no-key endpoint latency (241 ms vs 417 ms). PublicNode wins on Fastest free Osmosis RPC, live no-key endpoint latency (245 ms vs 257 ms), Fastest free Cosmos Hub RPC, live no-key Cosmos SDK endpoint latency (202 ms vs 258 ms), Fastest free Injective RPC, live no-key Cosmos SDK endpoint latency (257 ms vs 260 ms), Fastest free dYdX Chain RPC, live no-key Cosmos SDK endpoint latency (104 ms vs 258 ms).

Read methodology Last measured Window: rolling 24h13 shared benchmarks
LavenderFive logo
LavenderFive

Cosmos validator running multi-chain no-key RPC endpoints under rpc.lavenderfive.com/<chain> and lcd.lavenderfive.com/<chain>. Covers Osmosis, Cosmos Hub, Neutron, Injective and 20+ other Cosmos SDK chains.

PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

Side by side measurements

Frequently asked questions

LavenderFive vs PublicNode: which one is better?

LavenderFive and PublicNode are compared on 13 shared OpenChainBench benchmarks. LavenderFive leads on Fastest free Celestia RPC, live no-key Cosmos SDK endpoint latency. PublicNode leads on Fastest free Osmosis RPC, live no-key endpoint latency. See the live table on this page for every metric.

Which is faster, LavenderFive or PublicNode?

On the Fastest free Celestia RPC, live no-key Cosmos SDK endpoint latency benchmark, LavenderFive leads at 265 ms versus PublicNode at 399 ms. Live measurement is updated continuously by the OpenChainBench harness.

Which is faster, LavenderFive or PublicNode?

On the Fastest free Osmosis RPC, live no-key endpoint latency benchmark, PublicNode leads at 245 ms versus LavenderFive at 257 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the LavenderFive vs PublicNode comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.