Announcement · June 2026
For the builders building everything else.
Great projects change the world. Critique is committing €100,000 in cloud compute to help more of them ship — half for open source ecosystems, half to power the Critique beta experience.
Critique Open Source Program
Total commitment
€100,000
Committed cloud compute to support open source and power the future of Critique.
€50,000 · Open source
Reviewing, fixing, and helping build projects across the ecosystem.
€50,000 · Critique beta
Performance, scale, and intelligence for the product experience ahead.
Program breakdown
Two halves. One belief: builders deserve better merge infrastructure.
The program is not a marketing stunt. It is compute routed toward the two places Critique can matter most right now — the open repositories the industry depends on, and the beta surfaces where verification has to get faster and sharper.
€50,000 for open source
Review, fix, and help build the projects the ecosystem runs on.
We are putting half the commitment toward open source projects where maintainers are underwater — not because they lack care, but because throughput outran human review years ago.
AI-powered code reviews
Evidence-backed review on real pull requests, not comment spam.
Bug fixes
Bounded repair runs in disposable sandboxes when review finds actionable defects.
Architecture support
Merge-boundary guidance for maintainers drowning in agent-authored diffs.
Build assistance
Help unblocking CI, type errors, and release paths that stall merges.
€50,000 for Critique beta
Power the beta experience customers are already pushing us to ship faster.
The other half stays inside Critique — funding the infrastructure that makes review runs faster, repositories larger, routing broader, and early access more available.
Faster reviews
More compute headroom for parallel specialist passes and shorter queue times.
Larger repositories
Scale indexing and verification for monorepos and high-churn ecosystems.
More AI models
Broader model routing for lead reviewers and specialist sub-agents.
Expanded access
Earlier beta surfaces, workspace runtimes, and program cohorts.
Who should apply
Strong signal beats perfect polish.
We are looking for maintainers and foundations where compute and review capacity would immediately change merge outcomes — not slide decks about someday open-sourcing a wrapper.
- Public repositories with sustained contributor or agent PR volume
- Foundations, package ecosystems, or infra projects downstream teams depend on
- Maintainers who can describe the review bottleneck in concrete terms
- Teams willing to share anonymized outcomes so the program improves for everyone
Pricing context
Program support sits beside the OSS lane.
Critique is built for the same high-volume PR workflows enterprises use: foundations, package ecosystems, and downstream adopters with hundreds of merges per week typically run on Pro ($49/month, 3,000 shared credits) or Team ($149/month, 10,000 credits plus frontier models). Verified open source maintainers can apply for the student/OSS lane at $5/month — the same product surface as Solo-tier access, with unlimited repository indexing. If you need more capacity than the OSS lane includes, we are happy to discuss OSS credit grants and foundation pricing.
Compare plansSpecial thanks
Our compute partners made this commitment possible.
Grateful to Google Cloud and Microsoft Azure for their compute commitments and support. Their infrastructure helps Critique run sandbox verification, review workloads, and the beta-scale surfaces this program funds.
Apply now
Tell us what you maintain and where review is breaking down.
Applications are reviewed manually. Include enough context for us to understand volume, risk, and what a successful partnership looks like in the first 30 days.
- Repository URL(s) and your maintainer or foundation role
- Approximate weekly PR volume and contributor mix (human vs agent)
- What you need most: review capacity, bug fixes, architecture help, or build reliability
- Any security, compliance, or merge-policy constraints we should respect
What happens next
- 01
We read every application
No auto-reject bots. Maintainers deserve a human first pass.
- 02
We scope fit and compute
Accepted projects get a clear support lane: review credits, fix runs, or architecture sessions.
- 03
We ship with receipts
The point is merge outcomes — fewer silent failures, faster trustworthy merges, better contributor feedback.
FAQ
Questions maintainers ask before applying.
What is the Critique Open Source Program?
A €100,000 committed compute initiative announced in June 2026. Half supports open source projects with AI-powered code review, bug fixes, architecture guidance, and build assistance. Half powers the Critique beta experience — faster reviews, larger repositories, more models, and expanded access.
Who can apply for the open source portion?
Maintainers, foundations, and teams stewarding public open source repositories with real merge volume or meaningful ecosystem impact. We prioritize projects where review capacity, architecture help, or build reliability are the bottleneck — not vanity launches.
What does Critique provide to accepted OSS projects?
AI-powered pull request review with evidence, bounded bug-fix and build assistance inside sandboxes, architecture and merge-boundary guidance, and Critique credits aligned to your review volume. High-traffic foundations may also qualify for Pro or Team lanes and custom OSS credit grants.
Is this the same as the $5/month student and OSS pricing lane?
Related but distinct. Verified maintainers can still apply for the Solo-equivalent $5/month OSS lane for ongoing product access. The Open Source Program is a separate compute commitment for projects that need deeper review, fix, and build support beyond the default lane.
How do I apply?
Use the application form on critique.sh/oss-program or email ray@critique.sh with your repository links, maintainer role, weekly PR volume, and what you need most — review capacity, bug fixes, architecture help, or build reliability.
Who are the compute partners?
Google Cloud and Microsoft Azure committed compute resources that help Critique deliver sandbox verification, review runs, and beta-scale infrastructure for the program.