Ways to Leverage Lasso
Every plan unlocks Lasso's geo-distributed proxy and routing layer. They differ in throughput, capacity, and offer progressively more expressive built-in control. Custom profiles give you max freedom to orchestrate your own nodes, public providers, and bring any EVM chain you want.
Free
Public providers, routed and watched.
- providers
- Free public providers
- rate limit
- 30 RPC/s global · 60 burst
- monthly quota
- 1M CU
- strategies
- Load balanced
- Live provider health and routing evidence
- Requests stop at the monthly quota
Pro
Commercial providers, full strategy set.
- providers
- Public and commercial
- rate limit
- 100 RPC/s global · 200 burst
- monthly quota
- 10M CU
- strategies
- Load balanced, Latency weighted, Fastest, Priority
- Falls back to public providers at the quota
Custom
recommendedYour nodes, our routing layer.
- providers
- Your own nodes or provider keys
- rate limit
- 1k RPC/s global · 2k burst
- monthly quota
- Unlimited
- strategies
- Load balanced, Latency weighted, Fastest, Priority
- custom profiles
- Up to 5
- Any EVM chain Lasso can identify and probe
- Per-profile config, limits, and metrics
- Public endpoints retain shared upstream limits
It is straightforward to run yourself, and ships with every preconfigured public provider on your own infrastructure. Lasso.sh adds instant access to geo-distributed proxy nodes: lower latency at the edge, on routing infrastructure tuned for the Erlang VM.
compute units
Lasso meters traffic, not requests. One CU is 4KB of combined request and response payload, rounded up, so a small eth_call costs 1 CU and a wide eth_getLogs costs more. Debug and trace methods are charged 2×, and no single request exceeds 250 CU, so one oversized response cannot drain a month.
on every plan
- Geo-distributed proxy
- Circuit breakers and failover
- Block-lag detection
- Real-time observability