Bring Your Own Cloud
For compatible scopes, Voidr components can run in the customer AWS, Azure or GCP account. The perimeter is defined during Architecture assessment.
Resources in your account
Eligible components and their processing boundaries are defined in the technical design.
Declared flows
Data, metadata, telemetry and required endpoints are documented before deployment.
Region and policies
Region, network and cost responsibilities are agreed with Cloud and Security.
How BYOC
works in practice
In a BYOC architecture, eligible resources are provisioned in the cloud account defined for the scope, with documented responsibilities.
Data and metadata flows required for operation are described in the architecture and assessed by the customer before deployment.
The model supports scenarios requiring greater control over region, network and services, subject to the approved design.