I'm the developer behind Octopus Review, an AI code review tool that runs on pull requests. We just flipped a switch: every public, OSI-licensed repository gets unlimited reviews. No credit card, no monthly quota, no "free tier with limits."

I want to explain why, because the reasoning is more interesting than the announcement.

The Bill My Laptop Doesn't Send Me

Open the package.json of any project I've shipped in the last decade. React, TypeScript, Prisma, Next.js, Tailwind, Postgres, Redis, Nginx. Every single one is open source. Every single one was built by someone who didn't ask me for money.

The bill never arrives, but the debt is real.

And the people producing all of that are, by and large, exhausted. If you've ever maintained a moderately popular open source project, you know the pattern: a drive-by PR shows up on a Saturday morning, the contributor means well, the diff is 400 lines, half of it is unrelated formatting, the tests don't run on their machine, and they want a response now. Multiply by ten PRs a week, and that's your weekend.

Maintainer burnout isn't caused by writing code. It's caused by reviewing other people's code.

That's the exact problem Octopus was built to solve. Giving it to the people who need it most felt less like generosity and more like the obvious move.

The Selfish Version

I want to be honest. This isn't pure altruism, and the self-interested case is actually the stronger argument.

Public repos are where Octopus gets battle-tested. A private SaaS codebase looks broadly similar across customers. Open source is wilder: embedded C, Rust kernel patches, Lua game engines, six-decorator-deep Python ML libraries. If we can review those well, we can review anything.

Word of mouth in OSS is the best growth channel software has. None of that happens if your free tier is artificially crippled.

And open source is honest. Bad suggestions get called out in PR threads in public. We can't hide behind closed-source NDAs. That keeps us better than any internal QA process would.

Why "OSI-Licensed" and Not Just "Public"

There's a real difference between a permissively-licensed library and a public repo with a "no commercial use" license slapped on it. The first is open source. The second is source-available with a paywall, and that's fine, but it's not what we're subsidizing.

We use the OSI's list as the line: MIT, Apache 2.0, GPL, BSD, MPL, the standard ones. If your project is genuinely open, you qualify.

The Setup

One file in your repo:

# .github/workflows/octopus.yml
name: Octopus Review
on:
  pull_request:
    types: [opened, synchronize]

permissions:
  contents: read
  pull-requests: write

jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: octopusreview/action@v1

That's it. No dashboard signup gymnastics. No credit card "just in case." No quota meter ticking down.

The Catch

There isn't one. We pay for the LLM tokens, the indexing storage, the runners on our side. The maintainer pays nothing. There's no "we train on your code" clause: public code is already public, and we don't need to train on it to review it.

If you maintain an open source project, the workflow file above is the entire onboarding. Octopus itself is MIT-licensed and lives on GitHub. You can self-host the whole thing if you'd rather not depend on us, and that option stays open too.

To every maintainer reading this: thank you for the code I shipped this year on top of yours. This is the smallest piece of it I know how to give back.

Tags: opensource, ai, codereview, devtools, github