Ito

A closer look at Ito

Ito is a runtime code review tool that builds an app on every pull request, runs the impacted user flows in a real browser, and attaches video, logs, and reproduction steps to anything that breaks, before merge.

Editorial guidance based on published documentation. The workflow below is a suggested starting point, not a measured product result.

When to choose Ito

• Engineering teams whose PR volume from coding agents has outpaced manual verification and who want runtime bugs caught before merge.
• Teams that want every PR tested in a real environment, with a video replay, logs, reproduction steps, and severity ratings on each failure.
• Teams that want a self-healing codebase, where Ito proposes a fix as a PR for the bugs it finds, and re-runs on a fix to confirm it is resolved.

When to choose something else

• Teams that need native mobile app testing, since the pricing FAQ states any tech stack for web apps and APIs, with native mobile on the roadmap.
• Pro-plan teams that need more than 50 code reviews per seat, since additional code reviews are billed at $1 per review beyond the included 50.
• Teams that expect Ito to merge code itself, since the FAQ states Ito does not merge code and provides a critical signal that leads into merging.

A practical starting workflow

1. Open a pull request, and let Ito read the diff and description and build a targeted test plan for the flows the change affects.
2. Let Ito build and run a real, single-use copy of the app from source, navigating it like a real user including edge cases and adversarial scenarios.
3. Review the complete test summary in the PR, fix failures using the video, lines, and reproduction steps, and let Ito re-run to confirm the fix.

Check before committing

• Plan amounts on the pricing page are shown in $ without a named currency, so no charge fact is recorded; the free offers are a first-20-reviews offer and a qualified non-commercial open-source offer, not a general $0 tier fact.
• The guessed FAQ path returns only a 3-character page, so FAQ answers below are drawn from the pricing page FAQ section, not a separate FAQ page.

Common questions

Compare approaches for this task

• AIOProductOS — Product teams that want to build what pays, since the platform ties each customer record to feedback, revenue, work and code.; Companies that need enterprise controls, since the pricing page highlights EU and US data residency, BYOK encryption, SAML/SSO on Pro and 150+ compliance controls.
• AISOAP — Clinicians who spend too long on documentation, since AISOAP records, transcribes and generates SOAP notes from the visit conversation.; Clinics that need team controls, since multi-person plans add team management, template creation and an organisation-wide BAA.