Configuration overview

Lasso is configured via YAML profile files in config/profiles/. Each profile defines chains, providers, routing policy, and dashboard tester settings. Multiple profiles provide separate routing configurations for different environments. Identical upstreams can share connections, health, and observations; profiles are not authentication boundaries.

Profile File Structure

# config/profiles/<slug>.yml

# --- Frontmatter (YAML document separator) ---
---
name: "My Profile"           # Display name
slug: "my-profile"           # URL identifier (used in /rpc/profile/:slug/...)
rps_limit: 100               # Dashboard tester maximum RPS
burst_limit: 500             # Metadata; not enforced by OSS
---

# --- Body: Chain configurations ---
chains:
  ethereum:
    chain_id: 1
    providers:
      - id: "my_provider"
        url: "https://..."

Frontmatter fields:

Field	Type	Required	Description
`name`	string	Yes	Human-readable profile name
`slug`	string	Yes	URL-safe identifier. Must be unique across profiles
`rps_limit`	integer	No	Maximum RPS offered by dashboard tester controls (default: 100)
`burst_limit`	integer	No	Profile metadata (default: 500); no OSS ingress enforcement

OSS does not authenticate clients or enforce per-client request quotas. Configure authentication and inbound rate limiting at your reverse proxy. Provider quota and circuit-breaker backoff are separate routing controls. Unknown YAML fields and invalid types are rejected. Use booleans (false), not quoted strings ("false"). A failed reload keeps the previous active configuration. Errors identify the field without printing credential values. Profile slugs must match their .yml filenames. Files beginning with _ or . are skipped. Keep a public.yml profile: routes without a profile use public, and it is required at startup. unlisted: true hides a profile from the selector; its endpoints remain accessible.

Get Started

Core Concepts

Configuration

Deployment

Observability

Advanced

Configuration overview

Profile File Structure

Next steps

​Profile File Structure

​Next steps

Profile File Structure

Next steps