forge Request early access

Your engineers review AI code all day.

Bring your spec and repo. forge hands back a merge-ready pull request, with tests and a record of every check it ran. Your team reviews the outcome, not every line.

Send one backlog item How a run works

A working prototype: forge has merged 227 changes while building itself. Your first pull request is free.

Example run Add CSV export to the reports page
  1. Ticket received"Add CSV export to the reports page"0:00
  2. You approved the planWhat will change, and how it will be proven0:21
  3. Pull request ready9 tests passing, record of every check attached0:56
  4. You merge it, or send it back0:57
Two decisions are yours. Everything in between is forge.

You decide twice. forge does the rest.

Nothing gets built until you approve the plan, and nothing merges until you approve the pull request.

  1. Send a spec and your repo

    A ticket, a paragraph, or a link to an issue. GitHub or GitLab.

  2. Approve the plan

    forge proposes the tasks and the tests that will prove them. Change it or say yes.

  3. Review the pull request

    The change arrives as one pull request, with tests and the record of what was checked. Merge it or send it back with a comment.

The agent that writes the code never grades it. Tests, reviews and security checks each run separately, so a passing pull request means something.

Works on the code you already have.

Web apps, backends and Swift packages today. Other stacks on request.

PythonTypeScriptJavaScriptReactNodeSwift packages
iOS app core, Swift

Sign in, speeches, recordings and evaluations for a speech practice app

Outcomes agreed
22 of 22 met
Tests added
72
Status
Merged
Ask for a walkthrough
Storybook, open source, TypeScript and React

Browser tests that keep empty-string args in Storybook's "Open in isolation mode" link

Outcomes agreed
4 of 4 met
Tests added
3
Status
In review upstream
Read the pull request

The speech practice app is private, so I walk you through that pull request on a call: what went in, what came back, and the record of what was checked. The Storybook one is public, so you can read it yourself.

Who it's for, and your code.

A good fit

  • Founders and small teams with more backlog than engineers.
  • Agencies shipping across many client codebases.
  • Teams that already review AI-written code and want fewer, better pull requests to review.
  • Enterprise platform teams with a long tail of upgrades, dependency fixes and security patches. Start with one repository.

Not yet a fit

  • Companies that need a full vendor security review before a first trial.
  • Work with no spec and no way to test it.

What happens to your code

  • Each run happens in an isolated workspace built from your repo's lockfile.
  • forge opens pull requests. It never merges or pushes to your main branch.
  • Start on a fork or a non-critical repo if you prefer.
  • We agree what is kept after a run before your first one starts.

Taking five founding teams.

I work with each team directly and watch every run myself.

  • First pull requestFree
  • After thatA founding rate, set together
  • If you don't merge itYou don't pay

Book 30 minutes

Bring one backlog item and a link to your repo. We pick the first pull request together, and you get it free.

Pick a time