Deploy Beth and Isaiah inside the customer's own data center — full operational and security control, suitable for the most controlled enterprise environments.
On-premise is the deployment posture for customers whose data-residency, sovereignty, or operational-control requirements rule out any cloud deployment. Beth and Isaiah are installable in the customer's own data center, running on customer-managed infrastructure under the customer's existing operational and security policy. Pilot timelines are longer than cloud postures (typically 6–10 weeks) because of the additional operational coordination required.
Containerized deployment on customer-managed infrastructure (Kubernetes, OpenShift, VMware Tanzu, or bare-metal). Customer-managed everything — compute, storage, network, encryption keys, audit logs, model hosting. Huper provides the software, deployment runbooks, and operational guidance; customer's infrastructure team operates the deployment.
Kubernetes / OpenShift / VMware Tanzu or bare-metal deployment options. Customer's existing container orchestration platform is supported.
Deployment is fully air-gappable — no required outbound network connectivity to Huper or any external service. Model and platform updates can be staged through the customer's existing controlled-update process.
Models are hosted on customer-managed infrastructure. No model traffic leaves the customer's environment.
Huper provides deployment runbooks, operational documentation, and the option of dedicated implementation support during pilot scoping. Customer infrastructure team owns the day-2 operations.
Fully air-gappable — no required outbound network connectivity to Huper or external services
Customer-managed everything: compute, storage, encryption keys, audit logs
Compatible with customer's existing CIS Benchmarks, STIG, or sectoral hardening standards
Models hosted on customer-managed infrastructure (no model traffic to external providers)
All audit logs remain on customer infrastructure
Air-gapped or otherwise network-isolated requirements
Sovereignty mandates that prohibit cloud deployment of regulated workloads
Government, defense, intelligence, or classified-adjacent deployments
Energy/utilities NERC CIP-scoped workloads
Workloads where the customer's security policy explicitly precludes cloud
Updates are staged through the customer's existing controlled-update process — typically signed update bundles imported through the customer's standard data-diode or controlled-network pathway, then applied during the customer's change window.
Yes. Bare-metal and VM-based deployment options are available for customers without an existing Kubernetes/OpenShift platform. Pilot scoping covers the deployment topology against the customer's existing infrastructure.
On-premise pilots typically run 6–10 weeks, longer than cloud postures because of the additional operational coordination required (network architecture, security review, change-management approvals).
Tell us your requirements. We\u2019ll architect the right deployment for your security and compliance needs.
Talk to Us