marlow

Build the pipeline that turns tickets into reviewed pull requests, merged under your policy.

Needs a tracker, CI and a repository on GitHub, GitLab or Bitbucket.

app/runsDemo workspace
The runs list: every ticket Marlow worked, its outcome and its pull request

Plan, write, test and review, with a person only where your policy puts one.

  1. 01

    Unattended

    Nobody at a keyboard

    Label a ticket in the tracker you already use. Marlow works it in a disposable sandbox and opens the pull request.

  2. 02

    Governed

    Your merge policy decides

    A second vendor's model reviews every diff, your own scanner runs on it, and each project says what may merge.

  3. 03

    Accounted

    Every call priced

    Each model call is recorded against its run, under a spend ceiling and a concurrency cap you set.

Models

Route through OpenRouter, or hold the keys yourself

Bring your own provider keys and the bill is in your name. The model that reviews a change never comes from the vendor that wrote it.

  • Anthropic
  • OpenAI
  • Google
  • xAI
  • OpenRouter
  • Amazon Bedrock
  • OpenAI-compatible endpoints
  • OpenAI-compatible endpoints
  • Amazon Bedrock
  • OpenRouter
  • xAI
  • Google
  • OpenAI
  • Anthropic

Connectors

Plugs into the tracker you already use

Tickets come in from your tracker, forge or chat. Pull requests go out to the repository. Self-host with Docker Compose or the Helm chart, or use the hosted service.

How it is wired
  • GitHub
  • GitLab
  • Bitbucket Cloud
  • Linear
  • Jira
  • Sentry
  • Slack
  • Microsoft Teams
  • Google Chat

One chat app per deployment: Slack, Microsoft Teams or Google Chat.

app/runs/02ea1e86Demo workspace
One run from ticket to pull request: each step, its model calls and its cost

A real run

One ticket, start to merge, with every step and every cost on the record.

cod3nest/marlow-demo · pull request 1 · merged

Who it is for

Built for teams with more backlog than reviewers

Roughly ten to two hundred engineers, with a queue of small, well-understood work nobody has time to start.

How agencies use Marlow
  • A tracker you actually use

    Linear, Jira or GitHub issues. Marlow starts from the ticket, not from a prompt.

  • CI already running

    The CI verdict is part of the merge decision, so there has to be one.

  • A habit of reviewing

    Marlow hands over a reviewed pull request. Someone still owns the merge.

  • Agencies and studios

    Per-run pricing makes a client's work cost a number, not a monthly guess.

  • Self-hosted teams

    One chart or one compose file, on infrastructure you control.

  • Not a fit

    Below about ten engineers, an attended tool in the editor serves you better.

Use cases

What it does while nobody is watching

Each of these runs start to finish without someone at a keyboard.

Changelog

What shipped lately

All changes
  • Week of 2026-09-28

    A run waiting for plan approval can now be approved or sent back from the console even when the planner produced no plan.

  • Week of 2026-09-28

    /marlow ticket and emoji-reaction tickets now work in a Slack workspace connected from the console.

  • Week of 2026-09-21

    A connected GitLab instance no longer shows an open connect form beneath it, which read as its edit form.

Start on Free

Assign it one boring ticket.

Connect a repository and hand Marlow something you have been putting off. Set the gate to “open a pull request and stop” — the worst case is a branch you close.

No card required · nothing to cancel · read the FAQ