Sovereign Deployment

Sovereignty is who holds control. Not where the servers sit.

ZHC — Zero Human Coding™ — is the platform for autonomous enterprise software production. Sovereign Deployment is the platform’s customer-controlled posture: ZHC runs on infrastructure you control, including supported on-premises configurations — the far end of a continuum that begins at Essert-hosted. Sovereignty is a control posture, not a synonym for on-premises. Every claim on this page distinguishes what runs today from what is platform direction.

The sovereign postureIllustrative
InfrastructureYou
Data residencyYou
AccessYou
The two approvalsYou
The resultYou

Control is a property of the posture, not the address.

Sovereignty is not a location. It is a set of controls.

An on-premises server is a location. Sovereignty is who holds the keys: who controls the infrastructure, who decides where data lives, who authorizes access, who approves what gets built and what ships. You can host a system on-premises and hold no sovereignty — a vendor who holds the keys in your basement still holds them. And you can hold a fully sovereign posture in a cloud account that carries your name and your controls.

The sovereign posture means control rests with the enterprise: your infrastructure where you choose it, your data under your residency rules, your access policies, your two approvals — the brief and the merge — and your code at the end. Those attributes travel with the posture, not with the address.

Who holds the keys
Where it runs ↓
A vendor
You
On-premises

A location, not sovereignty

A vendor who holds the keys in your basement still holds them.

Sovereign

Supported on-premises configurations under your control.

Platform direction

Cloud account

Essert-controlled

Essert Cloud and Dedicated Managed Environment. Not the sovereign posture.

Sovereign control attributes

A cloud account that carries your name and your controls.

Available today

Sovereignty moves along the keys axis, not the address axis.

One platform. Four postures.

Control over the running environment increases along the continuum. The two approvals and the result stay with you in every posture.

 

Essert Cloud

Essert-hosted environment

Available today
Running environmentEssert-controlled
The two approvalsYou
The resultYou

 

Dedicated Managed Environment

Dedicated environment operated by Essert

Available today
Running environmentEssert-operated, dedicated to you
The two approvalsYou
The resultYou

 

Customer Cloud

Your cloud account or VPC

Available today
Running environmentYou control
The two approvalsYou
The resultYou

 

Sovereign Deployment

Customer-controlled infrastructure, including supported on-premises configurations

On-premises: platform direction
Running environmentYou control, end to end
The two approvalsYou
The resultYou

The posture determines who holds the running environment — never who holds the result. The system, the source code and the operating artifacts are yours in all four.

You do not adopt our stack to gain control.

The sovereign posture extends to infrastructure you already control — your cloud accounts today, your facilities in platform direction.

Available today

Your cloud accounts

ZHC operates in three postures today:

  • Essert Cloud
  • Dedicated Managed Environment
  • Customer Cloud

Customer-controlled cloud accounts and VPCs carry the sovereign posture’s control attributes:

  • Your infrastructure
  • Your access policies
  • Your two approvals
  • Your operating record
  • Your code

Platform direction

Your facilities

Sovereign Deployment: customer-controlled infrastructure, including supported on-premises configurations.

This page does not announce capabilities before they run.

When an on-premises configuration is supported and running, it appears here as available today, with its requirements stated exactly. Until then it is stated as direction — and direction is never sold as today.

What you hold in the sovereign posture: the inventory a sovereignty claim must survive.

Verified control attributes. Six of them.

  • Infrastructure

    The environment the platform runs in, under your control in the sovereign posture.

  • Data location and residency

    Your residency rules govern.

    Data Handling & Residency →

  • Access and identities

    Your policies govern who and what touches the system.

  • The two approvals

    The brief and the merge stay with your people in every posture.

  • The operating record

    Governance runs with the platform in every posture — MADAM inside ZHC — and the record your team reads is yours.

    MADAM →

  • The result

    System, source code, infrastructure, operating artifacts. Ownership is structural.

    Code Ownership & Portability →

Sovereignty language on this site names these attributes and nothing else.

Regulated evaluations do not take this page on faith.

The gated Security Overview contains the deployment models, the responsibility boundaries in each posture, and the data handling and residency summary.

Inside the summary

The deployment models
The responsibility boundaries in each posture
The data handling and residency summary

The form asks only for

Name
Company
Work email
Role
Evaluation stage

Sovereignty is who holds control — and in the sovereign posture, that is you.

Bring the control requirements. They shape the posture, not the other way around.