Eleven people in Manchester who got tired of waiting on test suites
We founded Bellwether in 2021 after years on build infrastructure, watching good engineers wait forty minutes for tests that could not see their change.
Where the name comes from
A bellwether is the sheep the shepherd puts the bell on. It is not the fastest or the strongest one. It is the one whose position tells you where the rest of the flock is, so you can stop counting sheep and start listening.
That is the whole product. A suite of four thousand tests contains a much smaller set whose result tells you what the four thousand would have said. Finding that set is a mechanical problem, not a judgement call, and it is a different set on every commit.
Three things we will not do
No predictions
We will not guess which tests are likely to fail. A suite you cannot trust is a suite you stop reading, so a test is skipped only when a recorded fact makes it safe.
No selection paywall
Selection, flake quarantine and the skip report are on every plan, including the free one. A cheaper tier without them would not be selling you anything.
No number without working
Every figure on the dashboard links to the runs it came from. If we cannot show the working, we do not show the number.
Who started it
Four founders, seven engineers and support people since. Everyone answers the contact form in rotation.
-
Ruth Okonkwo-Vance · CEO
Ran build infrastructure for a bank’s 900-engineer monorepo for six years.
-
Tomas Bergqvist · CTO
Wrote the first recorder; has opinions about coverage tools.
-
Ada Fennimore · Head of product
Spent four years triaging flaky tests before she was allowed to fix them.
-
Serge Iliev · Infrastructure
Keeps the map store up and the status page boring.
Talk to the people who built it.
Questions about your pipeline, a trial, or a security review. We reply within one working day.