An explicit data boundary
Engineering content stays customer-side. Select a data type to inspect what can cross and what must remain.
Customer environmentVendor capability cloud
Capability request
Only fixed control facts needed for capability delivery cross.
Data-path illustration · not live traffic
Delivery still needs checks
The cloud publishes capabilities. Local checks confirm authorization, version, signature and digest before use in a task.
Authorized
A device retrieves only capabilities it is authorized to use.
Signed
The local AI BOX checks the package signature and content digest.
Versioned
Capability information and package versions belong to the controlled delivery record.
Reviewed
The engineer approves controlled operations and reviews the result.
Responsibility on each side
- Customer-side
- Engineering files, software permissions, physical access and root privileges remain under the customer’s own security controls.
- Capability cloud
- Retains only fixed records needed for publishing, authorization, delivery and necessary metering.
- Task records
- State and recovery remain in the customer environment. Long-task recovery is in Technical Preview.
Discuss deployment boundaries in your engineering environment.
Contact the team