Skip to main content
BYOC is a Braintrust-operated data plane deployed into a cloud account or project that you own. You keep the cloud boundary, billing relationship, audit policy, and governance controls. Braintrust manages the deployment, upgrades, service health, and operational response for the Braintrust data-plane services. BYOC suits teams that need sensitive AI data to stay inside their own cloud, but don’t want to take on the day-2 operations of running the data plane themselves. For a comparison with SaaS and self-hosted, see Deployment options.
BYOC requires an Enterprise plan. See Manage billing for plan details.

​
Responsibility boundary

  • Braintrust provisions the data plane in your account, and operates upgrades, scaling, monitoring, and incident response for the Braintrust data-plane services.
  • Your team owns the cloud account, billing, governance, and audit policy, and provides the access path and cloud inputs Braintrust needs to operate the deployment.

​
What you provide

With BYOC, you typically provide:
  • A dedicated cloud account, project, or subscription with billing enabled and an agreed deployment region.
  • Completion of a reviewed bootstrap or preparation step that creates the required access path for Braintrust automation and approved support events.
  • Confirmation that required quotas, regional capacity, and cloud service limits are ready for the selected deployment region.
  • Any optional customer-specific networking, DNS, TLS, ingress, private-connectivity, or egress requirements that Braintrust should account for during deployment planning. By default, Braintrust uses its standard managed networking and endpoint pattern for the selected cloud.
You also remain responsible for reviewing and managing the cloud governance controls in that environment, including organization policies, IAM constraints, allowed regions, audit-log export, SIEM routing, and billing alerts. Braintrust may ask you to confirm whether any of these controls affect the agreed deployment path.

​
BYOC or self-hosted

BYOC and self-hosted both keep your data in your own cloud. They differ in who operates the data plane:
  • Choose BYOC when you want Braintrust to operate the data plane on your behalf.
  • Choose self-hosted when your team operates the data plane and can consume Braintrust’s published Terraform modules and Helm charts.
If your organization prohibits external operator access to your cloud environment, BYOC is usually not the right fit, because Braintrust needs an access path to operate the deployment. Self-hosted is the cleaner starting point.

​
Next steps