Proval Self-Hosted Code Review: What to Check First
Proval, a self-hosted code review agent, was posted to Show HN by user dowonseo, and its GitHub repository confirms support for GitLab, Forgejo, and GitHub. That three-platform list matters because most self-hosted review tools lock to a single git host, turning this into a hosting decision rather than a compatibility gamble. This guide lists the criteria to check before adopting Proval, maps its confirmed platform support to real team setups, and names the hosting-cost mistakes buyers make.

Disclosure: this article contains affiliate links. If you buy through them we may earn a commission at no additional cost to you. Our recommendations are based on the evidence recorded alongside this article, and prices were verified on the date shown.
What changed and why it matters
Proval, a self-hosted code review agent, went up on Show HN, posted by user dowonseo, with the project hosted at github.com/seoes/proval. The repository lists support for three source-control platforms out of the box: GitLab, Forgejo, and GitHub.
That third-platform detail is the reason this is worth a second look. Most self-hosted review tools pick one git host and stop there. A tool that already targets GitLab, Forgejo, and GitHub changes the buying question from "does it support my platform" to "where do I run it and what does that cost" — which is a hosting decision, not a compatibility gamble.
What to look for
Before you adopt any self-hosted code review agent, work through these in order:
- Platform match. Confirm the tool talks to the source-control platform your team actually uses today. Proval's repository confirms GitLab, Forgejo, and GitHub; it does not list any others, so don't assume coverage beyond that.
- Self-hosted means you run it. A self-hosted agent isn't a SaaS subscription — you provide the compute, the uptime, and the maintenance. Budget for hosting before you budget for the tool itself.
- Source of truth. Read the project repository directly rather than a summary of it. Show HN threads move fast and get outdated; the repo is the canonical record of what the tool currently does.
- Who's behind it. Note who posted the project and where. Proval was submitted to Show HN by dowonseo, and the canonical repository lives at github.com/seoes/proval — that's the account to watch for updates, issues, and releases.
None of this tells you what the tool costs to run, because self-hosted tools don't have a vendor price tag — the cost is whatever compute you point at it.
Recommended options
There's one tool in scope here, so "recommended options" means matching Proval's confirmed platform support to your setup rather than picking between competing products.
| Your source-control platform | Confirmed Proval support | Decision |
|---|---|---|
| GitHub | Yes | Proceed to a hosting decision |
| GitLab | Yes | Proceed to a hosting decision |
| Forgejo | Yes | Proceed to a hosting decision |
| Anything else | Not listed | Don't assume it works — check the repo before committing time |
Best for: teams already running GitHub, GitLab, or Forgejo who want code review automation without sending code to a third-party SaaS reviewer. Self-hosting keeps the review agent inside infrastructure you already control.
Skip it if: your team is on a platform not listed in the repository, or you don't want to own the hosting and maintenance that a self-hosted agent requires. A self-hosted tool with no confirmed managed offering means every hour of uptime is on you.
Common mistakes
Assuming "supports GitHub" means "runs on GitHub for free." Platform support tells you which source-control API the tool integrates with — it says nothing about where the agent itself runs. Proval is self-hosted, so you still need to provision and pay for the compute that runs it, separate from whatever your GitHub, GitLab, or Forgejo plan already includes.
Skipping the hosting-cost conversation until after adoption. Teams evaluate a self-hosted tool on features, get it working in a test environment, and only then ask what it costs to keep running in production. Do that math first. Before you provision compute for a self-hosted agent, [check current plans and pricing at Vercel](See current pricing at the merchant) so hosting isn't a surprise line item after you've already committed engineering time to the setup.
Treating a Show HN post as documentation. A Show HN submission is a launch announcement, not a spec sheet. It tells you a project exists and who posted it — in this case dowonseo — but for anything else, go to the repository itself rather than relying on secondhand summaries of the thread.
Not checking which platforms are actually listed. It's easy to assume a self-hosted review tool supports whatever platform you happen to use. Proval's repository names three: GitLab, Forgejo, and GitHub. If your team uses something outside that list, verify support in the repo before you invest setup time — don't infer it.
Confusing "self-hosted" with "no ongoing cost." Self-hosted often gets read as "free" because there's no subscription line item. It isn't free — it shifts the cost from a vendor invoice to your own infrastructure bill, plus the engineering time to keep it patched and running.
The decision
If your team already runs GitHub, GitLab, or Forgejo and you'd rather keep a code review agent inside infrastructure you control than send code to a third-party SaaS reviewer, Proval's confirmed platform support makes it worth evaluating. If you're on a different platform, or you don't want the hosting and maintenance overhead that comes with any self-hosted tool, that overhead is the real cost to weigh before you start — not the tool itself.
What this costs right now
Vercel
The last check on this price fell outside our freshness window, so no figure is shown.
Check the current price at VercelPrices move. We print the figure we read and the moment we read it, and suppress anything older than its window rather than guess at the current number.