# We built Revix AI because our own code couldn't ship fast enough.

> The story behind Revix AI. Two engineers built the AI code reviewer they wanted, so teams can ship fast without breaking their standards.

Canonical URL: https://www.revix.ai/about

We are two engineers. Code review became our bottleneck, so we built a tool to get past it.

## Meet the founders

### [Oscar Estudillo](https://www.oestum.com)

Frontend tech lead. Obsessed with building products and shipping fast since day zero.

### [Uri Gonfaus](https://urii.dev)

Backend & infrastructure tech lead. He turns fast-moving products into reliable systems.

## How Revix AI started

### Where we met

We met building side projects on the side of our day jobs. Eventually we landed on the same team, at the same company.

### Building at full speed

Together we shipped fast. With AI in the loop, even faster. Our ideas reached production almost as quickly as we could think them.

### Then we hit a wall

Our code piled up in review. We were writing far more than anyone could read, and the standards we cared about were never written down anywhere.

> Speed had created a new problem.

### Nothing on the market fit

Tools existed, but none protected speed from day one. Most needed manual setup and weekly upkeep. We weren't going to babysit the thing meant to help us.

### So we built Revix AI

We built the reviewer we wanted. It derives the rules from the repository itself, upholds the team's standards, and works from the first pull request.

### Too good to keep to ourselves

Revix AI cut our review time and raised our code quality beyond what we expected, so we turned it into a product.