Ito
AI code review that runs your app on every PR to catch runtime bugs pre-merge
Ito earns its keep if you ship a lot of AI-generated code and want runtime proof, not just diff comments, before merge. The 30-min–2-hr test window and GitHub-only integration are real trade-offs, and the $3-per-review overage can sting for high-volume teams. But the video evidence, scriptless setup, and self-healing tests beat writing/maintaining Playwright suites. Try the free 5-PR trial; if you need GitLab or sub-minute CI, hold off.
Verified 6d ago · liveness 72/100 · cite: rightaichoice.com/tools/ito
- Engineering teams shipping AI-generated code at high velocity who need pre-merge runtime verification
- Startups wanting to scale QA without hiring dedicated QA engineers
- Teams tired of flaky, script-heavy E2E test suites (Playwright/Cypress) and manual regression
- Organizations with high PR volume needing evidence-rich, autonomous review
- Teams using GitLab or Bitbucket (GitHub-only integration)
- Products requiring native mobile or desktop app testing (native mobile on roadmap only)
- Teams needing exploratory or strategic QA—humans still required
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 use GitLab or Bitbucket (GitHub-only), need sub-minute CI feedback (test times 30min–2hr), test native mobile/desktop apps, or expect strategic exploratory QA—it's runtime verification, not human judgment.
Going past 20 code reviews per seat/month on Pro adds $3 per review, which adds up fast for busy repos.
Ito's Pro at $40/mo per seat with 20 reviews is cheaper than hiring a QA engineer ($120K+/yr) and avoids Playwright maintenance. Compare to CodeRabbit's ~$18/mo starter (static only) and Mabl's enterprise pricing. For startups shipping lots of AI code, Ito's $40/mo is a budget-friendly QA layer; for high-volume teams, the $3/review overage may push you to Enterprise custom pricing.
In short
Ito — AI code review that runs your app on every PR to catch runtime bugs pre-merge. Best for Engineering teams shipping AI-generated code at high velocity who need pre-merge runtime verification, Startups wanting to scale QA without hiring dedicated QA engineers, Teams tired of flaky, script-heavy E2E test suites (Playwright/Cypress) and manual regression. Free to start; paid plans from $40/mo.
What's new in Ito
Checked 2 days agoAcross the latest 10 updates: 6 feature updates, 1 changelog entry and 3 news mentions.
Why AI Code Review Needs to Read Your Code and Run It
Guide on combining static and runtime analysis in AI code review, covering what each catches and why teams use both.
DoltHub Ran Ito on 43 Pull Requests: 2:1 Fixed-to-Dismissed Ratio
DoltHub reported 2:1 fixed-to-dismissed ratio for Ito bug findings, and surfaced pre-existing issues in 26 of 43 tested PRs over six weeks.
v1.1.16: Refreshed sign-in/sign-up flow and mobile navigation fixes
Auth pages now clarify product value. Fixed telemetry double-fire; improved mobile navigation, tables, settings layouts.
v1.1.15: Fixed trial usage wrongly counted in paid billing period
Fixed previously recorded trial usage that could incorrectly remain associated with a paid billing period.
v1.1.11: Usage-limit email notifications
New usage-limit notifications. Contributors get emails at 80% and 100% of included usage; admins get daily digest when teammates blocked.
v1.1.13: Team usage bar changes color on overage
Team usage bar now changes color across the full bar when entering overage or reaching usage cap.
Your fastest model is probably not your fastest model
Tokens per second measures emit speed, not finish speed. 13-model probe shows gap that flips speed and cost leaderboards.
v1.1.9: Billing page shows estimated charge and invoice history
Billing now shows estimated charge, finalized invoices, and overage totals. Usage now counts successful test runs including re-runs.
v1.1.7: Set per-engineer monthly overage limit
Admins can cap PR reviews per engineer per billing period. Usage bars show included reviews and overage spend. Blocked PRs get explanatory comment.
v1.1.6: Ito learns from repository fix history
Ito now learns from your repository's fix history to focus testing. Also included general fixes.
What people actually say about Ito — 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.
73 mentions across 6 sources (Hacker News, YouTube, Product Hunt, Bluesky, GitHub, Lemmy) · researched Jul 27, 2026.
- +Catches runtime bugs static analysis misses.
- +No test scripts needed—zero maintenance for QA.
- +Provides video replays and reproduction steps for failures.
- +Generates targeted test plans from PR diff and description.
- +Integrates as GitHub check with automatic re-run on push.
- −Community feedback is very limited outside a few HN posts.
- −Does not explicitly support backend-only repos.
- −Self-healing may mask real regressions.
- −New tool—long-term reliability unproven.
- −Only integrates with GitHub, not GitLab or Bitbucket yet.
Viability Score
How well maintained and how widely used is Ito? 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
- Builds and runs your app on every PR in a containerized sandbox
- Generates targeted test plans from PR diff and description
- Executes frontend and backend logic end-to-end
- Provides video replay, logs, and reproduction steps on failures
- Ranks findings with severity ratings
- Supports authenticated flows including MFA
- Framework-agnostic for web apps and APIs (React, Vue, Next.js, Rails, Django)
- Zero test scripts to write or maintain
- Self-healing adapts to UI changes automatically
- Learns from repository fix history (v1.1.6)
- Proposes fixes as PRs via self-healing codebase feature
- Automatic re-run on push until pass
- GitHub check integration with PR comments
- Usage-limit email notifications at 80% and 100% (v1.1.11)
- Per-engineer overage limits with cost estimates (v1.1.7)
About Ito
Ito is an AI code review agent that builds and runs your app on every pull request, exercising the user flows your changes affect. It goes beyond static analysis by actually executing your code in a containerized, single-use sandbox, navigating like a real user to surface runtime bugs that code-reading tools miss. Aimed at engineering teams shipping AI-generated code at high velocity, Ito automates the manual regression testing bottleneck without requiring a single line of test script. For each PR, Ito reads the diff and description, generates a targeted test plan, and deploys a fresh copy of your app from source. It runs both frontend and backend logic, handles edge cases and adversarial scenarios, and posts a full report directly in the PR with video replay, logs, reproduction steps, and severity ratings. When you push a fix, Ito automatically re-runs to confirm resolution. A recent update (v1.1.6) lets Ito learn from your repository's fix history to focus testing on the most relevant areas. Ito is framework-agnostic, supporting React, Vue, Next.js, Rails, Django, and any web stack. It handles authenticated flows including multi-factor authentication, and offers a scriptless approach that adapts to UI changes, eliminating the test maintenance tax of tools like Playwright or Cypress. Integrates as a GitHub check and starts testing within roughly 60 minutes of install. Security is a focus: isolated test runs, end-to-end encryption, and it is pursuing SOC 2 Type II compliance. While it doesn't merge code, many teams use its runtime verification as a signal to enable automerge. Compared to static reviewers like CodeRabbit or Claude, Ito provides evidence-rich, execution-based findings—catching behavioral regressions that only appear when code runs. It's not a replacement for human strategic QA, but it automates the repetitive verification layer.
Behind the Verdict
Most code review tools read your diff and reason about it. Ito runs your code. That distinction matters more every quarter, because AI coding agents are pushing PR volume past what manual review can absorb. If your team reviews AI-generated code, you've seen the pattern: a static reviewer flags a style nit, misses the broken checkout flow, and the bug ships. Ito builds the app from source, clicks through the actual user journeys, and posts a video of exactly what broke. Where it shines is the scriptless, self-healing approach to E2E testing. Playwright and Cypress suites rot: rename a button, and half your selectors break. Ito adapts to UI changes because it generates test cases from your app's actual behavior, not from brittle locators. That's the real value prop for teams tired of test maintenance. But the trade-offs are real. Reviews take 30 minutes to 2 hours, so it's not for CI pipelines that need sub-minute feedback. It's GitHub-only right now—no GitLab or Bitbucket—and native mobile apps are still on the roadmap. And the pricing model has a gotcha: the Pro tier at $40/mo includes only 20 code reviews per seat, then it's $3 per additional review. A high-volume team could burn through that fast. The trial usage now correctly excludes paid periods (v1.1.15), and usage-limit emails hit at 80% and 100% (v1.1.11), so you won't get blindsided by overages. The company is SOC 2 Type II compliant, which covers the security concerns—isolated sandboxes, end-to-end encryption, zero data retention. For teams shipping AI-generated code, Ito automates the verification layer that would otherwise eat 1-2 hours per engineer per day. You still need humans for strategic QA and exploratory work, but Ito removes the repetitive clicking. If you're a small startup without a dedicated
Researching Ito? 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 actually fits — and what changes day-one when you adopt it.
On Monday, your dev teams open 15 PRs. You install Ito on your GitHub org, connect a repo, and by afternoon the first PR gets a full runtime report with video and severity ratings. You push a fix to a flagged bug, and Ito re-runs automatically to confirm.
Outcome: Merge confidence improves: you catch runtime bugs pre-merge, reduce regressions, and cut manual verification time by hours per week.
You add Ito to your repo, configure per-engineer overage limits (v1.1.7) to control costs, and set up usage-limit email notifications (v1.1.11). When a critical PR updates auth logic, Ito runs the MFA flows and posts a failure with reproduction steps.
Outcome: Your team fixes the bug before it hits production, and you have a reproducible audit trail in PR comments, enabling faster reviews and safer automerge.
You approve Ito's Open Source plan. Every community PR gets runtime analysis automatically, catching regressions without you writing test scripts. When a contributor submits a PR that breaks a core flow, Ito posts a video replay and severity-rating comment.
Outcome: You maintain quality without extra QA headcount, and contributors get immediate feedback, increasing contribution velocity and trust.
Use Cases
- Automatically test every pull request for runtime regressions before merge.
- Catch backend logic bugs that code review alone misses by executing real database writes and business logic.
- Verify frontend UI flows with video evidence, eliminating manual clicking through scenarios.
- Scale QA without hiring—replace the 3+ hours per week each developer spends manually verifying AI code.
- Provide reproducible bug reports with video, logs, and steps to reproduce directly in PR comments.
- Ensure open-source contributions don't break existing functionality without requiring test maintenance.
- Trigger a test run on a draft PR by commenting @itoqa to get early feedback.
Limitations
- Ito focuses on AI-powered automated QA for web applications and HTTP APIs on GitHub pull requests.
- It runs browser-based tests in a containerized environment per PR, with test duration that may be slower than sub-minute CI feedback.
- The Pro plan includes 20 code reviews per seat, with additional reviews at $3 each.
- Currently, it integrates with GitHub; no other VCS integrations are mentioned in the provided evidence.
as of 2026-08-11
Verification history
We have re-verified Ito 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 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
Engineering teams wanting to test Ito on their real PRs before committing—first 5 PRs free, no credit card required.
What this tier adds
Starting free tier: includes runtime analysis, video & screenshots on each run, but limited to 5 PRs total.
Open Source
$0/mo
Ideal for
Qualified non-commercial open-source projects (MIT/Apache) that need free runtime QA on every community PR.
What this tier adds
Free tier with unlimited public repos, runtime analysis on every PR, and dedicated long-term support—no per-review fee.
Pro
$40/mo
Ideal for
Startups and small teams shipping AI code that want unlimited repos with 20 reviews per seat/month and flexibility to add more.
What this tier adds
Adds 20 code reviews per seat, custom rules, team insights & analytics, and $3 per additional review versus free trial's 5-PR cap.
Enterprise
Custom
Ideal for
Teams of 25+ engineers requiring security/compliance (SSO, audit logs), higher limits, and dedicated support.
What this tier adds
Adds security/compliance features, technical enablement, custom invoicing/DPA, and higher usage limits over Pro.
Where the pricing makes sense
The company stage and team size where Ito's pricing actually pencils out — and where peers do it cheaper.
Ito's Pro at $40/mo per seat with 20 reviews is cheaper than hiring a QA engineer ($120K+/yr) and avoids Playwright maintenance. Compare to CodeRabbit's ~$18/mo starter (static only) and Mabl's enterprise pricing. For startups shipping lots of AI code, Ito's $40/mo is a budget-friendly QA layer; for high-volume teams, the $3/review overage may push you to Enterprise custom pricing.
Setup time & first value
How long it actually takes to get something useful out of Ito — broken out by persona, not the marketing-page minute.
For a GitHub admin: about 60 minutes from install to first PR tested—sign up, install the GitHub App, connect a repo, and open a PR. For a team member: activate a seat, and Ito runs on their PRs automatically. No test scripts to write, no suite to configure.
Switching to or from Ito
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Playwright/Cypress: Stop maintaining scripts; Ito auto-generates tests from your PR diff and adapts to UI changes—no selector fixes.
- →From Manual QA: Replace the 1–2 hrs/day per engineer of clicking through flows; Ito automates regression, humans keep strategic QA.
- ↗To Mabl: If you need cross-browser testing at scale, Mabl offers more extensive browser coverage, but you'll write/maintain test cases.
- ↗To CodeRabbit: If you prefer static diff analysis and lower cost, CodeRabbit doesn't run your app—only reviews code.
- ↗To In-house Playwright: If you need full control and sub-minute CI, build custom Playwright suites (but maintain selectors and flakiness).
Integrations
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Ito
Common stack mates teams adopt alongside Ito, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Ito vs Locus Robotics
Don't choose between them — they solve completely different problems. Locus Robotics is for warehouse operators needing to 2-3x fulfillment productivity via physical robots; Ito is for software teams wanting zero-maintenance pre-merge testing. Pick based on your operational domain.
Ito vs Truleo
Truleo and Ito serve entirely different domains: Truleo is for law enforcement agencies needing to surface leads from siloed data, while Ito is for software teams automating regression testing via real code execution. There is no overlap; choose based on whether you are a detective or a developer.
Ito vs Presto Voice
These tools serve entirely different needs. Presto Voice is a voice AI platform for QSR drive-thrus, focusing on order automation and upselling. Ito is an AI-powered QA agent for software teams, automatically testing PRs by running the app. Choose based on whether you run a fast-food chain or ship code.
Alternatives to Ito
View allFrequently Asked Questions
Categories
Best-of guides
Used Ito? Help shape our editorial sentiment research.


