What leaves your runner, and what never does
The recorder is built to need as little as possible. It sends paths, IDs and timings. Your code stays on your machines.
| Data | Sent to Bellwether |
|---|---|
| Test file paths and test IDs | Yes |
| Paths of the files each test loaded | Yes |
| Test durations and pass / fail results | Yes |
| Branch names and commit SHAs | Yes |
| File contents and source code | Never |
| Environment variables and secrets | Never |
| Test output and logs | Only for quarantined tests, opt-in |
Status: all systems normal, 99.98% over the last 90 days.
Common security questions
Reports and questionnaires: [email protected]
Does Bellwether need our source code?
No. The recorder runs inside your pipeline and sends file paths, test identifiers and durations. File contents never leave your runner.
Where is the map stored?
On Open source and Team, in our EU region (Frankfurt), encrypted at rest with per-account keys. On Enterprise you can run the map store in your own cloud account and we never see it.
Do you support SSO and audit logs?
Enterprise includes SAML SSO, SCIM provisioning and an audit log you can export or stream to your own log store. Team uses email sign-in or your Git host’s login.
Is there a security report we can review?
Yes. Our latest SOC 2 Type II report and penetration-test summary are available under NDA. Ask at the security address on the security page.
Found a vulnerability?
Email [email protected] with the details. We acknowledge within one working day, keep you updated until it is fixed, and credit you in the changelog if you would like.