# Pricing

## Full Coverage on Every PR

Ito catches regressions and runtime bugs before merge by testing all of your PRs in a real environment before release.

FOR Engineering teams

Get Started

no credit card required

Watch 2 min demo

### Pro

For startups and small teams

$40/mo

- Unlimited Repositories
- 50 Code Reviews included per seat
- $1 per additional Code Review
- Unlimited Read-Only users
- Create Custom Rules
- Team Insights & Analytics

### Enterprise

For teams of 25 + Engineers

Custom

- All Pro Plan Features
- Security and compliance
- Technical enablement and dedicated support
- Custom invoicing and payment terms
- Custom DPA and terms of service
- Higher limits across the product

### Open Source

Free for qualified non-commercial projects with MIT or Apache licenses

Free

- Runtime analysis on every Pull Request
- Catch regressions from community contributions
- Video & screenshots on each run
- Unlimited public repositories
- 1-click GitHub install
- Dedicated long-term support

What teams do today
Hire more QA engineers: $120K+/year per hire. Slow to scale. Bottleneck before your releases.
Write & maintain Playwright: Engineers spend >10% of their time writing and maintaining tests instead of shipping features for your customers.
Manual review on every PR: Eats 1–2 hrs/day per engineer. Dreaded by your engineers. Skipped before deadlines.
Ship and pray: On-call fires. Customer-reported bugs. Trust erodes. SLAs at risk.
Coverage on every PR
Autonomous scale: The equivalent of a dedicated QA hire for every dev. Scales instantly without adding to your payroll.
Zero maintenance testing: No selectors to manage or scripts to fix. Adapts to UI changes so your tests stay current automatically.
Instant behavioral feedback: Get PR results within 60 minutes of install. Automated video, logs, and screenshots posted inline.
Pre-merge certainty: Catch regressions before they ship. Validates every unique user role and flow in a real browser to protect your users.

## FAQs

Everything you need to know about billing and plans

**Q: How does Ito save my team time?**

A: Ito replaces the manual regression layer of QA. This is the part where someone, usually an engineer reviewing another engineer's PR or a test engineer, clicks through flows on every PR to make sure nothing broke. This is roughly 1-2hrs per day of manual work that Ito automates. 

Strategic QA, exploratory testing, and release planning still belong with humans.

**Q: Does Ito merge code? **

A: No, but many customers use Ito as a critical signal that leads into merging code. 

We provide a critical signal of runtime verification that is hard to replicate and ensures software factories don't introduce bugs or regressions.

**Q: What is "runtime analysis"?**

A: Ito runs your actual product in a real browser and exercises it the way a user would: log in, navigate, fill forms, submit, verify state. We're testing behavior end-to-end as the code runs, not just looking at source code.

**Q: What happens when Ito finds a bug?**

A: Ito posts a GitHub comment on the PR sharing the exact lines of code with the issue, the severity of the issue, evidence of why it's an issue with a description, reproduction steps, and a simple prompt to fix it. Your team triages it like any other review comment.

**Q: How long does a PR test take?**

A: Reviews typically take 30 minutes to 2 hours, depending on the complexity of the change and the codebase. It is thorough testing on top of your actual running application: exploring flows, retrying when things are flaky, recording every step. 

We optimize for thoroughness.

Many customers use Ito as an input to automerge and complete their software factories. 

**Q: What kinds of apps can it test?**

A: Any tech stack for web apps and APIs. Native mobile is on the roadmap.

**Q: How is it different from Playwright or Cypress that we'd write ourselves?**

A: You don't write or maintain anything. Ito figures out the flows from your product and your PR. No selectors that break when you rename a button. No suite that goes stale.

**Q: Do we have to write or maintain tests?**

A: No. You can tell Ito what you want it to test, but it's not necessary.

**Q: How long until it's running on our repo?**

A: About 60 minutes from install to first PR tested. Any admin on your GitHub organization can set up Ito to run on their PRs. Activate other team members to try it on more of your PRs.

## Get started today

Free for your first 20 reviews.

Try Ito Free

Get your first results in less than 60 minutes