Ito

Ito is an AI QA engineer that connects to GitHub repositories and automatically runs browser-based, execution-based tests on every pull request. It builds and runs your app from source in an isolated, single-use sandbox, then posts a detailed bug report as a PR comment — complete with video recordings, reproduction steps, severity ratings, and code analysis. No test scripts to write, no flaky test suites to maintain.

What It Is

Ito sits in the code review workflow as an execution-based behavioral testing layer. Unlike static analysis tools or AI code reviewers that reason about diffs, Ito actually runs the application — frontend and backend together — and exercises real user flows to catch runtime bugs that only appear when code executes. The company describes it as "the only code review tool that runs execution-based behavioral tests on every pull request to provide scriptless end-to-end validation and automated QA reports." It is SOC 2 Type II compliant and targets engineering teams across financial services, healthcare, and defense.

How It Works

When a pull request opens, Ito reads the diff and PR description, then builds a targeted test plan focused on the user flows the change affects. It provisions a containerized, single-use copy of the app from source, navigates it like a real user using computer-use agents and deep browser inference, and exercises both happy-path and adversarial edge cases. Findings are posted inline on the PR with:

• Video replay of the failure
• Exact lines of code responsible
• Reproduction steps
• Severity ratings
• A suggested fix prompt
• Automatic re-run after a fix is pushed

Setup is described as autonomous and scriptless — connect a GitHub repository and Ito begins testing within about 60 minutes, with no configuration required.

What Sets It Apart from Static and Script-Based Tools

Ito positions itself against three categories of alternatives:

• Static AI reviewers (e.g., Cursor's BugBot, CodeRabbit, Greptile): These post comments based on diff analysis but cannot catch bugs that only manifest at runtime, such as broken UI logic or failed API integrations.
• Script-based E2E frameworks (e.g., Playwright, Cypress): These require engineers to write and maintain test scripts that break when the UI changes. Ito generates test cases from the app's actual behavior and adapts automatically as the UI evolves.
• Manual QA: Ito automates the 1–2 hours per day engineers typically spend manually clicking through flows on PRs.

The vendor claims that 81% of bugs it finds are unique to runtime, and that customers report 50% fewer regressions and 10x more coverage without additional headcount.

Stack and Integration Support

Ito is framework-agnostic and works with any web stack, including React, Vue, Next.js, Rails, and Django. It integrates with GitHub (via a GitHub App) and Slack. It supports authenticated user flows including multi-factor authentication, and manages sessions automatically. Native mobile testing is listed as on the roadmap. The docs describe three setup steps: sign up, connect a repository, and open a pull request — after which Ito begins monitoring automatically.

Security and Enterprise Readiness

Ito is built with a security-first architecture targeting enterprise customers. Key security properties include:

• SOC 2 Type II certification with independent audits and reports available on request
• End-to-end encryption with zero data retention — source code is never stored
• Isolated, single-use sandbox environments for every test run
• SSO, audit logs, and dedicated support for enterprise customers
• Custom DPA and terms of service available for enterprise agreements