Best Self-hosted Alternatives to Gerrit Code Review

Review Board is an open source, web-based platform for reviewing code and other project assets like images and documents. It helps teams manage review requests, discussions, and iterative revisions with detailed diffs and strong integration options.

Key Features

• Review requests that group code changes, files, and discussion threads in one place
• Advanced diff viewer with syntax highlighting, interdiffs, moved line detection, and indentation-aware changes
• Inline, multi-line commenting with threaded discussions and issue tracking for required fixes
• Image review and diffing with region-based comments and multiple comparison modes
• Document review workflows (including PDF and office-format review capabilities via extensions)
• Integrations with many SCM systems (including Git, Subversion, Mercurial, and Perforce) and common hosting providers
• Extensible API and extension framework for custom integrations and automation
• Dashboard for tracking incoming/outgoing reviews with filtering and bulk actions

Use Cases

• Team code review workflows outside of Git forge pull requests, especially for multi-repo or non-Git environments
• Reviewing design assets, screenshots, and documentation alongside code changes
• Enforcing review quality with structured discussions and tracked issues before approval

Review Board is well-suited for organizations needing a dedicated, extensible review system that supports both source code and non-code artifacts. Its mature diff tools and broad SCM integration make it a strong option for heterogeneous development environments.

Gerrit Code Review is a code review and project management tool for Git-based projects. It provides a structured review workflow around Git pushes, making it easier for teams to discuss changes and control how updates land in shared repositories.

Key Features

• Side-by-side diff viewer with syntax highlighting and inline comments
• Review-based workflow for proposing, updating, and approving changes
• Integrated Git repository hosting with SSH and HTTPS access for standard Git clients
• Delegatable access controls to manage projects, permissions, and workflows
• Repository maintenance support such as coordinating Git garbage collection across hosted repos
• Plugin architecture for extending server-side functionality

Use Cases

• Enforcing mandatory peer review before changes are submitted to shared branches
• Hosting and managing multiple Git repositories with centralized access control
• Running a review-driven workflow for large or regulated engineering organizations

Limitations and Considerations

• Gerrit’s review model and terminology can require onboarding for teams used to pull-request workflows
• Operating at scale typically involves tuning and operational planning (e.g., repository replication and maintenance)

Gerrit is well-suited for teams that want a rigorous, review-first workflow tightly integrated with Git hosting. Its extensibility and permission model make it a strong option for organizations with complex governance needs.

Kallithea is a web-based source code management platform for hosting and managing Git and Mercurial repositories. It provides a centralized place for browsing code, reviewing changes, and administering repositories with access control and auditing. Built as a fork in the RhodeCode lineage, it targets teams that want a straightforward SCM server with both Git and Mercurial support.

Key Features

• Hosts both Git and Mercurial repositories with a web interface for browsing history, diffs, and file contents
• Pull request / changeset-based code review workflows with inline comments and discussion
• Fine-grained permissions and repository/group management for multi-user environments
• Built-in user authentication options (including external auth integrations) and administrative UI
• Webhooks/integrations for connecting repository events to external systems
• Search and browsing utilities for navigating repositories and changes
• Audit-friendly activity/history views for repositories and users

Use Cases

• Team SCM server for organizations needing both Git and Mercurial in one platform
• Internal code review and collaboration for on-prem development environments
• Central repository hosting for regulated or air-gapped networks

Limitations and Considerations

• Primarily focused on SCM/review; it is not an all-in-one DevOps suite (CI/CD, issues, etc. typically require external tools)

Kallithea fits teams that want a lightweight, administrable Git/Mercurial hosting solution with code review, permissions, and integrations. It is especially useful where Mercurial support is still required alongside Git, without adopting a larger integrated platform.

RhodeCode is an on-premises source code management platform that unifies repository hosting and collaboration for Git, Mercurial (Hg), and Subversion (SVN). It focuses on centralized access control, auditing, and review workflows suited for organizations with strict security requirements.

Key Features

• Unified repository management for Git, Mercurial, and Subversion
• Built-in code review with inline comments and change discussion
• Centralized permission management and role-based access controls
• Auditing and reporting capabilities for compliance and governance
• Workflow automation and integrations to connect repositories with external tools
• Gists/snippets for sharing code and collecting feedback

Use Cases

• Hosting and governing mixed SCM environments (Git, SVN, Hg) in one platform
• Running secure, behind-the-firewall code collaboration for regulated teams
• Supporting SVN-to-Git migration while maintaining ongoing SVN workflows

Limitations and Considerations

• Some advanced functionality and official support are part of the Enterprise Edition rather than the Community Edition

RhodeCode is a strong fit for teams that need a unified, security-focused code collaboration hub across multiple version control systems. It combines repository management, reviews, and permissions into a single platform designed for enterprise governance.

Trac is an enhanced wiki and issue tracking system designed for managing software development projects with a lightweight, process-neutral approach. It combines tickets, wiki pages, and version control references into a single web interface to help teams track work and project history.

Key Features

• Issue tracking with wiki-style markup in ticket descriptions
• Integrated wiki for project documentation and collaboration
• Integration with version control systems such as Subversion and Git
• Automatic cross-linking between tickets, changesets, files, and wiki pages
• Timeline view aggregating project events for quick historical context
• Roadmap and milestones for planning upcoming work
• Reporting and query capabilities for tracking progress and status

Use Cases

• Manage bugs, tasks, and feature requests for software projects
• Maintain project documentation alongside development activity
• Provide traceability between code changes and the tickets they address

Limitations and Considerations

• User interface and workflow model are intentionally minimal and may feel dated compared to newer “all-in-one” dev platforms
• Some advanced features are commonly added via plugins, which can increase maintenance complexity

Trac is well-suited to teams that want a straightforward, self-managed environment for tickets and documentation with strong cross-referencing to source control activity. Its minimalism and extensibility make it a practical choice for organizations that prefer adapting tools to existing processes rather than adopting rigid workflows.

SourceHut is a suite of integrated tools for hosting and collaborating on software projects. It provides a minimal, performance-focused web UI and emphasizes standards-based workflows (notably email-driven collaboration).

Key Features

• Hosted Git repositories with public, private, and unlisted visibility options
• First-class Mercurial hosting alongside Git
• Fine-grained access control, including access for users without accounts
• Continuous integration with fully virtualized builds across multiple Linux distributions and BSDs
• Ad-hoc CI jobs and post-build triggers (email, webhooks, etc.)
• Mailing lists with web-based patch review tools and searchable, threaded archives
• Focused ticket tracking with support for private/security bug reports and email participation
• Markdown- and Git-driven wikis with flexible page organization
• Account security features such as TOTP-based 2FA, audit logs, and PGP-signed/encrypted service email

Use Cases

• Hosting open source projects that prefer email-based patch review workflows
• Running CI for multi-platform builds (Linux and BSD) with reproducible, isolated environments
• Managing project collaboration with integrated repos, tickets, wikis, and mailing lists

Limitations and Considerations

• Designed around a minimalist UI and email/SSH-centric workflows, which may differ from PR-centric forges
• The public service has historically been labeled as “alpha,” which may affect expectations around stability

SourceHut is well-suited to teams and communities that value simple interfaces, strong integrations, and standards-driven collaboration. It offers a cohesive set of tools for maintaining projects without relying on heavyweight, JavaScript-dependent web experiences.