
AI code review that actually runs your code to catch runtime bugs pre-merge.
By Tanmay Verma, Founder · Last verified 03 Jul 2026
In short
Ito — AI code review that actually runs your code to catch runtime bugs pre-merge. Best for Engineering teams shipping AI-generated code, Startups wanting to scale QA without hiring, Teams tired of flaky test suites and manual regression. Free to start; paid plans from $40/mo.
See what real users actually say. We scan live discussions, reviews and complaints across the web and hand you an honest verdict — in under a minute.
3 free scans · no card needed · downloadable report
Ito fills a genuine gap by actually running code rather than just reading it. For teams overwhelmed by AI-generated PRs, it's a game-changer. However, the pricing may be steep for large teams, and the 45-minute+ test time won't suit all workflows.
Compare with: Ito vs OpenHands, Ito vs Draftbit, Ito vs Cognition AI
Last verified: July 2026
Across the latest 10 updates: 5 feature updates, 3 changelog entries and 2 news mentions.
Argues runtime evidence is needed beyond static analysis to catch integration and end-to-end issues.
Ito adds text-based evidence and threaded PR comments with inline replies on code lines.
General performance and stability improvements.
Inline PR comments are now anchored to exact diff lines where issues are found.
Allows per-repo automation toggle, supports multiple screenshots, improved onboarding and PR page.
Adds severity filter to PR table and updates comment format for clearer findings.
Dashboard UI/UX polish and a fix for Test Instructions settings permissions.
Introduces inline PR comments within GitHub.
Fixes a UI selection crash and issues with GitHub App installation authentication.
Argues that 3-5x developer productivity via AI requires scaled operations and processes.
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
61 mentions across 5 sources (Hacker News, YouTube, Product Hunt, GitHub, Lemmy).
How likely is Ito to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →Ito is an AI-powered QA agent that automatically tests every GitHub pull request by building and running your app in a real browser. It targets the specific flows affected by a change, executes both frontend and backend logic, and returns a detailed report with video replays, logs, and reproduction steps—all without requiring any test scripts or maintenance. Designed for engineering teams shipping with AI-generated code, Ito eliminates the manual regression testing bottleneck. It works by reading the PR diff and description, generating a targeted test plan, provisioning a containerized environment from source, and exploring the app like a real user. Failures are posted directly as PR comments with severity ratings. What sets Ito apart is its infrastructure that actually executes code—catching behavioral bugs that static analysis (like CodeRabbit or Claude code review) misses. It claims to catch 30% more bugs than those tools by testing runtime behavior rather than just reading diffs. The tool integrates as a GitHub check, is configurable per repo, and typically starts testing within 60 minutes of installation.
Ito tackles a problem that's becoming more acute as AI code generation accelerates: how to verify that code actually works at runtime, not just looks right on review. Unlike static analysis tools that only read diffs, Ito builds and runs the application, catching behavioral bugs that would otherwise slip into production. In practice, it's surprisingly easy to set up—connect your GitHub repo and within an hour you'll see results on PRs. You can add custom test instructions in plain English, and the AI adapts to UI changes automatically, so you're not stuck maintaining brittle selectors. Where it bites: the 45-minute to 2-hour test time is too slow for teams that expect sub-10-minute CI feedback. If you're a startup shipping fast with AI-generated code, Ito can save your engineers hours of manual clicking per week. But if you need lightning-fast iteration or test native mobile apps, look elsewhere. Compared to CodeRabbit or Greptile, Ito is the only option that actually executes code—so it finds bugs those tools miss entirely. For open-source projects with MIT/Apache licenses, the free tier is a generous offer.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Common stack mates teams adopt alongside Ito, with the specific reason each pairing earns its keep.
Used Ito? Help shape our editorial sentiment research.