How etox compares to Competitor 1 (large hosted RPC)
Teams evaluating a switch from a major SaaS RPC vendor—here labeled Competitor 1—usually care about three vectors: price at scale, method coverage (especially trace), and whether a vendor exposes a free Ethereum RPC without forcing heavyweight signup flows. etox.io competes on the first two with transparent CU tables, and adds rpcfree.com for the third — a funnel many incumbents do not offer in the same form.
Snapshot comparison
| Capability | etox.io | Competitor 1 (typical) |
|---|---|---|
| Ethereum archive | Yes (Reth) | Yes |
| Arbitrum trace / debug | Yes today on pruned depth; archive trace roadmap | Often limited or absent on Arbitrum |
| No-signup public RPC | rpcfree.com | Rarely equivalent |
| Pro list price | $49/mo (300M CU) | Often a similar tier in market |
| Infrastructure model | Owned Hetzner bare metal | Hosted SaaS / multi-tenant |
Why Arbitrum trace matters
Debug and trace calls power internal simulators, support tooling, and incident response. If your workload needs
debug_traceTransaction on Arbitrum, verify provider support before you commit — see our
Arbitrum RPC page for candid depth limits today and the Erigon Nitro archive plan.
Metering transparency
etox publishes per-method CU weights per chain in /docs. That makes load tests reproducible: you can multiply expected method mix by published weights and compare against plan ceilings without reverse engineering opaque credit calculators.
Try etox alongside your current vendor
Point a canary workload at eth.etox.io using a dashboard key, keep Competitor 1 (or any incumbent)
as fallback, and measure tail latency on eth_getLogs plus trace-heavy paths. For instant
experiments, start at rpcfree.com — details on /free.