dashboard-api is the public admin API surface for OpenLeash dashboards.
It is built from the same core service as client-api, but runs with OPENLEASH_API_SURFACE=dashboard so admin workflows stay separate from client enforcement routes.
- Organization onboarding
- Identity provider setup
- User and group sync
- Policy management
- Organization plugin policy: mandatory/default state, employee catalog freedom, configuration locks, and per-agent profiles
- Deployment tokens
- Agent, MCP, skills, trigger, and audit views
- BYOK evaluation key management
- Managed self-hosted admin workflows
npm install
docker compose up -d postgres
python3 migrate.py --target local --scope core --apply --yes
npm run dev:dashboard-apiHealth:
curl http://localhost:9319/healthRecommended full-mode runner:
python3 run.pyChoose Private Cloud.
dashboard-api uses the same public Postgres schema as client-api. Run the core migration job once per target database before starting or upgrading either API:
python3 migrate.py --target custom --database-url 'postgres://...' --scope core --backup-apply --yesFor a fresh database, --apply is enough. For production upgrades, prefer --backup-apply.
Managed private-cloud/self-hosted customers can configure:
- Google Workspace
- Okta
- Ping Identity
- Microsoft Entra ID / Azure AD
- LDAP / Active Directory-style sync
cloud-dashboard-api wraps this surface for OpenLeash-hosted multi-tenant cloud. Shared admin behavior belongs here; hosted-only tenancy and operator behavior belongs in the cloud wrapper.
Plugin administration follows the same public contract in Private Cloud and organization OpenLeash Cloud. Controls are independent: requiring a plugin does not automatically lock its settings or close the catalog. Profiles may apply organization-wide, to an agent kind, or to an exact authenticated/enrolled agent runtime; employee overrides are honored only when organization policy permits them.