Ito AI
AI code review that runs your app on every PR to catch runtime bugs before merge.
Ito is the only AI code review tool that runs your code before merge, catching runtime regressions that static tools miss. If you ship web apps on GitHub and rely on AI assistants, it's the difference between a comment asserting a bug and a recording of it failing. Its video evidence, severity ratings, and auto re-run on fix make triage fast. But it's web-only (native mobile is roadmap) and GitHub-only, and the Pro tier's 20-reviews-per-seat cap can bite high-volume teams. Skip it if you need native mobile testing, GitLab or Bitbucket support, or on-prem deployment. For teams that want scriptless, execution-based validation, it's a strong alternative to CodeRabbit or Claude Review, and more
Verified 5d ago · liveness 75/100 · cite: rightaichoice.com/tools/ito-ai
- Engineering teams using AI coding assistants like Copilot or Cursor
- Startups and mid-size companies shipping multiple PRs daily
- Web app teams on GitHub wanting scriptless end-to-end testing
- Open-source projects wanting automated QA on contributions
- Teams needing native mobile app testing (roadmap only)
- Organizations requiring on-premise or air-gapped deployment
- Teams that prefer GitLab or Bitbucket—GitHub only currently
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Ito if you need native mobile app testing, GitLab or Bitbucket support, on-premise or air-gapped deployment, or if you want to write and maintain your own custom test scripts.
Beyond 20 code reviews per seat per month on Pro, each additional review costs $3, which can add up quickly for high-volume teams.
Ito's Pro at $40/mo per seat with 20 included reviews is competitive against hiring a QA engineer at $120K+/year, and cheaper than maintaining Playwright suites by hand. Open-source teams get it free. For higher-volume needs, additional reviews at $3 each can make it pricier than alternatives like CodeRabbit (which may offer flat pricing), but you're paying for runtime evidence, not just diff comments. Enterprise pricing is custom, aimed at teams of 25+ engineers with security and compliance
In short
Ito AI — AI code review that runs your app on every PR to catch runtime bugs before merge. Best for Engineering teams using AI coding assistants like Copilot or Cursor, Startups and mid-size companies shipping multiple PRs daily, Web app teams on GitHub wanting scriptless end-to-end testing. Free to start; paid plans from $40/mo.
What's new in Ito AI
Checked 5 days agoAcross the latest 5 updates: 3 changelog entries and 2 news mentions.
Case Study: DoltHub Ran Ito on 43 Pull Requests
DoltHub reported a 2:1 fixed-to-dismissed ratio for Ito bug findings, and surfaced pre-existing issues in 26 of 43 tested PRs over six weeks.
Ito v1.1.16: Refreshed sign-in and sign-up experience
Authentication pages updated to clarify what Ito does and include customer proof. Fixes for telemetry, mobile navigation, and tables.
Ito v1.1.14: Fixed test runs counted toward paid-plan usage
Fixed issue where test runs completed before org started a paid plan could be counted toward paid-plan usage.
Ito v1.1.15: Fixed trial usage associated with paid billing
Fixed previously recorded trial usage that could incorrectly remain associated with a paid billing period.
MTTR is the Wrong Metric for AI-Era Engineering Teams
AI tools produce 41% more bugs and 98% more pull requests. MTTR can't keep up. MTTF shifts focus from incident response to prevention.
What people actually say about Ito AI — is it worth it?
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.
34 mentions across 3 sources (Hacker News, YouTube, Lemmy) · researched Aug 12, 2026.
- +Runs your app on every PR to catch real behavioral bugs.
- +Zero-configuration setup, connect GitHub and start in ~60 minutes.
- +Video replays and screenshots make failures easy to understand.
- +Auto re-runs on push fixes to confirm resolution.
- +Targeted test plans generated from PR diff and description.
- −Community feedback is sparse and mostly promotional, not real user testimony.
- −One Hacker News post is about a different product, causing confusion.
- −No critical reviews available to validate reliability and accuracy.
- −Pricing details unclear, hidden costs possible.
- −Potential for high resource usage and scaling costs with many PRs.
- • Potential infrastructure costs if usage exceeds included limits
- • Possible overage charges for high PR volumes or heavy usage
- • Enterprise price not disclosed, may be significantly higher
Viability Score
How well maintained and how widely used is Ito AI? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: August 2026
How we score →Key Features
- Execution-based code review: builds and runs your app on every PR
- Computer-use agents navigate UI like a real user
- Deep browser inference to detect behavioral regressions
- Scriptless end-to-end validation—no test scripts to write
- Video replay, screenshots, and reproduction steps for every failure
- Severity ratings to prioritize what to fix first
- Auto re-run on push fixes to confirm resolution
- Targeted test plans generated from PR diff and description
- Add plain-English test instructions to prioritize scenarios
- Containerized single-use sandbox testing per PR
- Authenticated flow testing including multi-factor authentication
- Framework agnostic: React, Vue, Next.js, Rails, Django, and more
- QA profile built from fix history to focus testing (v1.1.6)
- Draft PR testing via @itoqa mention (v1.1.5)
- Usage-limit notifications at 80% and 100% (v1.1.11)
About Ito AI
Ito is an AI-powered code review tool that takes a fundamentally different approach from static analyzers: instead of just reading your diff, it actually builds and runs your web app in a disposable, single-use sandbox on every pull request. It uses computer-use agents to navigate your app like a real user, exercising the flows your change touches against your real backend, and surfaces runtime bugs—broken UI logic, data flow errors, failed API integrations—that only appear when code executes. This catches behavioral regressions that static tools like CodeRabbit or Claude Review miss, because a comment that asserts a problem is no match for a recording of it failing. Ito posts detailed findings directly in your PR with video replays, screenshots, reproduction steps, severity ratings, and a prompt to fix. Push a fix, and Ito automatically re-runs to confirm the issue is resolved. It supports any tech stack for web apps and APIs—React, Vue, Next.js, Rails, Django, and more—and handles authenticated flows including multi-factor authentication. Setup is scriptless and autonomous: connect your GitHub repo, and Ito starts testing within about 60 minutes, with no test scripts to write or maintain. It also integrates with Slack for notifications. Recent updates have added a QA profile that learns from your repo's fix history to focus testing on bug-prone areas, draft PR testing via an @itoqa mention, usage-limit notifications, per-engineer overage caps, and an improved billing page with estimated charges. Ito is freemium: a free trial for your first 100 reviews, a free tier for qualified open-source projects, Pro at $40/mo for startups and small teams with 20 included reviews per seat and $3 per additional review, and custom Enterprise for larger organizations.
Behind the Verdict
Ito's core value is that it doesn't just read your code—it runs it. This is a meaningful distinction. Static analyzers like CodeRabbit or Claude Review can reason about the diff and spot potential issues, but they can't tell you if a button actually breaks when a user clicks it. Ito's execution-based approach means it catches bugs that only manifest at runtime, like service authorization failures, concurrency issues, data migration errors, and broken error handling—things that a diff review simply can't see. The evidence it produces is also a big differentiator: instead of a comment asserting a problem, you get a video replay, screenshots, and reproduction steps. This makes triage fast, because you can see exactly what happened rather than having to reproduce it yourself. For engineering teams using AI coding assistants like Copilot or Cursor, the pitch is strong: AI generates more code, and more bugs. Manual verification becomes the bottleneck. Ito automates that verification with scriptless, autonomous testing that adapts to your app. The ability to automerge with confidence is a real time-saver, as one customer noted. The setup is genuinely zero-configuration—you connect a GitHub repo and Ito figures out the flows to test. However, there are notable constraints. Ito is GitHub-only; GitLab and Bitbucket are not supported. It's web-app-only for now; native mobile testing is on the roadmap. If you need on-prem or air-gapped deployment, Ito won't work—it runs in cloud sandboxes. The pricing model also bears scrutiny: Pro is $40/mo per seat with 20 code reviews included, and each additional review costs $3. For high-volume teams, the $3 per review overage can add up quickly. Usage-limit notifications and per-engineer caps (v1.1.7) help admins control costs, but you need to be aware of the caps. Where Ito fits best is in engineering teams that ship fast, use AI assistants, and want to cut manual regression testing without writing or maintaining brittle test scripts. It's also a great fit for open-source projects (free tier) and for QA leads who want to automate the manual click-through on every PR. Where it doesn't fit: teams on GitLab or Bitbucket, teams needing mobile testing, and teams that want to write and maintain their own custom test scripts—Ito is scriptless by design. The latest news reflects active development: billing transparency (estimated charges, invoice history), usage-limit notifications, per-engineer overage caps, and a QA profile that learns from fix history. The company's stance on MTTF (mean time to failure) over MTTR is a clear signal that they're targeting prevention rather than just faster incident response. Overall, for the right team, Ito is a compelling tool that could replace a significant portion of manual QA.
Researching Ito AI? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Ito AI actually fits — and what changes day-one when you adopt it.
After connecting the GitHub repo and installing the Ito app, you enable Ito to run on every PR. When a PR from a coding agent comes in, Ito builds the app in a sandbox, runs the affected flows, and posts a comment with a video of a broken checkout flow. You see a severity rating of 'High' and a prompt to fix, and you push the fix. Ito re-runs, confirms the fix, and you automerge with confidence.
Outcome: Your team ships multiple PRs per day without a manual QA bottleneck, and you cut the 1-2 hours/day per engineer spent on manual regression verification.
You connect the GitHub org and invite your QA engineers. On the first PR, Ito automatically generates a targeted test plan from the diff and runs it. It catches a data migration bug that static analysis missed, with screenshots and reproduction steps. You triage it in minutes and assign a fix.
Outcome: You replace the manual click-through regression testing on every PR, freeing your team for strategic exploratory testing and release planning.
You install the Ito GitHub app on your repo, and it starts testing every community PR automatically. When a contributor submits a PR that breaks a login flow, Ito posts a video of the failure in the PR, and the contributor can fix it before a maintainer even looks.
Outcome: You reduce the maintainer review burden and catch regressions from community contributions, keeping your project healthy.
Use Cases
- Catch regressions before merging by automatically testing every PR in a real browser
- Replace manual 3-hour-per-week verification of AI-generated code with automated runtime checks
- Validate complex backend logic and database writes that static analysis misses
- Scale test coverage without adding QA headcount by running scriptless AI tests on each push
- Fast-track open-source contribution reviews with automated QA on every PR from external contributors
- Automerge PRs from coding agents with runtime verification as a gate, without adding a review bottleneck
Limitations
- Ito requires a GitHub integration and is designed for web applications that can be exercised through a browser.
- It does not mention support for native mobile testing or on-premise deployment.
- The free tier is restricted to qualified open-source projects with MIT or Apache licenses, and Pro plans include 20 code reviews per seat per month with additional reviews at $3 each.
- Reviews can take variable time (typically 30 minutes to 2 hours), which may delay urgent merges.
as of 2026-08-18
Verification history
We have re-verified Ito AI 6 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
12-month cost
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.
Plans compared
For each published Ito AI tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free Trial
$0
Ideal for
Teams evaluating Ito who want to try it risk-free, with no credit card required and 100 reviews to explore the runtime analysis on their own PRs.
What this tier adds
Starting entry point: first 100 reviews free, full runtime analysis, but no team management or analytics.
Open Source
$0/mo
Ideal for
Qualified non-commercial open-source projects with MIT or Apache licenses that want automated QA on community PRs at no cost.
What this tier adds
Free for approved projects: adds unlimited public repositories, video & screenshots on each run, and dedicated long-term support.
Pro
$40/mo
Ideal for
Startups and small teams shipping multiple PRs daily who need unlimited repositories, team analytics, and custom rules without enterprise overhead.
What this tier adds
Adds unlimited repositories, 20 code reviews per seat, $3 per additional review, unlimited read-only users, custom rules, and team analytics.
Enterprise
Custom
Ideal for
Teams of 25+ engineers in security-sensitive industries (financial services, healthcare, defense) needing compliance, SSO, and dedicated support.
What this tier adds
Adds security and compliance, technical enablement, custom DPA and terms, custom invoicing, and higher usage limits.
Where the pricing makes sense
The company stage and team size where Ito AI's pricing actually pencils out — and where peers do it cheaper.
Ito's Pro at $40/mo per seat with 20 included reviews is competitive against hiring a QA engineer at $120K+/year, and cheaper than maintaining Playwright suites by hand. Open-source teams get it free. For higher-volume needs, additional reviews at $3 each can make it pricier than alternatives like CodeRabbit (which may offer flat pricing), but you're paying for runtime evidence, not just diff comments. Enterprise pricing is custom, aimed at teams of 25+ engineers with security and compliance
Setup time & first value
How long it actually takes to get something useful out of Ito AI — broken out by persona, not the marketing-page minute.
Connect your GitHub repo and install the Ito GitHub App—about 60 minutes from install to first PR tested. No test scripts to write. Any admin on your GitHub organization can set up Ito, and activate other team members to try it. Free trial starts immediately, no credit card required.
Switching to or from Ito AI
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual QA: Connect your GitHub repo and Ito starts testing on the next PR—no migration of test scripts needed since it's scriptless.
- →From Playwright/Cypress: You can stop maintaining your hand-written suites; Ito generates its own test plans, though you may keep legacy suites initially.
- ↗To another code review tool (e.g., CodeRabbit): Export your PR history and comments manually; there's no automated export.
- ↗To an in-house test suite: You'd need to write your own scripts; Ito's video evidence can inform what to test, but there's no direct translation of its AI-generated flows.
Integrations
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Ito AI
Common stack mates teams adopt alongside Ito AI, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Ito Ai vs Locus Robotics
These tools solve completely different problems: Locus Robotics automates physical warehouse operations with AMRs and a RaaS model, while Ito AI automates code testing by running real code in containers. Choose Locus if you need to scale warehouse fulfillment; choose Ito if you need to catch runtime bugs before merge.
Ito Ai vs Truleo
Truleo and Ito AI serve entirely different domains: law enforcement intelligence vs. software testing. Choose Truleo if you need to connect siloed police data (RMS, jail calls, BWC) and automate lead generation; choose Ito if you need runtime bug detection on PRs. There is no feature overlap—the decision is purely based on your industry.
Ito Ai vs Presto Voice
If you're a software team shipping multiple PRs daily and want to catch runtime bugs without writing tests, Ito's automated runtime testing is a game-changer. Presto Voice is completely unrelated — it's a drive-thru voice AI for QSR chains. Choose based on your domain: code quality vs. restaurant operations. They solve different problems.
Alternatives to Ito AI
View all
Greptile
AI code review agent that runs your tests, catches 3x more bugs, and learns your team's standards.
Diamond by Graphite
AI code review agent that catches critical bugs and security issues on GitHub PRs
Frequently Asked Questions
Best-of guides
Used Ito AI? Help shape our editorial sentiment research.