Skip to main content

Glossary

What is BYOC?

Last updated Monday, Aug 3, 2026

BYOC (bring your own cloud) means the platform deploys into your own AWS or GCP account instead of a vendor's shared infrastructure. Your data and compute stay inside your own cloud account, under your existing security boundary, rather than moving into someone else's.

How it differs from SaaS

A typical multi-tenant SaaS data platform stores your data in the vendor's own infrastructure, alongside other customers' data. BYOC flips that: the platform's compute and storage run as resources inside your cloud account, using your credits, your region, and your security boundary.

What this means for cost and control

Cloud compute bills separately, at your own cloud provider's rates, since it's running in your account. Your existing cloud security and compliance posture, VPC rules, IAM policies, whatever your team already enforces, applies automatically, because it is your account the platform runs in.

Related terms

  • AI data team: The AI roles that run inside your BYOC deployment.
  • Medallion architecture: The Raw, Clean, and Ready layers that live as Iceberg tables in your own cloud account under BYOC.

Frequently asked questions

OptimaFlo deploys BYOC on AWS or GCP.

Data at rest, storage and pipeline compute, run inside your own AWS or GCP account, not a vendor's shared infrastructure. OptimaFlo doesn't keep copies of your tables on its own servers.

Cloud compute is billed by your cloud provider directly, at your rates, so there is no separate infrastructure markup from the platform. Your total bill still depends on how much compute you use, the same as any cloud workload.

Browse every term or see the AI data team roles.

Staffed, not self-serve

See AI teammates work on your own data.

Start your pilotContact

Now in early beta. One flat plan, no per-query tax. Runs in your cloud, and your tables stay in your account.