Unlike pull-request forges, Gerrit reviews every Git change as a series of patchsets, and nothing merges until the required approvals are in. Developers upload with a plain git push to a refs/for ref, adding push options for topics, hashtags, work-in-progress, or private changes. Each change gets a page listing reviewers, CCs, an attention set that flags who must act next, and submit requirements driven by labels such as Code-Review and Verified, with a quick approve button for the last missing vote. Side-by-side diffs with syntax highlighting take inline comments written in Markdown, saved as drafts and published together. A Checks tab shows CI runs reported by plugins, and integrations reach Jenkins, GitHub Actions, Zuul, and webhooks. Access rights attach to groups and branch patterns, including regular expressions, and inherit from parent projects and All-Projects. Sign-in works with LDAP, OAuth, OpenID, or HTTP single sign-on, and SAML through a plugin. A query language filters changes by status, owner, reviewer, label, file path, and reviewer count. Projects pick a submit strategy: merge if necessary, fast forward only, rebase if necessary, rebase always, merge always, or cherry pick. A REST API, SSH commands, and a plugin system extend the server, and an optional Review Agent chat panel can summarize a change once an AI provider plugin is installed. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Every bug a team finds, from the first report to the day it is marked resolved, lives in one shared list in MantisBT, an open-source issue tracker. Reporters file issues with a summary, steps to reproduce, severity, and attachments, and email notifications reach the reporter, the handler, monitors, and note authors. Six access levels, from viewer to administrator, can be overridden project by project, and private projects stay hidden from users below the configured level. Administrators define their own status values, workflow transitions, and custom fields. Sub-projects inherit versions and categories from their parents, and issues link as related, parent and child, or duplicates. @mentions pull colleagues into a discussion, tags group related work, and a chronological history records who changed what. Triage works from stored and shared filters, the My View page, and summary charts, while a roadmap and changelog track what each version contains. Reporting comes through CSV and Excel export, optional time tracking with billing totals, and RSS feeds. Sign-in can use LDAP or Active Directory, scripts reach the tracker through REST and SOAP APIs, plugins extend the interface, and 50 languages are included. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0-or-later licensed.