Skip to main content
Profiles define chains, providers, and routing policy. They are configuration scopes, not client authentication boundaries. RPC Core has no built-in incoming client quotas; rps_limit controls the dashboard tester maximum and burst_limit is metadata.

​
Shared upstreams

With sharing_mode: auto, identical upstreams can share physical connections, health observations, and transport circuit breakers across profiles. Separate profiles do not create separate upstream quota. A problem with the shared upstream may affect every referencing profile. sharing_mode: isolated separates runtime state by profile. It does not increase the upstream account’s quota or remove the provider’s external limits. Each profile retains its own provider membership and routing policy. Dashboard aggregate and region views describe different scopes; use a regional view when diagnosing a local failure.

​
Multiple Profiles

Create separate profiles for different environments or use cases:
The dashboard lists configured profiles and links to this guide. To add a profile, create its YAML file in the profiles directory on each node and reload Lasso. For containers, follow the deployment instructions. v0.5.0 supports new profiles reusing connected WebSocket upstreams after reload. On v0.3.4, restart after adding a profile to avoid unavailable subscriptions. For new profiles and YAML edits, reload the running release:
Confirm the reload returns :ok, then refresh the dashboard. Each node reads its own files; distribute the same configuration to every node. Access via URL: /rpc/profile/:slug/:chain
See Configuration for validated fields and Docker deployment for host-mounted profiles.