Veratex AI · the autonomous software maintainer

Your codebase,
maintained.

Veratex AI finds bugs, fixes GitHub issues, reviews pull requests, and tests changes in a sandbox. Run it fully on its own, or have it work on a separate branch and merge only what you want.

Start with GitHub → Book a demo

What it does,
step by step.

01
Use
tries your product like a user
02
Triage
reads every issue
03
Write
fixes it, with tests
04
Review
a second agent checks it
05
Test
tests it, then tries it live
06
Land
merges when tests pass
07
Incorporate
you move it to your branch
acme/api-gateway · exploring
using the product
Found a dead button on /checkout
19:02 open /checkout, add an item
19:03 apply coupon "  " · nothing happens
19:03 filed a bug with repro steps
It starts by using your product
Veratex runs your product in a sandbox and tries it the way a user would. Bugs and ideas become proposals for you to approve.
acme/api-gateway · triage
reading
#482 marked ready to fix
Clear scope, easy to reproduce, worth doing. Queued for a fix.
It reads every issue first
A quick check decides what is worth working on before any code is written.
agent · writing
fixing
Fix the token refresh race
Opened branch fix/482-auth. Rewrote the token path, changed 3 files, added 6 tests.
Every fix comes with tests
All work happens on a work branch, never directly on yours.
review
approved
Reviewing PR #508
✓No security problems
✓Tests cover the change
✓Matches how the codebase is built
A second agent reviews the code
A fresh reviewer checks correctness and security, then approves or asks for changes.
sandbox · fresh vm
testing
Tested, then tried for real
$ pnpm test · 312 passed
$ playwright test · 14 e2e passed
open /login · fix works in a real browser
It uses the fix, not just the test suite
The tests run in a clean sandbox, then Veratex opens the product and checks the change works in real use. Our servers record the results.
merge
merged
Merged PR #495
✓All tests passed
✓Diff under the size cap
✓Same repo, not a fork
Merges only when it is safe
On autopilot this lands on your branch. On a draft branch it lands on Veratex's own branch, and step 7 is yours.
acme/api-gateway · draft branch
2 ready
Tested changes, ready when you are
Add backoff to webhook retries
re-tested against your branch · 41 min ago
Fix: coupon accepts whitespace
unit + e2e passed · 2h ago
Merge into devDiscard
Your branch changes only when you click
Each change is re-tested against your latest code, then lands exactly as tested.
How teams use it

Two ways
to use it.

Maintain a repository, hands-off.

Give Veratex a repo and it keeps it healthy on its own: issues fixed, pull requests reviewed, every change tested and merged.

Build alongside your team.

On a repo your team actively develops, Veratex works on a separate branch: it suggests features, fixes bugs, and tests everything. You decide what gets carried over.

Works with your monitoring an alert becomes a tested fix
Get started

Start in
two minutes.

Connect a repository and Veratex gets to work today.

Start with GitHub → See how it works