What is Canary?

A clear overview of what Canary does and how teams use it day to day.

Canary is a QA tool that tests your product the way a user would, then turns what it finds into clear, trackable issues.

It’s built to help teams catch regressions earlier, keep coverage up as the product changes, and spend less time on repetitive manual checks.

How it works (the core loop)

Add a property: Tell Canary which site/app to test (often an environment like production or staging).
Add login credentials (optional): If parts of your app require sign-in, Canary can log in to reach and test those pages.
Crawl: Canary explores the app to discover pages and build a map of what it can reach.
Explore and create flows: Turn important user journeys (sign in, checkout, invite teammate) into repeatable flows.
Run QA: Canary runs page checks and flows, collecting evidence like screenshots and traces.
Run a smoke suite before release: Group your most important flows into a small suite you can run on every release for fast confidence.
Review issues: Canary groups failures into issues, tracks when they first/last happened, and helps you prioritize by severity and category.
Connect your tools: Optionally sync with tools like Jira or Slack so issues and updates land where your team already works.

Coverage that stays current: Crawls and runs adapt as navigation and pages change.
Faster triage: Issues come with context and evidence so you can debug quickly.
Health over time: See whether pages and flows are getting better or worse as you ship.