Skip to main content
Lasso RPC Core routes Ethereum JSON-RPC across your nodes and providers over HTTP and WebSocket. Configure a provider pool, choose a routing strategy, and inspect performance in the dashboard. Use RPC Core to run the open-source engine on your infrastructure. Use Lasso Cloud for managed endpoints, accounts, API keys, and billing. These sections describe RPC Core v0.5.0; Cloud has a separate compatibility contract. See Versions, availability, and evidence to compare the released Core artifact with the separately deployed Cloud service. Support, security, incidents, and lifecycle explains the public help path, supported-version policy, and repository boundaries.

​
Routing and resilience

  • Select providers using measured latency, load balancing, configured priority, or a direct provider route.
  • Apply transport health, circuit state, declared method restrictions, and request limits when selecting candidates.
  • Bound retries by execution safety and the original request deadline. Signed transaction submission gets one upstream dispatch.
  • Share matching newHeads and logs subscriptions and recover within explicit replay and time limits.
  • Inspect local and aggregated observations with optional clustering. Each node makes its own routing decisions.
Provider plans, quotas, history, and parameter support still constrain what Lasso can serve. More profiles or Lasso nodes do not multiply an upstream account’s quota.

​
Get started

Install the public container, make your first request, then configure your own providers. The included public.yml profile lets you try public upstreams without provider keys. RPC Core has no built-in client authentication or incoming customer quotas. Protect exposed RPC, metrics, and dashboard endpoints at your network or reverse proxy. See Production checklist.