FactorAI

Solutions

Fix bugs before they're filed

Find bugs in deployment events, open issues, and code, then get a draft pull request with the fix and a test that proves it.

Try the demoGet started

Find bugs nobody filed

Check deployments, open issues, and code for errors.

Reproduce confirmed bugs

Get exact steps and the root cause by file and line.

Prove the fix

Get a test that fails before the fix and passes after.

How it works

From error to tested fix

A sample run, start to finish. It finds a bug nobody filed, reproduces it, writes the fix and a test, and leaves a draft pull request for you.

FactoriesEngineering run

IdleIllustrative run
Reading

      Guardrails

      It never merges. Your team does.

      Every fix ends as a draft pull request for you to review, change, or close.

      Drafts only

      Every pull request opens as a draft against your default branch. It never merges, closes issues, or replies to customers.

      Text is data

      Text from issues, deployment events, and fetched pages is read as data, never as instructions.

      Linked in Linear

      Comments on the matching issue when one exists. Otherwise files a new labeled issue that links the pull request.

      Works with your engineering stack

      Uses the tools your team already runs

      Vercel

      Reads recent deployments and their events to collect errors and failures.

      GitHub

      Reads the code behind each error, checks the repository out to write the fix, and opens draft pull requests.

      Linear

      Reads open issues so a known bug gets a comment, and files a labeled issue for a bug nobody reported.

      Your tests

      Runs your tests in the checkout to show the result before and after the fix.

      Start from a template

      All templates
      • AI Support AgentReads deployment events, open issues and code to find bugs nobody filed yet. Each one comes back as a draft pull request with a test that fails before the fix and passes after, linked from Linear.
        See template
      • AI MaintainerSplits the cleanup backlog into small, independent draft pull requests, each with the check that proves it. Merging stays with you.
        See template
      • Documentation QA EngineerStart with Documentation URL + public repo. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
        See template

      Start on Hobby, move to Pro when you need more

      Hobby is free with monthly FTAI. Pro is for heavier use. Eligible accounts can start Pro with a 7-day free trial.

      Compare all plansContact sales

      Hobby

      $0/ month

      $5 in monthly FTAI

      Get started

      What's included:

      $1 daily login bonus

      Pro

      $20/ month

      $20 in monthly FTAI

      Get Pro

      Everything in Hobby, plus:

      Pay as you go

      Multi-member teams

      Free viewers

      Beta Feature Opt-in

      Engineering questions, answered

      What a run reads, what it changes, and what stays with your team.

      Have a question about your engineering workflow? Talk to us

      1
      Does it merge its own pull requests?
      No. Every pull request opens as a draft, and your team reviews and merges it. It never closes issues or replies to customers.
      2
      Where does it look for bugs?
      Recent Vercel deployments and their events, open issues for your Linear team, and the code in the repository you connect.
      3
      How do I know a fix works?
      Each pull request includes a test that fails before the fix and passes after it, with both results in the description.
      4
      What happens to bugs it cannot reproduce?
      It skips them and reports them as unconfirmed. It only opens pull requests for bugs it can reproduce and explain.
      5
      Will it file duplicate issues?
      No. When an open issue already covers the bug, it comments there with the pull request link instead of filing a new one.
      6
      Can text in an issue or a log tell it what to do?
      No. It treats text from issues, deployment events, and fetched pages as data, never as instructions.
      7
      Which tools do we need to connect?
      GitHub for the repository and pull requests, Linear for issues, and Vercel for deployments.
      8
      What does a run return?
      A table with each bug, where it was found, its root cause, the draft pull request, the Linear issue, and the test result.

      Review fixes, not bug reports

      Connect GitHub, Linear, and Vercel, and get tested draft pull requests for bugs nobody has filed yet.

      Start fixing bugsContact sales