Bring Your Own Cloud

Bring Your Own Cloud lets an organization power its product with infrastructure inside its own AWS account or GCP project.

MIOSA remains the orchestration and product control plane.

Activation gated Infrastructure packages built

Control plane and customer cloud

The customer controls the cloud account, network, identity policies, provider resources, and provider bill.

MIOSA controls desired capacity, workload placement, immutable runtime generations, acceptance, scheduling, drain, and reconciliation.

Layer	MIOSA control plane	Customer cloud
Organization and workspace policy	Yes	No
Desired capacity and placement	Yes	Reflected by worker capacity
Provider IAM and networking	Validated and orchestrated	Created and owned
Worker hosts	Observed and scheduled	Executed and billed
Firecracker workloads	Requested and tracked	Executed
Host runtime artifacts	Identified and verified	Downloaded and installed
Customer data stores	Bound by the application	Customer-selected
Acceptance evidence	Recorded	Produced by the host

Terraform and CloudFormation packages define private multi-AZ worker foundations, scoped IAM, immutable templates, and fail-closed acceptance.

Terraform defines the service account, network, firewall, instance template, artifact access, and acceptance handoff.

Infrastructure creation does not make a region live.

Placement begins only after provider preflight, one real host acceptance, recorded evidence, and explicit enablement.

	Bring Your Own Cloud	OpenComputers
Unit	Governed cloud region or host pool	Individual owned machine
Provisioning	Terraform or CloudFormation	Agent installation
Network	Customer VPC or subnetwork	Existing host network
Identity	Cloud IAM and instance identity	MIOSA host registration
Capacity	Provider fleet	Connected machines
Best for	Enterprise cloud boundaries	Local and owned hardware