Skip to main content
Henry Cloud is the default. For organizations that need Henry inside their own boundary, an enterprise self-hosted deployment is available: your database, your models, connected or fully air-gapped.
Self-hosted Henry is scoped with our team, not self-serve. Contact sales and we will walk your security team through the architecture and the deployment that fits.

​
Your own model endpoint

A self-hosted Henry can route model calls to any OpenAI-compatible endpoint: vLLM, Ollama, TGI, LiteLLM, or an internal gateway. This is configured on the deployment, not per workspace. Behavior:
  • The endpoint appears in Settings → Models as a single catalog entry.
  • Calls go directly to your endpoint. Henry’s gateway never sits in front, and there is no failover.
  • No reasoning or thinking configuration is sent.
  • Self-hosted inference records no Henry-side model cost.
  • Use a model id that does not collide with a catalog model. If it does, calls still reach your endpoint but are priced at the catalog model’s rates; CUSTOM_MODEL_EXCLUSIVE=1 avoids this.
  • With exclusive mode on, every workspace’s model preference resolves to your endpoint.

​
Identity

Self-hosted deployments support SAML single sign-on the same way Henry Cloud Enterprise does. See Single sign-on.

​
What to expect from the engagement

  • Architecture walkthrough for your security team, including the security architecture and subprocessor list.
  • Sizing and deployment scoping for your environment.
  • Versioned updates, including offline updates for air-gapped installs.