Deployment Options
Willow supports three deployment models. Choose the one that fits your security posture, compliance requirements, and operational preferences.
SaaS
The simplest way to get started. Willow hosts and manages everything — the runtime, the admin console, authentication, audit logs, and all backing infrastructure. There is nothing to install or maintain. Connect your AI assistants, configure your tools, and you're live in minutes.
Best for teams that want to move fast without any infrastructure overhead.
Learn more about SaaS deployment →
Hybrid
Your data stays on your infrastructure; Willow handles everything else. The runtime service that executes tool calls is deployed in your Kubernetes cluster, so API keys, database credentials, and internal data never leave your network. The admin console, SSO, permissions, audit logs, and updates are all managed by Willow SaaS.
Best for organizations with data residency or compliance requirements that don't want to operate a full on-prem stack.
Learn more about Hybrid deployment →
On-Premises
Every component of Willow runs inside your own Kubernetes cluster — the runtime, the admin app, the database, and all supporting services. There is no dependency on Willow SaaS at runtime. Your network never needs to reach out to mcp-s.com.
Best for organizations with strict air-gap requirements, regulated industries, or security policies that prohibit any external cloud dependency.