ZHC — Zero Human Coding™
One platform. Four postures. Every boundary stated.
ZHC — Zero Human Coding™ — is the platform for autonomous enterprise software production. This page states where it runs: the four deployment postures, how ZHC operates in each, and the responsibility boundaries between your enterprise and Essert — stated per posture, never implied. The control story — what sovereignty means, and exactly what runs today versus what is platform direction — is stated in Sovereign Deployment.
One platform. Four postures. The four postures are the sections below. What the continuum does not change is the point: the lifecycle, the governance and the ownership are identical at every step.
You choose the posture at Deploy; the posture sets the environment. It never sets the result.
The control posture and the available-today line: Sovereign Deployment →
Specification to production, the same eight stages, the same two gates.
The brief and the merge stay with your people in every posture.
The work stays inside your conditions.
What your team reads and what your evaluators review belongs to you.
System, source code, infrastructure, operating artifacts. Ownership is structural.
ZHC runs in Essert’s hosted environment. The entry posture: no infrastructure program, no environment procurement. Essert holds and operates the running environment; you hold everything that governs it — specifications, policies, the two approvals — and you own the result.
A dedicated environment operated by Essert, for one enterprise. The environment is yours alone — no other customer runs in it. Essert operates it; you hold the controls and the result.
ZHC runs in your cloud account or VPC. The environment carries your name, your controls, your perimeter. You hold the account; the platform runs inside the boundaries you define.
Customer-controlled infrastructure, end to end — including supported on-premises configurations. The far end of the continuum: you hold the environment; Essert holds nothing inside it.
What runs today and what is platform direction is stated exactly in Sovereign Deployment.
Nothing is implied.
The specifications and policies
The two approvals
The operating record
The result
| Posture | The running environment | Infrastructure |
|---|---|---|
| Éssert Cloud | Essert-hosted | Essert |
| Dedicated Managed Environment | Dedicated to you | Essert-operated |
| Customer Cloud | Your account or VPC | You |
| Sovereign Deployment | Customer-controlled, end to end | You |
Who operates the platform follows your engagement model, not your posture.
Where it runs
Éssert Cloud, Dedicated Managed Environment, Customer Cloud or Sovereign Deployment.
Who runs it
Under Adopt ZHC, your team runs the lifecycle. Under Delivered with ZHC, Essert or a joint team delivers the outcome into the posture you chose.
The sanitized depth — deployment models and responsibility boundaries, at evaluation altitude — is in the gated Security Overview, alongside the security architecture and the data handling summary.
It requests only name, company, work email, role and evaluation stage.
The architecture answers them.