Every finding carries its evidence
Every finding arrives with reproduction steps, a screen recording and environment details, so your team can go straight to fixing instead of spending the morning on "works on my machine".
ABOUT
The team that wrote the product can't test it impartially.
That isn't a criticism. Whoever builds a thing knows how it's meant to work, and without noticing takes that path every time. Users don't know; they take other paths, and nobody has tried what happens there.
Send the Canary started in 2021 with three test engineers. All three of us had worked inside product teams, and we kept seeing the same thing: as release day approached, testing collapsed into a developer walking through their own flow one more time.
Today the work is split between a core testing team and a network of 4,700 testers who work with us. The core team sets the scope, the test plan and the report; the scenarios are run by testers on their own devices, their own connections and in their own regions. We don't write features, sell consulting or ship fixes — we find issues, prove them and report them.
The name comes from the canary in the coal mine. The canary reacted before the miners did; early warning wasn't a weakness, it was how you got out alive. Software is no different: your user should not be the first to notice.
How we work
Testing is all we do
That is where the independence comes from: when the party that finds a problem is not the party that repairs it, the report stays impartial. We verify your fix afterwards, which is what makes the re-test worth having.
Scope goes in writing first
We put what will not be tested in writing too. Without a boundary, neither the price nor the delivery date means anything.
We never target a bug count
We won't promise anyone "we'll find N bugs". A number target is the fastest way to manufacture findings that aren't real.
We don't sit on bad news
If something critical turns up you hear immediately, not when the report lands. Some things can’t wait their turn.
Data is deleted in 90 days
Test data, recordings and access credentials are permanently deleted 90 days after the test ends.
Don't test the next release alongside your users.
Sign up in the panel, pick what you want tested, pay. The first findings start landing in the same panel within hours.