Our Story

Built by engineers who got tired of maintaining broken tests

BotGauge was founded in San Francisco in 2022. We are a four-person team that believes autonomous test management should be the default — not the premium add-on.

Our mission

In 2022, Michael Hoy was consulting at a developer tooling company in SoMa when the QA lead left and the team reverted to shipping without a test suite. Releases started slipping. The fix was obvious — but the fix was also a part-time job: writing Playwright scripts, maintaining selectors, debugging flaky failures in CI. Nobody had time for that on top of feature work.

That conversation kept repeating. Every engineering team had the same problem: tests were too brittle, too expensive to maintain, or both. BotGauge was built to make the self-managing test suite the default — not an expensive enterprise luxury.

We are not a test scripting tool. We do not expect your engineers to learn a new test DSL. BotGauge's agent generates tests from your live app, runs them in your CI/CD pipeline, and fixes broken selectors autonomously. The team ships. The tests keep up.

In mid-2025 we closed an angel round of $750K from individual investors in the developer tooling space. We remain a small, focused team — four people shipping fast and staying close to customers.

The team

Michael Hoy, Founder and CEO of BotGauge
Michael Hoy
Founder & CEO
Sarah Chen, Head of Engineering at BotGauge
Sarah Chen
Head of Engineering
Jorge Navarro, Product at BotGauge
Jorge Navarro
Product
Aisha Okafor, Customer Success at BotGauge
Aisha Okafor
Customer Success

What guides us

Zero test debt

If a test breaks silently, it's not a test — it's dead weight. We build BotGauge to surface failures loudly and fix them before they accumulate.

Reliability before velocity

A flaky CI gate trains engineers to ignore test results. We would rather ship a smaller feature set that every developer trusts than a full platform nobody believes.

Explainable decisions

Every test BotGauge generates, every selector it patches, every coverage gap it flags — all of it is visible in your dashboard and linked to the pull request that triggered it.