An approved issue becomes a review-ready PR.
With evidence against the acceptance criteria, a Greenlight grade from a separate reviewer and a plain account of what remains uncertain. Start smaller: connect a repo and get a second review of the PRs you already have, before anything writes code.
A second reviewer first. An engineer when you are ready.
A second review of the PRs you already have
Connect a GitHub repo and the QA Teammate reviews the pull requests your team is already opening, with inline findings checked against the issue and your repo's conventions. It does not replace your review. It adds the useful findings your existing review missed.
Greenlight: graded 1 to 6 on a fixed rubric
Greenlight, our reviewed and graded change workflow, scores correctness, verification, scope and risk from the facts in the diff, each with a file and line, before it reads the PR description. Out of the box it comments only. Turn approve mode on and it approves at grade 5 or 6, your choice, on the exact commit it graded, and withdraws when the next push falls short.
Evidence, not narration
When the Engineer Teammate opens a PR, the body carries its test plan with command output: the test that failed before the change and passes after it, mapped to the acceptance criteria, and ends with what remains uncertain and the questions only a human can answer.
A QA agent grades every change
A change that falls short goes back to the engineer, and with approve mode on only a change at your grade is approved. Your branch rules decide what merges. CI config, keys, certificates and secret files are never auto-approved; add your own protected paths.
From issue to merge, every step leaves a record.
-
1
Issue
You approve an issue in your tracker. Nothing starts without one.
-
2
Spec
The Product Teammate interviews you and writes numbered acceptance criteria into the issue.
-
3
Failing, then passing tests
The Engineer Teammate writes the test first, shows it failing for the stated reason, then makes it pass.
-
4
Greenlight grade
The QA Teammate reviews the PR against the spec, your repo's past failure patterns and its conventions, and grades it 1 to 6 on a fixed rubric. The Engineer answers every finding, and every push is graded again.
-
5
Approved or sent back
With approve mode on, only a change that earns your grade is approved. Anything short goes back to the engineer, and your branch rules decide the merge.
What a teammate on its own server does that a per-seat review tool does not.
Runs your code, not just reads it
The Engineer Teammate works on a dedicated server that keeps your repo checked out and runs your tests before it opens a PR.
Remembers your repository's past failures
Review comments and fix PRs feed a failure-pattern file for your codebase. The engineer and the reviewer both read it before their next pass.
Implements as well as reviews
The same lane that reviews your PRs can take an approved issue to a pull request when you want it to.
Teammates are not billed per person
The plan is one flat price for any number of people. The product, engineer and QA teammates share one server, so the lane costs a server, not three more charges.
One engineering lane, priced at list.
Product, engineer and QA teammates on one server. Templates and setup are free. The Pro plan is one flat price for any number of people and includes one Standard Small server and 20 GB of storage. Anything beyond that, and model usage, is billed as you use it, like any other Teammate.
| Pro plan, any number of people | $100/mo |
| Server: Standard Medium, 2 vCPU / 8 GB | $108/mo |
| Included server credit: one Standard Small server | −$71/mo |
| Disk beyond the included 20 GB: 0 GB | $0/mo |
| Model usage | Billed at provider list rates, depends on volume |
| Fixed monthly before model usage | $137/mo |
Cost ceiling
Model usage draws from a prepaid account balance. With automatic top-up off, your teammates stop when the balance runs out instead of running up a bill. With it on, you choose the threshold and the top-up amount.
Book a 30-minute look at the demo repository.
We will walk you through a repository where our own product, engineer and QA teammates work in the open: issues, specs, pull requests, findings and the QA grade. Then we talk about your repo.
Get Started