Trust & Control
Code Ownership & Portability
Ownership is designed in, not negotiated at the end.
ZHC — Zero Human Coding™ — is the platform for autonomous enterprise software production. Everything the platform produces belongs to the enterprise that commissioned it: the system, the source code, the infrastructure, the operating artifacts. This page states what ownership includes, when it passes, what it means in each deployment posture, and what it takes to operate independently of Essert.
Nothing leased, metered or revocable.
What you own
The inventory, in full.
Four assets. Each one transfers with the result of the lifecycle.
01
The system
The production system ZHC produced, with its status stated exactly — live in production, or production-ready and accepted.
02
The source code
The code the governed agent fleet produced for your specification.
03
The infrastructure
The environment the system runs in — owned per your deployment posture, stated below.
04
The operating artifacts
The documentation, configurations and operating records your team needs to run the system.
Nothing in that list is leased, metered or revocable. The result of the lifecycle is yours.
When ownership passes
Ownership is a property of the lifecycle.
Under Adopt ZHC, you operate the platform itself — you own what it produces from the first production run. Under Delivered with ZHC, ownership passes at handover, when the system is accepted: the source code, the infrastructure and the operating artifacts transfer to you, and the operating model becomes yours to choose.
Adopt ZHC
You operate the platform itself.
Delivered with ZHC
Ownership passes when the system is accepted.
Specify
Produce
HandoverAfter handover, the operating model becomes yours to choose.
Either way, ownership is not a renewal clause and not an exit negotiation. The line ends with you owning the result. Adopt ZHC →
Ownership by deployment postureWhat you own is constant. Who runs the environment changes.
What you own stays the same in every posture. Who controls the running environment changes with the posture you chose.
01
Essert Cloud
- System, code, artifacts
- Yours
- Running environment
- Essert-hosted
02
Dedicated Managed Environment
- System, code, artifacts
- Yours
- Running environment
- Essert-operated, dedicated to you
03
Customer Cloud
- System, code, artifacts
- Yours
- Running environment
- Your cloud account or VPC
04
Sovereign Deployment
- System, code, artifacts
- Yours
- Running environment
- Customer-controlled infrastructure, including supported on-premises configurations
† Supported on-premises configurations only — see Sovereign Deployment.
Essert-hosted postures
Portability means the system and its artifacts redeploy to your environment.
The produced system- NeedsRuntimes
- CarriesDependencies
- StepsTakeover steps
- Run byYour engineers, or a partner you choose
- No license from us
- No permission from us
- Not inside your loop
What portability means
The system runs without Essert.
Portability passes one test: the system runs without Essert. Independence has stated requirements — the runtimes the system needs, the dependencies it carries, the operational steps to take over, and who can perform them: your engineers or a partner you choose.
Those requirements are published in the Security Overview, which procurement and vendor-risk evaluators can request. Independence does not require a license from us, permission from us, or Essert inside your loop.
Availability of each posture is stated exactly — what runs today and what is platform direction.
Your data and your records
Both stay with you.
Your data
Your data is yours. Where it lives, and how it is governed, is stated in Data Handling & Residency.
Your records
The operating records transfer with the system. The audit trail your security review reads belongs to you, not to us.
- What the fleet ran
- What validation confirmed
- What each stage produced
For evaluators
Do not take this page on faith.
Procurement and vendor-risk teams can verify the claims. The gated Security Overview contains the code ownership and portability summary.
Inside the summary
The form asks only for
The platform produces, you own, and the exit is designed in.
Bring the exit question with you. It survives the meeting.