# Pricing

---

Coverage on every PR, automatically
Ito catches regressions before merge by testing all of your PRs in a real browser before every release.
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 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.

---

### Free Trial

Individuals, Side Projects, Try before you buy

$0

- 1-click GitHub install
- 5 PRs free
- Video & screenshots on each run
- Same engine as paid
- Email Support

### Enterprise

For teams of 25 + Engineers

Custom

- Custom onboarding tuned to your setup
- Unlimited PR tests on all your repos
- Video & screenshots on each run
- Slack + priority support
- Dedicated forward-deployed engineer for complex configurations
- Smoke testing on core workflows before major releases
- Demo videos for your feature launches

### Open Source

For open-source projects

Free

- QA 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

---

## FAQs

Everything you need to know about billing and plans

**Q: Is Ito QA, or does it replace QA?**

A: Ito replaces the manual regression layer of QA. This is the part where someone clicks through flows on every PR to make sure nothing broke. Strategic QA, exploratory testing, and release planning still belong with humans.

**Q: What does "behavioral testing" mean exactly?**

A: We run your actual product in a real browser and exercise it the way a user would: log in, navigate, fill forms, submit, verify state. We're testing behavior end-to-end, not source code.

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

A: Typically 45 minutes to 2 hours. It's AI on top of AI doing real work: exploring flows, retrying when things are flaky, recording every step. We optimize for thoroughness, not speed.

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

A: Web apps and HTTP APIs today. 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, that's the point.

**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.

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

A: It posts a GitHub comment on the PR with a video clip of the failure, repro steps, and the affected flow. Your team triages it like any other review comment.

**Q: Does it integrate with our CI / GitHub checks?**

A: Yes. It runs as a GitHub check, doesn't block merges by default, configurable per repo.

---

## Get started today

Ito is free for your first 5 PRs.

Try Ito Free

Get your first results in less than 60 minutes