On‑Prem
On-Prem is its own item in the admin sidebar, under Admin — it is not a section inside Settings. It appears only when your organization actually runs its own infrastructure, which means either of these is true:
- Your admin app is a self-hosted on-prem deployment, or
- You run hybrid, and an External Run Service gateway is your default gateway
If you don't see it, the second condition is the usual reason: adding an external gateway is not enough on its own, it has to be set as the default. See Gateway Settings.
What's on the page
It is a read-only view of your deployment plus a couple of maintenance tools:
- Service URLs — your Runtime URL and Connect URL, shown for reference. Edit them in Gateway Settings, not here.
- MCPB download and service versions
- Encryption Key — rotate the master key that encrypts secrets at rest. Full on-prem deployments only; it does not appear on hybrid, where Willow manages the database. See Rotating the Encryption Key.
Looking for your runtime and connect URLs?
Every organization has them, on-prem or not. They live in Gateway Settings, where each gateway lists its connect URL (the dashboard) and its run URL (the MCP endpoint).
Looking to configure a self-hosted run service?
That is Gateway Settings → Add Gateway → External Run Service, which also issues the auth secret your deployment needs. The end-to-end procedure is in Hybrid Deployment.
Looking to deploy Willow on your own infrastructure?
Running Willow inside your own Kubernetes cluster is a deployment task rather than a settings change. See On-Prem Deployment for the Helm chart, prerequisites, and setup guide, or Hybrid Deployment to self-host only the runtime.