Frequently asked questions
Grouped by setup, security and billing. Anything else goes to the contact form and an engineer replies within one working day.
Setup
How long does setup take?
Two lines in the pipeline file and one full recording run. The recording takes as long as your suite plus about four percent. Until it finishes, Bellwether selects every test, so nothing changes for your team on day one.
Which CI systems and test runners does it support?
Anything that can run a shell step: hosted runners, self-hosted runners and build farms alike. Test runners with a first-party recorder are RSpec, Minitest, pytest, Jest, Vitest, Go test, JUnit 5 and Cargo test. Others work through the generic file-access recorder.
What happens when the map is wrong?
Two rules keep a wrong map safe: a test whose map entry is older than its own file always runs, and a test that has never been mapped always runs. A full run every night compares its results with the day’s selections and flags any entry that went stale.
Can we turn it off?
Delete the two lines. Your pipeline runs the whole suite again on the next push. There is no uninstall step and no export window.
Security
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.
Billing
Who counts as an active committer?
Anyone who pushed a commit that Bellwether ran against in the billing month. Bots, release automation and people who only read the dashboard are not counted.
Is the open-source plan really free?
Yes, for public repositories under an OSI-approved licence, with no seat limit and no run limit. Private repositories need the Team plan.
What if we go over the included runs?
Team includes 5,000 selected runs a month. Beyond that it is $4 per 1,000 runs, billed at the end of the month. We email you at 80 percent, and nothing ever stops running.
Can we cancel or get a refund?
Monthly plans cancel at the end of the month. Yearly plans can be refunded pro rata in the first 60 days, no questions asked.
Still deciding?
Book 30 minutes with an engineer. Bring your pipeline file and we will tell you honestly whether selection will help.