About
Writing code has become cheap. Knowing it works hasn't.
AI coding agents can produce a pull request in minutes. Checking that it does what it should still takes people, time and good tests. RuyQA is built to close that gap. It tells you, for every change, whether your tests show that it works.
How we build it
Evidence decides.
A verdict comes from test results and which code those tests cover. A model can help write a bug report or suggest why a test is flaky, but it never decides whether a change is Verified.
Say so when we don't know.
When there isn't enough history to call a test flaky, or no browser to look at a page, the agent says that. It doesn't make something up to fill the gap.
A person approves.
Tests that an agent writes are saved as drafts. A rewritten test that passes is flagged for review, and is never counted as a pass. Your data exports as JSON and CSV, so it isn't stuck here.
The name
Named after a chess opening.
RuyQA is named after Ruy López, a Spanish priest who wrote one of the first serious books on chess, in 1561. The opening that carries his name is still played today.
The product uses the same language. A change is a move, and it is either proven or it isn't. A change that has earned its evidence is promoted, and a change in trouble is in check. Ruy, the knight on our pages, is the mascot. It shows up on loading screens and empty states. It never gives a verdict, because the verdict seal does that.
Ruy, settled. This is the mood for a Verified change.
Who builds it
RuyQA is built by Tensflare Inc., a small team. We start with teams in Africa, where QA tools are usually priced in dollars, billed by card and built for a large manual QA department. RuyQA takes payment in naira, cedis, Kenyan shillings and rand, and it is built for developers who ship with AI agents.
Talk to us, or try it.
If you ship with AI coding agents, or you run a QA team, we would like to hear how you check changes today.