A price needs a product definition
A useful comparison identifies the network, data product, plan, billing period and included limits. A cheap read-only RPC plan and a high-volume decoded transaction stream answer different workloads. Listing them beside each other without those differences can make an accurate number support an inaccurate conclusion.
Keep a claim ledger
provider: Example
product: Solana transaction streaming
plan: Named plan
price: quoted amount + currency
period: calendar month or 30 days
limits: filters, connections, traffic, replay
source: official pricing URL
checked_at: timestamp
measurement: none, or reproducible benchmark referenceTreat this as a record template. It contains no current commercial quote. Preserve the official page or dated notes where allowed so a later change can be distinguished from an earlier research error.
Compare like for like
- Check the provider's official pricing and the product-specific Docs.
- Confirm whether an add-on is required for the exact stream or archive depth.
- Calculate costs using the same method mix and traffic assumptions.
- Keep negotiated quotes distinct from public list pricing.
- Mark a missing or ambiguous term as unknown and ask a precise question.
Refresh only what changed
Before a purchase or publication, recheck price-sensitive facts and update their dates. Technical benchmark results need their own methodology, region, observation window and event set. A pricing table cannot establish a performance winner. Supanode comparison pages should therefore distinguish current published service facts from measured results and from operational questions that still need a trial.