Ito AI
Runtime code review that builds and runs your app on every pull request to catch behavioral bugs static reviewers miss.
Most AI review tools hand you a confident comment and leave the verification to you. Ito builds and runs the app, then attaches the video, logs and exact lines, which is a materially different product from CodeRabbit, Greptile, Qodo or Cursor Bugbot. The honest catch is reach: GitHub only, web apps and APIs only, native mobile still on the roadmap, and runs take 30 minutes to 2 hours, which is slow if you need a verdict right now. If GitHub plus web is your stack, $40/mo per seat with 50 reviews included and $1 per additional review is cheap next to a QA hire or a maintained Playwright suite.
Verified 4d ago · liveness 73/100 · cite: rightaichoice.com/tools/ito-ai
- Engineering teams merging AI-written code who need runtime verification before merge
- Startups and mid-size teams shipping multiple PRs a day on GitHub
- Web app teams that want scriptless end-to-end testing without maintaining a suite
- Teams using automerge that need a hard runtime signal to merge safely
- Teams needing native mobile app testing — web apps and APIs only, mobile is roadmap
- Organizations standardized on GitLab or Bitbucket — GitHub is the supported platform
- Teams that want to hand-write and maintain their own E2E test scripts
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 your repos live on GitLab or Bitbucket, you need native mobile app testing, or you require a sub-minute review verdict rather than a 30-minute to 2-hour runtime run.
Each code review past the 50 included per seat costs $1, so an agent-heavy repo pushing hundreds of PRs a month can add a meaningful overage line on top of the $40/mo per seat.
At $40/mo per seat with 50 reviews included and $1 per additional review, Ito sits well under a $120K+/year QA hire and under a maintained Playwright suite, but above flat-rate static reviewers like CodeRabbit for small teams. It fits startups and mid-size GitHub teams shipping multiple PRs a day; teams of 25+ engineers move to custom Enterprise pricing for SSO, audit logs and higher limits.
In short
Ito AI — Runtime code review that builds and runs your app on every pull request to catch behavioral bugs static reviewers miss. Best for Engineering teams merging AI-written code who need runtime verification before merge, Startups and mid-size teams shipping multiple PRs a day on GitHub, Web app teams that want scriptless end-to-end testing without maintaining a suite. Free to start; paid plans from $40/user/mo.
What's new in Ito AI
Checked 5 days agoAcross the latest 10 updates: 6 changelog entries, 3 community discussions and 1 news mention.
The Electrification of Factories: What Software Teams Can Learn From the Transition
Ito blog argues AI software teams need the same workflow, review and verification redesign factory electrification required.
Bug Catch of the Week: How a Failed Database Swap Could Delete Your Only Copy
Ito case study: DoltLite's replacement flow could delete the old database before the new copy was safe; runtime testing caught it pre-release.
How to Build Quality Into Your Software Factory
Ito engineering post on layered testing — fast tests first, then deeper validation — to cut bugs in AI-speed release cycles.
Ito v1.2.17: Shared PR link previews, automation settings page
v1.2.17 adds PR link previews with private-page protection, a dedicated automation controls settings page, and skips reviews on housekeeping-only PRs.
Ito v1.2.16: Refreshed account and review email design
v1.2.16 refreshes Ito's account and review emails with a card-based layout.
The AI Model Plateau: Why Your Infrastructure Matters More Than the Next Release
Ito blog argues model routing and evaluation, not the next LLM release, now decide production results.
Ito v1.2.15: Faster test runs, PR overview tab
v1.2.15 speeds test environment prep and recovery, and opens demo-video PRs on a combined Overview with recording chapters and description.
Ito v1.2.11: Auto seats on install, PR demo video links
v1.2.11 grants org members seats automatically on install, reviews bot-authored PRs by default, and links demo recordings from PR summary comments.
Ito v1.2.10: Onboarding lists open PRs by repository
v1.2.10 shows open pull requests across accessible repositories, grouped by repo, to pick the first review target, plus more reliable test-run prep.
Ito v1.2.9: Trial allowance and large-repo clone fixes
v1.2.9 stops some non-review runs from consuming trial allowance and fixes clone failures on very large repositories.
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.
35 mentions across 3 sources (Hacker News, YouTube, Lemmy) · researched Aug 27, 2026.
Average across the 3 sources that answered — each source counts once, not each post.
- +Actually runs the app, catching runtime bugs static tools miss.
- +Video replays and screenshots make bugs easy to reproduce.
- +Zero-config setup—just connect GitHub and it works.
- +Auto re-runs after fixes to confirm resolution.
- +Supports authenticated flows, including MFA, which is rare.
- −Community feedback is limited to marketing-style YouTube comments.
- −No independent, detailed user reviews on Reddit or GitHub yet.
- −Per-review pricing can add up for active teams.
- −May not handle complex, stateful backends without flaky results.
- −No public uptime or CI latency data available.
- • Per-review overage fees at $3 each can quickly exceed expectations for busy teams
- • Enterprise pricing may require annual contract and minimum seat counts
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: October 2026
How we score →Key Features
- Runtime code analysis that builds and runs your app on every PR
- Computer-use agents navigate your app like a real user
- Deep browser inference catches behavioral regressions
- Containerized single-use sandbox per pull request
- Scriptless end-to-end validation with no test scripts to maintain
- Targeted test plans generated from the PR diff and description
- Plain-English test instructions to prioritize or skip scenarios
- Video replay, screenshots, logs and reproduction steps per failure
- Severity ratings and exact lines responsible on every finding
- Automatic re-run on fix to confirm the bug is resolved
- Self Healing Codebase proposes a fix as its own PR
- Agent Sandboxes give coding agents a live managed copy of your app
- Automatic smoke testing maps each change to at-risk journeys
- Authenticated flow testing including multi-factor authentication
- Framework agnostic: React, Vue, Next.js, Rails, Django and more
About Ito AI
Ito AI is a runtime code review tool for web app teams on GitHub. Instead of only reasoning about the diff, Ito builds a single-use copy of your app from source on every pull request, deploys it in an isolated containerized sandbox, and drives it with computer-use agents and deep browser inference to surface the behavioral regressions that only appear when code actually executes: service authorization, concurrency, failure handling, data migration, and authentication issues that a diff never shows. Test plans are generated from the PR diff and description, so you write no test cases and maintain no suite. Every failure lands inline on the PR with a video replay, screenshots, logs, reproduction steps, a severity rating, the exact lines responsible, and a plain-English prompt to fix it; push a fix and Ito re-runs automatically to confirm resolution. Automatic smoke testing maps each change to at-risk journeys, and the vendor also lists a Self Healing Codebase that proposes a fix as its own PR plus Agent Sandboxes that hand coding agents a live managed copy of your app to build and test against. It is framework agnostic for web apps and APIs — React, Vue, Next.js, Rails, Django, any web stack — and handles authenticated flows including multi-factor authentication via test environment credentials. Setup runs on any GitHub org admin account with no scripts: the vendor's own benchmark is about 60 minutes from install to first tested PR, and reviews typically take 30 minutes to 2 hours depending on change complexity. Ito is SOC 2 Type II compliant, uses end-to-end encryption with zero data retention, and runs each test in an isolated sandbox. Pricing is freemium: Pro is $40/mo per seat with unlimited repositories and 50 code reviews included per seat, then $1 per additional review, while Enterprise is custom for teams of 25+ engineers with SSO, audit logs and dedicated support. The first 20 reviews are free, and qualified MIT or Apache open-source projects get it at no cost. Closest alternatives are static AI reviewers like CodeRabbit, Greptile, Qodo, Mabl and Cursor Bugbot — those read code; Ito runs it.
Behind the Verdict
Ito's bet is simple and defensible: a diff is an assertion, and only execution tells you whether the change behaves. Every PR gets a single-use containerized copy of the app built from source, computer-use agents navigate it like a real user, and every action runs your real backend code — which is why the vendor's examples include failures with no trace in the diff at all, like DoltLite's replacement flow deleting the old database before the new copy was safe. Findings are unusually complete for this category: video replay, logs, severity, exact lines, reproduction steps, a plain-English fix prompt, plus automatic re-run on fix. The scripting burden is genuinely zero — test plans come from the diff and PR description, and you can add plain-English test instructions to prioritize or skip scenarios, which is what most teams actually want at 20 PRs a day. The trade-offs are structural, not cosmetic. It is GitHub-only today, so GitLab and Bitbucket shops are out. It tests web apps and APIs; native mobile is roadmap. Runs take 30 minutes to 2 hours, so it is a gate for automerge and software-factory workflows rather than a sub-minute lint. It is runtime behavioral analysis, not architecture or security static analysis — if you want a dependency-CVE scan or a design critique, buy something else alongside it. And the metered model matters: 50 reviews per seat is generous for a small team, but an agent-heavy repo pushing hundreds of PRs a month will see $1 overage reviews add up quickly, so budget for that rather than being surprised. Where it fits best is teams already merging AI-written code who need a hard runtime signal before merge, teams using automerge that want a non-human gate, and engineering managers trying to reclaim the 1–2 hours per day per engineer currently spent manually clicking through PRs. Teams that want to hand-write and maintain their own Playwright or Cypress suites, or that need a verdict in minutes, should look elsewhere.
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.
Installs the Ito GitHub App on the org, connects the main repo, and lets Ito generate a test plan from the diff and PR description on the next PR — no selectors or scripts to write.
Outcome: The PR comes back with a video replay, logs and severity-rated findings on the exact lines, replacing the 1-2 hours a day previously spent manually clicking through flows before merge.
Uses Ito as the runtime gate on bot-authored PRs — which are reviewed by default (v1.2.11) — and relies on automatic re-run on fix to confirm a pushed change actually resolves the finding.
Outcome: Agents automerge without a human review bottleneck, with a hard runtime signal that the change behaves rather than a comment asserting it does.
Applies the free qualified MIT or Apache plan, which gives unlimited public repositories and runtime analysis on every pull request with video and screenshots per run.
Outcome: Community PRs get automated QA evidence before merge, so maintainer time goes to design and scope rather than reproducing contributor bugs by hand.
Use Cases
- Catch regressions before merging by automatically testing every PR in a real browser.
- Replace manual PR verification of AI-generated code with automated runtime checks.
- Validate service authorization, concurrency 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 connects to GitHub and tests web applications and APIs by building and running them in containers on every pull request.
- Native mobile is on the roadmap, not supported today, and GitLab or Bitbucket are not supported platforms.
- Reviews typically take 30 minutes to 2 hours depending on change complexity, which can delay urgent merges since the tool optimizes for thoroughness over speed.
- The Pro plan includes 50 code reviews per seat at $40/mo, with each additional review billed at $1, so high-volume teams that push many agent-authored PRs can exceed the included quota and incur overage charges.
- It is runtime behavioral analysis rather than architecture or security-focused static analysis, so it will not replace a dependency scanner or a design review.
- If you need a verdict in minutes, or you want to hand-write and maintain your own E2E suite, Ito is the wrong shape.
as of 2026-10-04
Verification history
We have re-verified Ito AI 9 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
Showing the 6 most recent of 9 verification passes.
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/mo
Ideal for
A single engineer or small team that wants to see Ito run on their own PRs before committing budget.
What this tier adds
Starting tier: free for the first 20 code reviews with no credit card and a 1-click GitHub install.
Open Source
$0/mo
Ideal for
Maintainers of non-commercial projects under an MIT or Apache license with active community contributions.
What this tier adds
Runtime analysis and unlimited public repositories at $0/mo, adding dedicated long-term support over the trial.
Pro
$40/mo per seat
Ideal for
Startups and small teams shipping multiple PRs a day on GitHub with no dedicated QA function.
What this tier adds
Adds unlimited repositories, 50 code reviews included per seat, custom rules and team insights, with extra reviews at $1 each.
Enterprise
Custom
Ideal for
Engineering organizations of 25+ engineers with security review, procurement and compliance requirements.
What this tier adds
Adds SSO, audit logs, technical enablement, dedicated support, custom invoicing, custom DPA and higher limits across the product.
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.
At $40/mo per seat with 50 reviews included and $1 per additional review, Ito sits well under a $120K+/year QA hire and under a maintained Playwright suite, but above flat-rate static reviewers like CodeRabbit for small teams. It fits startups and mid-size GitHub teams shipping multiple PRs a day; teams of 25+ engineers move to custom Enterprise pricing for SSO, audit logs and higher limits.
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.
Any GitHub org admin can install Ito with no scripts: about 60 minutes from install to the first PR tested, and the vendor quotes first results in under 60 minutes. A solo engineer is typically reviewing runtime findings on the very next PR. Larger teams can grant seats automatically on install (v1.2.11) and start additional members on more PRs without extra configuration.
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 PR review: install the GitHub App, connect the repo, and let Ito take over the runtime verification layer while humans keep strategic QA and release planning.
- →From Playwright: stop maintaining selectors and suites and let Ito derive flows from your product and the PR, adding plain-English test instructions for the scenarios you care about.
- →From Cypress: the same scriptless path applies, with no selector upkeep when UI elements are renamed.
- →From a static AI reviewer like CodeRabbit, Greptile or Cursor Bugbot: run Ito alongside for a runtime signal rather than replacing your diff-level comments.
- ↗To Playwright: if you need scripted control over exact assertions on your own test infrastructure, expect to rebuild the flows Ito was discovering for you.
- ↗To a static AI reviewer such as CodeRabbit or Greptile: cheaper per seat, but you trade runtime evidence for diff-level comments and lose execution-based detection.
- ↗To a managed E2E platform like Mabl: more enterprise test-management surface, more configuration and more ongoing maintenance.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Ito AI”, and we withheld 6: 6 could not be judged, because “Ito AI” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Ito AI.
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.
Ito
Ito builds and runs your app on every pull request, then drives it with computer-use agents to catch runtime bugs before merge.
GitHub Copilot
GitHub Copilot is an AI coding agent that completes code, reviews pull requests, and runs Copilot, Claude, and Codex agents inside GitHub
CodiumAI
Agentic AI code review plus a governance layer that enforces your team's coding rules on every pull request.
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
Ito
Ito builds and runs your app on every pull request, then drives it with computer-use agents to catch runtime bugs before merge.
GitHub Copilot
GitHub Copilot is an AI coding agent that completes code, reviews pull requests, and runs Copilot, Claude, and Codex agents inside GitHub
Frequently Asked Questions
Used Ito AI? Help shape our editorial sentiment research.