Show HN: Ito – Code reviews that run code

I'm Evan and I made Ito.ai

It's code review that actually runs your code. The result is that it finds more bugs with a smaller false positive rate. You get screenshots, videos, and run logs. I built Ito because manual verification sucks and I thought I could automate it. I've been a professional developer for 15 years and now more than ever, I'm just spending time making sure things work.

I looked into all of the other agentic testing tools that click around a url you give them and frankly, they sucked. They just didn't work. I figured to be able to actually testing things you need to run the full environment so you can seed data, bypass gates, mock external dependencies. They also can't get runtime evidence about changes that aren't frontend. Ito does.

Under the hood, Ito is creating a devcontainer for your application. All of your services are wired up and then a team of agents goes and tests your PR. We rolled out our own sandboxes and our own agentic coding loops.

I built Ito to be another useful signal in development. It shouldn't annoy you when it's not perfect and it saves you a bunch of time testing.

A few open source examples:

- n8n https://app.ito.ai/share/bb7d73aa-fd08-482d-9938-87938e2a232...

- lobehub https://app.ito.ai/share/1d76f15a-9998-4154-85b4-b177924cba8...

- excalidraw https://app.ito.ai/share/d1cb1475-fbe5-4c71-901b-409ba2aa6d6...

▲

debug_forever 5 hours ago | parent | next [-]

How does it decide what to test in a PR? And how does this code review tool connect with services that require configs? E.g. My checkout uses stripe, and for QA, we have a sandbox account connected.

	▲	evanmarshall 5 hours ago \| parent [-]
		It uses code diffs + descriptions + issues as the base test plan (acceptance criteria + regression). You can then interact with it to shape it more towards what you want.

▲

johndonavon 5 hours ago | parent | prev | next [-]

How much of a difference are you seeing between this and existing static code analysis tools?

	▲	evanmarshall 5 hours ago \| parent [-]
		Static code analysis is great but it misses a lot. Agents that read code make guesses about how code would execute, Ito makes a guess and then verifies it with runtime evidence.

▲

mbv_512 4 hours ago | parent | prev | next [-]

Does Ito support testing back-end only repos? Our repo layout is split up between back-end and front-end repos.

	▲	evanmarshall 4 hours ago \| parent [-]
		Yes, but the tests and evidence won't include screenshots, it'll be more curl requests and logs.

▲

castertroy 5 hours ago | parent | prev [-]

we're trying to build this ourselves with some qa skills. what's the benefit of buying?

	▲	evanmarshall 5 hours ago \| parent [-]
		Our first POC was slow, expensive, and bad quality. It takes a lot of effort to build the infrastructure, memory layers, QA code gen fixtures and more to get it working reasonably well.