Self-host the review core
The community edition is aimed at teams that want GitHub pull request review, merge safety, and evidence-backed decisions on infrastructure they control.
Community edition
Open source, with a real operating boundary.
Critique is opening a separate community edition for teams that want to self-host the main GitHub pull request review workflow. This is not a raw dump of the private product repo. It is a public boundary built to keep the core review system operable without private inference or hosted company-only systems.
Keep the boundary honest
Inference API and hosted platform-only systems are not the community target. The public repo should stay understandable, operable, and safe to run without private company dependencies.
Preserve the review workflow
Review runs, verification flow, and the main merge-facing surfaces stay central. Open source only works here if maintainers can operate the actual review loop rather than a demo shell.
Scope
What the community edition is actually for.
Included now
- Public community repo on GitHub
- Community landing page, scope docs, and roadmap
- Clean separation from private hosted history
Opening next
- Retained GitHub review routes and shared review primitives
- Self-host setup, environment contracts, and operator docs
- Core dashboard surfaces needed to run review end to end
Out of scope for the community boundary
- Private inference billing and managed API operations
- Hosted-only internal systems that assume Critique cloud ownership
- Anything that would leak private operational history into the public repo
Why a separate repo
Public history matters as much as public code.
Open-sourcing Critique correctly means publishing a repo with a deliberate shape, clear ownership boundaries, and self-host assumptions that make sense outside our hosted environment. The community edition exists so contributors can work in the public without inheriting private operational residue.