Every pull request.
Your agent on it.
Catch bugs. Understand changes. Ship with confidence. A review agent that runs on your infrastructure.
No seat fees. Your models. Your keys.
Bring your own model keys
Switch providers by changing one setting. Your GitHub workflow stays the same.
- OpenAI
- Anthropic
- DeepSeek
- OpenRouter
- Groq
- and more
How it works
How a pull request gets its first pass
Deploy once. After that, every pull request goes through the same five steps, and all of the output appears in GitHub.
Step 1
Deploy once on servers you control
Install Strivon next to the rest of your stack. The GitHub App key and your model keys stay in your environment.
Step 2
A pull request opens
Strivon starts a review when the pull request opens, or when someone approves it, depending on your settings. It adds a reaction so the author knows work has started.
Step 3
It reads the diff
Strivon checks the changed code for bugs and correctness problems. When the diff touches risky APIs, it runs a security pass too.
Step 4
Findings land on the changed lines
Each finding is an inline comment on the line it is about, with a summary in the conversation. Comment /describe, /ask, or /triage for more.
Step 5
Large changes get a partial review
When a diff is too big to read in full, Strivon reviews what it can and lists the files it skipped.
Examples
What Strivon posts on a pull request
Four commands. Each answer appears in the pull request thread.
/reviewFindings on the lines that changed
Separate passes check correctness, security, quality, and tests. A final pass drops duplicates and weak findings before anything is posted.
- Each finding is an inline comment, with a summary in the conversation
- Runs when the pull request opens or is approved, or when you comment /review
- P0 to P2 findings fail the Strivon Review check. P3 findings do not
- Small docs-only pull requests get a shorter check instead of a full review
Strivon review
Concurrent reads can both miss the lock and overwrite each other in src/config.ts.
Race on the shared settings map.
Shutdown path lacks a drained-queue test.
Pricing
$0
No per-seat fee
Know the cost before you connect GitHub or add an AI provider.
- $0 per developer
Strivon costs nothing per seat
Adding a fiftieth developer adds nothing to the Strivon bill.
- Hosting and model usage
You pay your own vendors
You pay for the server, the Postgres database, and the model provider.
- No third-party data path
Your network, your provider
Review traffic goes only to the model provider you configure.
Compare
Strivon compared to hosted reviewers
Each tool reviews pull requests. They differ in where the review runs and who holds the model keys.
| Tool | Deployment | Difference |
|---|---|---|
| Strivon | Self-hosted | You run the reviewer, hold the model keys, and pick the provider. |
| CodeRabbit | Cloud SaaS, self-host on enterprise plans | Subscription pricing. Review data goes through their servers. |
| Greptile | Cloud SaaS, self-host option | Indexes the whole repository for cross-file context. |
| Cursor Bugbot | Cloud, inside the Cursor ecosystem | Bug-focused review that needs Cursor. |
| Macroscope | Cloud SaaS | Hosted GitHub review with a managed pipeline. |
FAQ
Questions teams ask before they deploy
If your question is missing, email us and we will add the answer here.
What is Strivon?
A GitHub App you run on your own servers. You connect GitHub and a model provider, and it posts reviews, descriptions, and answers on your pull requests.
Is Strivon a self-hosted alternative to CodeRabbit?
Yes. It reviews pull requests, comments on changed lines, writes summaries, and answers commands in GitHub. CodeRabbit runs on its servers. Strivon runs on yours, with your credentials and model keys.
How does Strivon compare to Greptile?
Greptile is a cloud reviewer that indexes whole repositories. Strivon reads each pull request from its branch and diff, on your servers, with the model provider you choose.
Does Strivon replace Cursor Bugbot?
Bugbot runs inside the Cursor ecosystem. Strivon reviews GitHub pull requests on your own servers with your own model keys, with no editor requirement.
Which models does Strivon support?
OpenAI, Anthropic, Google, DeepSeek, OpenRouter, Groq, and more. You set the provider and its API key on the machine that runs reviews.
Does Strivon only work with GitHub?
Yes, for now. GitLab and Bitbucket are not supported.
Where should I host Strivon?
On a VPS you control, with HTTPS in front of the web process. Hetzner, Hostinger, and DigitalOcean all work. Dokploy or Coolify can handle the domain and the certificate.
Installation
Three steps from a fresh machine to a review
You need Docker, a GitHub App, and one model provider key. GitHub must reach your host over HTTPS.
Step 01
Create a GitHub App
Register the App, generate a private key, and install it on a test repository. If you install it on selected repositories only, include that one.
- Webhook URL
- https://your-host/webhooks
- Homepage URL
- https://strivon.dev
- Subscribe to
- Pull requests, issue comments, pull request review comments, workflow runs, check suites, check runs, and statuses.
Step 02
Fill .env and start the stack
Copy the example env file. Paste the App private key as one line, the webhook secret, and a provider key. Then start Strivon with Docker Compose.
Terminal
cp .env.example .env # Paste the one-line GitHub App PEM, WEBHOOK_SECRET, # and your provider key docker compose build docker compose up -d
Minimum keys to set
.env
GITHUB_APP_ID=... GITHUB_APP_PRIVATE_KEY=... WEBHOOK_SECRET=... PI_PROVIDER=openai PI_MODEL=gpt-4o-mini OPENAI_API_KEY=sk-...
Step 03
Open a pull request and comment /help
Comment /help as a repository owner, member, or collaborator. Strivon ignores commands from other accounts.
/review/describe/verify/cancel/ask …/triage/triage preview/triage all/help
YOUR CODE. YOUR INFRASTRUCTURE.
Your next PR.
Already on it.
Give every pull request a second set of eyes. Run Strivon on your servers, with the models you choose.
