Deployment
Deploy at the boundary you control.
Start with local packages, add managed execution where available, and embed review without surrendering your product’s identity or permissions.
four surfacesHow this surface works
The interface may change. The operation and evidence contract does not.
Versioned operation
Inputs, outputs, options, losses, and errors stay behind one inspectable contract.
Target preflight
The destination profile and validators run before an artifact enters delivery.
Bound evidence
Artifact identity, rules, execution, and decisions resolve from one durable receipt.
Operational sequence
State advances only with evidence.
Every step has an observable input, result, and release consequence.
- 01
Local SDK
Run deterministic operations in the runtime and data boundary you already own.
available by item - 02
Hosted API
Use authenticated managed jobs for supported public operations.
capability gated - 03
Embedded review
Keep exceptions and approvals inside the host product experience.
design partner
Availability
Claims follow the registry.
Private deployment is a future boundary. It is not represented as generally available.
Inspect current capability evidence