Ito

congrats!

Running the app before reading the diff is the actual difference here, and it creates a question I have not seen a runtime reviewer answer well.What does Ito post on the PR when the container itself never came up? Build failed, seed data unavailable, external service refused the credential. If that lands as "no runtime issues found", then a broken environment and a clean PR are the same result, and it fails silently in the direction that looks fine.So: what does a run that could not run report as?

Grayson here, one of Ito's cofounders.I love that the hard part of Ito is often overlooked: generalizing the ability to run code is the difficult problem. Everyone assumes it's a "deciding what to test" problem (which is definitely hard too!). But the challenge of standing up an actual application is insanely hard. Get that wrong and the smartest agent in the world clicks around a broken login page. Internal teams at DoorDash or Ramp have spent quarters of engineering time trying to build this internally because they know it's important. Most teams cannot, and shouldn't have to.That is why runtime review didn't exist until now. Nobody wanted to build the unglamorous layer, and you cannot fake it by bolting a sandbox onto a static reviewer.That layer is where most of our engineering was spent prior to launch, and it's the reason the reviews surface verifiable bugs instead of suspicions. Just wait to see what else we do :)

It's a neat approach that is differentiated from and complimentary to the standard AI review tools. We use it and it has surfaced bugs other tools missed on multiple occasions. The team moves fast too and is very responsive to feedback. They are a pleasure to work with.

Hi, I'm Geoff, a software engineer on the Ito team. 👋The thing I love most about Ito: it actually runs the code. 🚀 Every PR I open comes back with a test plan that wasexecuted, not just read.⚡ Automates the manual testing I used to do by hand — click through the flow, check the edge cases, confirm nothing else broke. That's hours back every week.🐛 Catches bugs I would have missed. Real runtime failures that linters and static analysis structurally can't see,because they never execute anything.🤖 Makes agentic loops genuinely feasible. When an agent writes the code, something has to verify it actually worksIto is that step, so I can let the loop run longer and trust what comes out the other end.Getting to build this as an engineer who also uses it every day has been the most fun I've had on a product. 🎉Easy to try and see how Ito can help your team: app.ito.ai

The runtime approach to code review is really interesting. Instead of just analyzing what the code looks like, Ito actually checks how the application behaves in real scenarios and backs the findings with evidence. The combination of agent swarms and isolated environments makes this especially relevant as AI-generated code keeps increasing.

the "mocks data when it doesn't have access" line is the scary part to me, a mocked call that quietly diverges from the real service gives a false pass that looks more trustworthy than static analysis. do you flag which parts of the evidence pack came from a mock vs a live call?

Love the runtime angle. How do you handle PRs that touch external services — mock them in the ephemeral env, or spin up real instances?

Question: How do you compare with Greptiles Trex feature?

Can I run it on my local machine?

I like the ephemeral env per PR idea - less guessing from a diff

Hey Product Hunt. I'm Evan, cofounder of Ito.Coding agents produce more code than you can review. Existing code review tools only stare at the code, so you still have to review tons of code or build complex internal systems to verify it.Ito is a runtime code review tool. On every pull request:Creates test plan from code, PR description, ticket, your inputBuilds your app in a single-use isolated container with the ability to use credentials, seed data to reach the state that matters, and use external services just as an engineer would on their local machine. Mocks data/code when it doesn’t have access.Drives the app with a swarm of agents (click, navigate, API call, db verification)Catches runtime issues: concurrency, failure handling, data migration, authentication, etc.Posts results on PR with evidence: video, logs, screenshotsWe built Ito with a team of 8 MIT engineers, and spent many cycles to arbitrarily build any application. Ito gets better the more you use it:Responds to feedbackFaster runtimes every run as Ito learns how to navigate your application and builds tools to manipulate your environmentReviews focused on the areas you care about (sees what gets fixed vs ignored)Test instruction per org, per repo, or per authorFirst 100 reviews free, no card. $40/mo after that. Free forever for open source (already supporting >100k stars): app.ito.ai?phYou can also try out open source PRs without signing up here: https://www.ito.ai/review?ph