Ito

What is Ito?

Ito is an execution-based code review tool for web apps and APIs: on every pull request it deploys your application into an isolated, single-use sandbox, drives the user flows the change touches with a computer-use agent, and posts the resulting video, screenshots, logs and reproduction steps back to the PR. It is aimed at engineering teams whose coding agents now open more pull requests than humans can manually click through.

Key features

• Builds and deploys the PR branch into an isolated, single-use sandbox and exercises the running app, rather than reasoning over the diff alone
• Scriptless setup: you connect a GitHub repository and Ito infers the flows to test from your product and the pull request — no selectors or test suites to write or maintain
• Drives real user flows in a real browser (log in, navigate, fill forms, submit, verify state) using computer-use agents and browser inference
• Posts a GitHub PR comment naming the exact lines at fault, the severity, evidence and description, reproduction steps, and a prompt to fix it
• Attaches runtime evidence — video, screenshots and run logs — to every review so failures can be triaged without reproducing them locally
• Handles test-environment credentials including multi-factor authentication, with the QA agent managing sessions across the run
• Framework agnostic across web stacks; the site names React, Vue, Next.js, Rails and Django as working examples
• Does not store your code, and the company states it is SOC 2 Type II compliant

Who it's for

• Engineering teams running coding agents at volume, where PR throughput has outrun the humans available to manually verify each change
• Small teams with no dedicated QA engineer who currently lose 1-2 hours a day to clicking through regression flows on other people's pull requests
• Teams building toward automerge or an automated software factory that need a runtime verification signal before code lands
• Product teams on web stacks without an end-to-end test suite, who want coverage without committing to writing and maintaining Playwright or Cypress scripts
• Open-source maintainers on MIT or Apache non-commercial projects, who qualify for the free tier

When not to use it

Not for native mobile apps — Ito covers web apps and APIs only, with native mobile listed as roadmap — and not for anything that cannot be built and run in an ephemeral sandbox with test credentials; reviews also take roughly 30 minutes to 2 hours, so it is not a merge gate that returns in seconds, and it explicitly does not replace exploratory testing, strategic QA or release planning.

FAQ