Backend Required
Local means Individual Open Source.
OpenLeash supports a local open-source product mode only when desktop uses the real public client-api and Postgres. There is no standalone desktop-only backend.
1Install desktop
2Choose backend
3Connect
4Install hooks
5Protected
What Happens
Choose one of three backend-backed modes. Hooks call the configured client-api directly; provider proxy traffic can pass through the desktop edge for local container-plugin execution.
- Install the desktop client.
- Choose Individual Open Source, OpenLeash Cloud, or Private Cloud.
- Start the local backend, sign in to personal Cloud, or enroll with your organization.
- Install agent hooks.
- Keep coding.
OpenLeash Desktop
Backendapi.openleash.com
HooksClaude, Codex, Cursor, Gemini, OpenCode, OpenClaw, NanoClaw
Cloud backend connected · local plugin edge ready
Backend Required
Policy, evaluation, plugin settings, approvals, audit, and account state come from client-api and Postgres in every mode.
Individual Open Source hooks: http://127.0.0.1:9318/v1/hooks/:agent/:event OpenLeash Cloud hooks: https://api.openleash.com/v1/hooks/:agent/:event Private Cloud hooks: https://openleash.company.example/v1/hooks/:agent/:event
What This Means
The desktop may keep local cache/setup state, but it is not the source of truth.
Backend and Postgres are required
Hooks target the configured client-api directly
Protected hooks fail closed when the backend is unavailable
Individual Open Source stores BYOK locally
Organization plugin policy flows from the dashboard
Finish Line
You are done when the desktop client is running, hooks are installed, and the backend connection is healthy.