Gerrit, Google's legendary code review system, pioneered a fundamentally different approach to pull requests than what GitHub popularized. Where GitHub PRs treat each commit as atomic and immutable once merged, Gerrit tracks patch sets—successive revisions of the same logical change, with reviewers able to compare diffs between versions and approve specific revisions rather than a branch. Gerrit also enables per-file sign-offs, allowing different reviewers to approve different sections of code, and maintains deterministic rebasing semantics critical for projects where change history matters. Despite Gerrit's power, most modern teams use GitHub, GitLab, or Gitea, leaving them without these capabilities. Maiao, a new open-source project gaining traction on GitHub, bridges this gap by implementing Gerrit's change control model as an abstraction layer across multiple platforms.

Maiao works by layering atop existing Git hosting APIs and webhooks, translating between Gerrit-style workflow patterns and the native PR/MR systems of GitHub, GitLab, and Gitea. Rather than forcing teams to migrate infrastructure, Maiao allows developers to keep their existing hosting while gaining structured review practices. The tool tracks patch iterations server-side, displays per-file reviewer sign-offs in a unified interface, and enforces rebasing discipline without manual intervention. This architectural approach—treating Git hosts as interchangeable backends—signals a shift in how developers view platform lock-in. Teams managing monorepos with dozens of simultaneous reviewers, or projects like Kubernetes where change provenance and approval chains matter legally or operationally, have traditionally been forced to deploy Gerrit. Maiao lowers that barrier, enabling organizations already invested in GitHub or GitLab to adopt Gerrit's rigor without wholesale infrastructure overhaul.

The emergence of Maiao reflects a broader developer concern: standard pull request workflows inadequately serve large, distributed teams reviewing changes to critical systems. GitHub's PR model assumes relatively lightweight review—one or two approvals per change. Enterprise and open-source projects stewarding complex codebases need granular, auditable approval trails. By decoupling workflow semantics from hosting platform, Maiao lets teams define review policy independently of whether code lives on GitHub or GitLab. In practice, this means a team can enforce rules like 'every function touching security subsystem requires sign-off from two specific reviewers' and 'changes rebase cleanly onto main,' then apply that policy consistently whether code moves platforms or teams collaborate across different hosting solutions. For growing projects outgrowing GitHub's review model but unable to justify Gerrit's operational overhead, Maiao offers a pragmatic third path.