Skip to main content
Lasso RPC Core v0.5.0 runs on your infrastructure. For a managed endpoint, use the Lasso Cloud quickstart.

​
Container installation

See release evidence for the verified v0.5.0 image digest and native installation checks. The primary distribution is ghcr.io/jaxernst/lasso-rpc, with native Linux AMD64 and ARM64 images. Use the Compose attachment from the release you select. It requires Docker Compose and OpenSSL for generating local secrets:
Open http://localhost:4000/dashboard. Preserve .env across restarts and keep it private; it contains the signing and Erlang distribution secrets. Compose passes its values into the container, including provider credentials you add. Changing .env requires container recreation with docker compose up -d --force-recreate --wait; reloading YAML does not change a running container’s environment. Compose binds port 4000 to localhost, runs as UID/GID 10001:10001, and keeps the root filesystem read-only. /tmp is temporary; the named /data volume retains profiles and benchmark history. docker compose down retains that volume; docker compose down --volumes deletes it. Set LASSO_PORT in .env to choose another local port and LASSO_NODE_ID to give the instance a stable identity.

​
Source installation

​
Prerequisites

  • Elixir: 1.18.4 (CI version)
  • Erlang/OTP: 28 (CI version)
  • Node.js: 18+ (asset compilation)

​
Setup

Available at http://localhost:4000. Dashboard at http://localhost:4000/dashboard. The included public profile includes free public providers — no API keys required.

​
.env File

Lasso loads a .env file from the project root if present (via Dotenvy). System environment variables take precedence over .env values.

​
Configure and verify

Keep config/profiles/public.yml; routes without a profile use public. Public upstreams require no provider key, but have their own availability and quotas. A successful health response proves the application is running; make an upstream-backed RPC request as well. For custom profiles, persistent storage, image verification, upgrades, and rollback, see Docker deployment. RPC Core has no built-in client authentication or incoming RPC quotas. Protect externally accessible RPC, metrics, and dashboard endpoints at your network or reverse proxy.