Ito
Ito builds and runs your app on every pull request, then drives it with computer-use agents to catch runtime bugs before merge.
If your bottleneck is verifying that AI-written code actually behaves, Ito answers a question CodeRabbit and Cursor Bugbot structurally cannot: it runs the app instead of reading the diff. The trade-off is latency — 30 minutes to 2 hours per PR — plus a GitHub-only footprint and Pro pricing that bills $40/mo per seat with 50 code reviews included and $1 for each additional review, so high-volume teams should model seats before committing. Start on the free tier (first 20 reviews, no credit card) or the open-source plan if you qualify under MIT or Apache licensing, then decide whether the runtime signal is worth the wait in your merge queue.
Verified 12d ago · liveness 72/100 · cite: rightaichoice.com/tools/ito
- Engineering teams merging high volumes of AI-generated code who need runtime verification before merge
- Startups scaling regression testing without hiring a QA engineer per team
- Teams paying the maintenance tax on flaky Playwright or Cypress suites
- Organizations with heavy PR volume that want a runtime signal feeding automerge
- Teams on GitLab or Bitbucket — the integration is GitHub-only
- Products needing native mobile or desktop app testing — native mobile is still on the roadmap
- CI pipelines demanding sub-minute feedback — reviews typically take 30 minutes to 2 hours
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 develop on GitLab or Bitbucket, need native mobile app coverage today, or expect CI feedback in under a minute — reviews typically take 30 minutes to 2 hours.
Pro includes 50 code reviews per seat; every review beyond that bills at $1, which compounds quickly on a repo with heavy PR traffic.
Pro at $40/mo per seat suits startups and small teams; at 50 included reviews plus $1 each thereafter it undercuts hiring a QA engineer at $120K+/year but costs more than static reviewers like CodeRabbit if you only want diff comments. Enterprise is custom for teams of 25+ engineers. Qualified MIT/Apache open-source projects pay nothing.
In short
Ito — Ito builds and runs your app on every pull request, then drives it with computer-use agents to catch runtime bugs before merge. Best for Engineering teams merging high volumes of AI-generated code who need runtime verification before merge, Startups scaling regression testing without hiring a QA engineer per team, Teams paying the maintenance tax on flaky Playwright or Cypress suites. Free to start; paid plans from $40/user/mo.
What's new in Ito
Checked 3 days agoAcross the latest 10 updates: 7 changelog entries and 3 community discussions.
The Electrification of Factories: What Software Teams Can Learn From the Transition
Ito engineering blog argues factory electrification only paid off after workflows were redesigned, and AI software teams need the same shift in review and verification.
Bug Catch of the Week: How a Failed Database Swap Could Delete Your Only Copy
Ito's Bug Catch series documents a DoltLite replacement flow that could delete the old database before the new copy was safe, found via runtime testing.
How to Build Quality Into Your Software Factory
Ito blog recommends layered testing — fast tests first, deeper validation later — to keep software factories shipping without bug regressions.
Ito v1.2.17: shared PR link previews, automation settings page, housekeeping-file skip
v1.2.17 adds PR link previews with privacy gating, a dedicated automation settings page for admins, and skips reviews for housekeeping-file-only PRs.
Ito v1.2.16 refreshes account and review email design
v1.2.16 ships a card-based redesign of Ito's account and review notification emails.
Ito v1.2.15 speeds up test runs, merges demo video into PR Overview
v1.2.15 cuts time to start and complete test runs, and moves demo videos into a combined PR Overview tab with chapters and description.
Ito v1.2.11 auto-seats new orgs, reviews bot PRs by default, links PR demo videos
v1.2.11 grants seats automatically on install, reviews bot-authored PRs by default, and links available demo videos from the PR summary comment.
Ito v1.2.10 shows all open PRs during onboarding, improves test-run reliability
v1.2.10 lists open pull requests across accessible repos during onboarding, grouped by repository, and improves repository prep reliability.
Ito v1.2.9 fixes trial allowance miscounting and large-repo clone failures
v1.2.9 fixes non-review runs consuming trial allowance and blocks, and prevents clone failures when testing very large repositories.
Ito v1.2.8 adds PR demo videos, GitHub-style status icons, trial count display
v1.2.8 generates screen recordings with clickable chapters for PR changes, adopts GitHub status icons in PR lists, and shows free review counts at sign-up.
What people actually say about Ito — is it worth it?
We scanned public community sources for Ito on Jul 27, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Our own analysis of that scan says the posts were off-subject. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
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: October 2026
How we score →Key Features
- Builds and runs your app from source in a single-use containerized sandbox on every PR
- Generates a test plan for the specific PR commit from the diff and description
- Executes user flows with computer-use agents and deep browser inference
- Runs real backend logic to surface authorization, concurrency, and data migration bugs
- Posts video replay, screenshots, logs, severity ratings, and reproduction steps on failures
- Automatically re-runs after a fix until the PR passes
- Self Healing Codebase proposes a fix as a PR for bugs Ito finds
- Creates PR demo videos walking through each change (v1.2.8)
- Combined PR Overview page merging recording, chapters, and description (v1.2.15)
- Automatically reviews bot-authored PRs by default (v1.2.11)
- Auto-assigns seats to org members (v1.2.11)
- Explains skipped reviews caused by trial, seat, or billing limits (v1.2.5)
- Accepts plain-English test instructions to prioritize or skip scenarios
- Supports authenticated flows including multi-factor authentication
- Framework-agnostic across React, Vue, Next.js, Rails, Django, and any web stack or API
About Ito
Ito is an execution-based AI code review agent for web apps and APIs. Rather than reading your diff and posting an opinion, Ito deploys a single-use containerized copy of your application from source, then navigates it like a real user with computer-use agents and deep browser inference — every click and form submit runs your real backend code. It authenticates through the Ito GitHub App and monitors your repositories for new and updated pull requests. When a PR opens, Ito reads the diff and the PR description, maps the change to the user flows most at risk, and builds a test plan for that specific commit; you can add plain-English test instructions to prioritize scenarios. Findings come back as a PR comment with a video replay, screenshots, logs, the exact lines responsible, severity ratings, and reproduction steps, and pushing a fix triggers an automatic re-run until it passes. The Self Healing Codebase will additionally propose the fix itself as a PR. Coverage is framework-agnostic across React, Vue, Next.js, Rails, Django and any web stack or API, and Ito handles authenticated flows including multi-factor authentication. Reviews typically take 30 minutes to 2 hours per PR. It is aimed at teams whose PR volume — especially code written by coding agents — has outrun what anyone can verify by hand.
Behind the Verdict
The pitch behind Ito is a diagnosis most engineering leaders will recognize: coding agents now produce more diffs than any human can meaningfully verify, and the static reviewers that grew up around that problem can only assert. Ito's differentiation is structural rather than cosmetic — it provisions a real, single-use copy of your app from source for each PR and exercises it in a browser, so backend logic, authorization paths, concurrency behavior and data migrations are tested as they actually run, not as they read. That is why its customer quotes keep circling the same point: bugs with no visible trace in the diff. The workflow around the test run is unusually complete for a tool this young. Test plans are generated per commit from the diff and PR description, plain-English instructions let you steer priorities, and failures arrive with video replay, logs, severity ratings and reproduction steps rather than a paragraph of speculation. Fix, push, and it re-runs automatically. The Self Healing Codebase goes one step further and opens a PR with the proposed fix. Recent releases have filled in the operational edges: demo videos for each PR (v1.2.8), bot-authored PRs reviewed by default and org members auto-seated (v1.2.11), a combined Overview page and faster test runs (v1.2.15), and explicit explanations when a review is skipped for trial, seat or billing limits (v1.2.5). Where Ito does not fit is equally clear. It is GitHub-only, so GitLab and Bitbucket shops are out. Native mobile is on the roadmap, not in the product. The 30-minute-to-2-hour review window rules it out of pipelines that expect sub-minute feedback, and it is honest about its own scope: strategic QA, exploratory testing and release planning stay with humans. Cost is the other real constraint — Pro is $40/mo per seat with 50 reviews included and $1 per extra review, so a team running hundreds of PRs a month is buying overage, not a flat subscription, and Enterprise with security and compliance is for teams of 25+ engineers on custom terms. The free open-source plan is a genuine on-ramp for MIT and Apache projects. Buy it if your merge queue is the bottleneck and you can absorb the latency; skip it if you need instant CI feedback or you live outside GitHub.
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.
A coding agent opens five PRs overnight. Ito provisions a fresh containerized copy of the app for each, reads the diff, maps the change to at-risk flows, and drives them in a browser against real backend logic including authenticated and MFA paths.
Outcome: Two PRs come back with failures — a broken authorization path and a data migration issue with no trace in the diff — each reported with video replay, severity rating, exact lines, and reproduction steps. The clean three merge the same day.
Instead of walking flows by hand on every PR, the QA lead adds plain-English test instructions to prioritize the checkout and billing scenarios, then lets Ito run them and re-run automatically after each fix.
Outcome: The 1–2 hours a day previously spent on repetitive verification shift to exploratory and release-planning work, and every failure arrives as a reproducible report rather than a description.
A maintainer of an MIT-licensed project installs the Ito GitHub App on the public repository and lets it analyze incoming pull requests, including ones authored by bots.
Outcome: Community contributions get runtime analysis with video and screenshots on each run at no cost, so regressions are caught before they land without the maintainer writing or maintaining a test suite.
Use Cases
- Run runtime tests on every pull request before merge, with no test scripts to write or maintain.
- Catch backend logic bugs — authorization, concurrency, data migration — that a diff review cannot see.
- Verify UI flows with video evidence instead of clicking through scenarios by hand.
- Cut the 1–2 hours a day engineers spend manually regression-checking other people's PRs.
- Give coding agents a pre-merge verification signal strong enough to feed automerge.
- Hand reviewers reproducible bug reports — video, logs, exact lines — inside the PR comment.
- Keep open-source contributions from breaking existing functionality without maintaining a suite.
- Comment @itoqa on a draft PR to get early feedback before the change is finished.
Models Under the Hood
as of 2026-10-08
Limitations
- Ito provisions a fresh containerized copy of your app from source for each eligible GitHub pull request and runs browser-based user flows with an AI agent, posting video, screenshots, logs, and reproduction steps as a PR comment.
- It integrates through the Ito GitHub App, with GitHub being the only VCS integration documented.
- Pro is $40/mo per seat including 50 code reviews, with $1 per additional review; Enterprise is custom-priced for teams of 25+ engineers, and a free tier exists for qualified non-commercial projects with MIT or Apache licenses.
- Test execution happens per PR in a single-use sandbox, so coverage depends on the change and falls back to the PR diff/description for test-plan selection.
as of 2026-09-25
Verification history
We have re-verified Ito 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 tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Open Source
$0/mo
Ideal for
Maintainers of qualified non-commercial projects under MIT or Apache licenses who want PR runtime analysis without a budget.
What this tier adds
Free entry point: runtime analysis on every pull request, video and screenshots per run, unlimited public repositories, 1-click GitHub install, and dedicated long-term support.
Pro
$40/mo per seat
Ideal for
Startups and small teams running regular PR volume who need runtime verification plus custom rules and team analytics.
What this tier adds
Adds unlimited repositories, 50 code reviews included per seat with $1 per additional review, unlimited read-only users, custom rules, and team insights and analytics for $40/mo per seat.
Enterprise
Custom
Ideal for
Engineering organizations of 25+ engineers in financial services, healthcare, or defense that need security review and custom contracting.
What this tier adds
Adds security and compliance controls, technical enablement and dedicated support, custom invoicing and payment terms, custom DPA and terms of service, and higher limits across the product on custom pricing.
Where the pricing makes sense
The company stage and team size where Ito's pricing actually pencils out — and where peers do it cheaper.
Pro at $40/mo per seat suits startups and small teams; at 50 included reviews plus $1 each thereafter it undercuts hiring a QA engineer at $120K+/year but costs more than static reviewers like CodeRabbit if you only want diff comments. Enterprise is custom for teams of 25+ engineers. Qualified MIT/Apache open-source projects pay nothing.
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.
From install to first tested PR is roughly 60 minutes: sign up at app.ito.ai, install the Ito GitHub App on your org or personal account, connect a repository, then open or update a PR. Any GitHub org admin can set it up; teammates are activated onto seats afterward. Runs themselves take 30 minutes to 2 hours each.
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 or Cypress: retain existing suites while Ito covers flows without selectors or maintenance, then retire the flaky specs Ito replaces.
- →From manual PR regression clicking: install the GitHub App, connect the repo, and let Ito own the repetitive verification layer.
- →From a static AI reviewer like CodeRabbit or Cursor Bugbot: keep the diff comments and add Ito as the runtime signal that executes the app.
- ↗To a static reviewer if your priority is sub-minute diff comments rather than execution proof — expect to lose runtime evidence like video and backend logic coverage.
- ↗To a hand-written Playwright or Cypress suite if you need full control over selectors and assertions, accepting the ongoing maintenance cost.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Ito”, and we withheld 6: 6 could not be judged, because “Ito” 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.
Official links
Tools that pair well with Ito
Common stack mates teams adopt alongside Ito, with the specific reason each pairing earns its keep.
Ito AI
Runtime code review that builds and runs your app on every pull request to catch behavioral bugs static reviewers miss.
Human Behavior
AI session replay that watches every session, triages the bugs it finds, and opens pull requests to fix them.
TestDriver AI
TestDriver runs AI UI testing on every GitHub pull request — black-box E2E tests that self-heal.
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 all
Ito AI
Runtime code review that builds and runs your app on every pull request to catch behavioral bugs static reviewers miss.
Human Behavior
AI session replay that watches every session, triages the bugs it finds, and opens pull requests to fix them.
TestDriver AI
TestDriver runs AI UI testing on every GitHub pull request — black-box E2E tests that self-heal.
Frequently Asked Questions
Categories
Used Ito? Help shape our editorial sentiment research.