How etox compares to Competitor 2 (request-capped hosted RPC)
Teams outgrowing Competitor 2—here meaning a widely used provider that often meters free tiers in daily requests—usually hit ceilings on log-heavy workloads or want clearer WebSocket access for indexers. etox.io meters compute units per JSON-RPC method rather than treating every call identically, publishes the weight table, and exposes WS on the same hostname pattern as HTTP — details in /docs.
Quick comparison
| Topic | etox.io | Competitor 2 (typical) |
|---|---|---|
| Free tier shape | 20M CU/mo + 10 rps (keyed); 10M CU on rpcfree.com | Often daily request-based caps on free |
| WebSocket | Supported per chain where node exposes WS | Available on many plans; verify chain matrix |
| Ethereum archive | Reth archive | Available on paid tiers |
| Arbitrum / Base / Polygon | Rolling roadmap — see chain pages | Broad chain menu (varies by tier) |
| Infrastructure | Self-operated bare metal | Centralized provider fleet |
When etox is a fit
- You want predictable CU math for heavy
eth_getLogsand trace calls. - You need a public sandbox without API keys — rpcfree.com.
- You prefer routing to single-tenant-class hardware instead of opaque pools.
When to keep your current stack
If you rely on bundled ecosystem integrations or legacy enterprise contracts with your existing vendor, dual-provider failover may beat a hard cutover. etox is happy to run beside Competitor 2 (or any incumbent) during burn-in.
Technical integration mirrors any JSON-RPC host swap: change base URL, keep chain IDs identical, and re-run integration tests focusing on batch calls and subscription churn. Start on Ethereum RPC or read vs Competitor 1 for trace-specific positioning.