Skip to main content

Buyer guide

Braintrust Data Plane, Hosting & Security Checklist

Choose a US or EU region, BYOC, or self-hosting before launch. Then move model API keys to short-lived credentials and set access and redaction.

Reading time
3 min read
Sources
18 cited

Pick the Braintrust data plane before production traces flow, because the US or EU SaaS region cannot change after sign-up. BYOC and self-hosting require Enterprise. After the May 2026 incident, connect organization-level providers through workload identity federation or assume-role, and put a provider-side spend limit on every key you still store.

When you need this

  • Security or legal must approve sending prompts, retrieved documents, and model output to a third party.
  • You serve EU residents, regulated data, or customers with residency terms.
  • You plan to store AI provider keys in Braintrust for playgrounds, scorers, or the Gateway.

Evaluation criteria

  1. Training and contract terms

    Does Braintrust use your data?

    Look forBraintrust's MSA bars it from using customer data to train or develop AI models, including model improvements. Pro includes a click-through DPA. Enterprise adds custom DPAs and legal terms, a HIPAA BAA, and the SOC 2 Type II report.

  2. Control plane and data plane

    What sits where?

    Look forThe data plane stores experiment, log, and dataset records, playground prompts and completions, human review scores, and project-level provider secrets. Braintrust always runs the control plane, whatever the hosting option. The control plane holds project and experiment names, git metadata, organization settings, API key hashes, and organization-level provider secrets. Clerk handles sign-in.

  3. Region

    Where does trace data live on the cloud plans?

    Look forChoose the US or EU data plane when you create the organization. You cannot change it afterward. Braintrust's security page recommends EU-resident BYOC or self-hosting for full GDPR compliance. Ingestion redaction sends selected text outside the EU, even for EU organizations.

  4. BYOC or self-hosted

    Must data stay in your own cloud?

    Look forBoth require Enterprise. With BYOC, Braintrust operates the data plane inside your cloud and needs access to it. With self-hosting, your team deploys Terraform modules on AWS, GCP, or Azure, upgrades once or twice a month, and staffs on-call. Health and usage telemetry goes back to Braintrust until you turn it off. One self-hosting team caught a cold-start call to braintrust.dev. Another reported vulnerable dependencies in the published images for weeks.

  5. Provider keys

    How are AI provider credentials held?

    Look forIn May 2026, an attacker used a compromised employee credential to reach decrypted AI provider keys in a migration backup. Braintrust found the activity limited to Anthropic keys, and 30 customers reported suspicious key use. Hosted organizations now connect OpenAI, Anthropic, Google Vertex AI, and Azure AI Foundry through workload identity federation, and Bedrock through assume-role. Both need a Braintrust-hosted organization, and workload identity federation covers organization-level providers only. Project-level providers and self-hosted deployments still store keys, so set a spend limit on each at the provider and rotate on a schedule. Braintrust flags provider keys older than six months on its secrets page.

  6. Mask before upload

    Which fields must never be traced?

    Look forStrip sensitive values with SDK masking or span customizers before they leave the application. One team keeps Braintrust switched off until it has a signed DPA, 30-day retention, and a tested deletion path.

  7. Access and audit

    Who can see which projects?

    Look forStarter has only the Owner group. Pro adds the Engineer, Viewer, and All AI Provider Access groups. Enterprise adds custom groups, project and object permissions, SAML or OIDC SSO, domain mappings, and audit logs kept for the life of the subscription. Since October 2026, organization owners can list every member's API keys through the API. If logs contain untrusted image URLs, block rendering or require click-to-load.

Questions to ask vendors

  1. Which region did we choose at sign-up, and does it satisfy every customer contract?
  2. Which provider keys are stored in Braintrust, and can each move to workload identity or assume-role?
  3. Which fields are masked in the SDK, and who reviews the masking code?
  4. Do we need BYOC or self-hosting, and can we staff upgrades and on-call for a self-hosted data plane?
  5. Who can read production traces today?

Red flags

  • Organization-level provider keys stored with no spend limit at the provider and no rotation since May 2026.
  • An EU contract served from a US data plane, which cannot be moved after sign-up.
  • Relying on ingestion redaction for data that must never leave the application.
  • A self-hosted data plane more than three months behind, which Braintrust treats as unsupported.

Products in this piece

Sources

Official documentation
15
Public source
3
  1. Braintrust Master Subscription AgreementOfficial documentationbraintrust.dev
  2. Braintrust docs: SecurityOfficial documentationbraintrust.dev
  3. Braintrust docs: Architecture (control plane and data plane)Official documentationbraintrust.dev
  4. Braintrust docs: Organizations and data plane regionOfficial documentationbraintrust.dev
  5. Braintrust docs: Deployment options (SaaS, BYOC, self-hosted)Official documentationbraintrust.dev
  6. Braintrust docs: Bring your own cloud (BYOC)Official documentationbraintrust.dev
  7. Braintrust docs: Self-hosting BraintrustOfficial documentationbraintrust.dev
  8. Braintrust docs: Protect sensitive dataOfficial documentationbraintrust.dev
  9. Braintrust docs: Authentication, API keys, and provider credentialsOfficial documentationbraintrust.dev
  10. Braintrust docs: Access controlOfficial documentationbraintrust.dev
  11. Braintrust docs: Audit logsOfficial documentationbraintrust.dev
  12. Braintrust docs: Plans and limitsOfficial documentationbraintrust.dev
  13. Braintrust Trust Center: Updates, including the May 2026 security incident reportsOfficial documentationtrust.braintrust.dev
  14. Braintrust blog: Supporting privacy and compliance for EU teams (Mar 12, 2026)Official documentationbraintrust.dev
  15. Braintrust docs: Product updates (workload identity federation May and June 2026, key-rotation warnings May 2026, usage analytics by project Sep 2026, organization API key listing Oct 2026)Official documentationbraintrust.dev
  16. bt issue #384: self-hosted daemon contacts braintrust.dev on cold start (Sep 25, 2026)Public sourcegithub.com
  17. helm issue #86: self-hosted data plane images ship a vulnerable starlette (May 28, 2026)Public sourcegithub.com
  18. Tech Fleet pull request #433: keep Braintrust off until DPA, retention, and deletion are confirmed (Oct 10, 2026)Public sourcegithub.com