A described future, not an available product.
This page explains where a private, self-hosted deployment would sit. It does not sell one, because no distribution, installer or hosted tenancy exists today.
Your browser / dashboard
│
Your CLI ──────────────┐
│ │
Your API deployment ────┼── private network, customer-controlled
│ │
Local artifact processing
│
Customer-controlled roots / pinsEvery box in this diagram would be operated by the customer. Verify would not hold your roots, your pins, or your artifacts.
The limits that would shape a private deployment.
Key custody, trusted time and single-use guarantees all bear directly on what a private topology could promise. Each of those is recorded, with its source, on one page rather than restated here.
Read status & limits →How a private deployment would work.
How this works
- 01
Every component would run on your side
Browser, CLI, API deployment and artifact processing all sit inside your network. Nothing would phone home for an answer.
- 02
You would hold your own roots and pins
The digests that define what an artifact is supposed to be are yours. Verify would compare against them, never supply them.
- 03
Artifacts would never leave your systems
Processing happens locally, which is the same property the browser demo already has, extended to the whole deployment.
- 04
The assessment would still grant nothing
A private deployment changes where the engine runs. It does not change what the engine is allowed to conclude.