Self-Hosted Deployment

Customer-controlled cloud deployment with Huper providing software and runbooks but no operational access — for customers who want cloud convenience with on-premise-style operational control.

Self-hosted sits between cloud-hosted (Huper operates) and on-premise (customer operates in their own data center). The customer operates Beth and Isaiah on cloud infrastructure they fully control — typically AWS, Azure, or GCP — with Huper providing the software, runbooks, and engagement support but no operational access to the customer's environment.

Architecture

Customer-controlled cloud deployment in customer's AWS / Azure / GCP account. Customer's infrastructure team operates the deployment using Huper-provided runbooks and infrastructure-as-code. Updates and patches are coordinated through the customer's standard change-management process. Huper has no operational access; engagement support is via documented support channels.

Key Features

Customer operational ownership

The customer's infrastructure team operates the deployment. Huper provides the software and the documentation; the customer does day-2 ops.

Cloud cost-commit alignment

Deploy inside the customer's existing cloud commit (AWS, Azure, GCP) so the deployment economics align with the customer's existing cloud spend rather than adding a separate Huper infrastructure cost.

Customer security tooling integration

Compatible with the customer's existing cloud-security tooling — CSPM, CWPP, SIEM, vulnerability scanning, container security.

Security Features

Customer fully controls infrastructure, network, encryption keys, and audit logs

Huper has no operational access to the deployment

Compatible with customer's existing cloud-security tooling (CSPM, CWPP, etc.)

Models hosted on customer-controlled infrastructure

Audit logs flow to customer's existing logging infrastructure

Compliance Mapping

SOC 2 / ISO 27001 inherited from customer's cloud postureGDPRCustomer-imposed sectoral frameworks

When to Choose Self-Hosted

Customers with mature cloud-infrastructure operations capability

Security policies that allow cloud deployment but require customer operational ownership

Multi-region or multi-cloud strategies the customer wants to control directly

Customers with existing cloud-cost commit they want the deployment to ride on

Frequently Asked Questions

How is self-hosted different from dedicated-instance / VPC?

Dedicated-instance / VPC is operated by Huper inside a single-tenant deployment. Self-hosted is operated by the customer's own infrastructure team. Same isolation; different operational boundary.

What does Huper provide vs the customer?

Huper provides the software, infrastructure-as-code, deployment runbooks, version-update guidance, and engagement support. Customer's infrastructure team handles deployment operations, monitoring, and the day-2 ops.

Deploy with Self-Hosted

Tell us your requirements. We\u2019ll architect the right deployment for your security and compliance needs.

Talk to Us