Use cases
Maintenance for open source, on the public record
Triage, review and releases for public repositories. Every action logged, and a public project page anyone can check.
Upgrade zod across services
- Read repository context
- Proposed implementation plan
- Running checks
Fix auth redirect loop
- Read repository context
- Proposed implementation plan
- Writing tests
Refresh the quickstart
- Read repository context
- Proposed implementation plan
- Opening pull request
The unglamorous half of maintaining a project
Most open-source burnout is not about writing code; it is about answering the same issue for the fifth time, chasing a repro, and merging a dependency bump at midnight. developerz.ai runs that half. Open-source projects under your own GitHub name run on OSS Free, at no charge. A project whose maintainer opts in to being listed gets a page under /oss showing what was handled, so the claim is checkable rather than asserted. Listing is off by default.
Upgrade zod across services
- Read repository context
- Proposed implementation plan
- Running checks
Fix auth redirect loop
- Read repository context
- Proposed implementation plan
- Writing tests
Refresh the quickstart
- Read repository context
- Proposed implementation plan
- Opening pull request
Free for open-source projects in your own name
Request access through the waitlist; OSS Free carries no charge, with a monthly cap on agent-hours. Verified OSS status is a separate application from the dashboard that a person reviews: approval is not automatic, and we say so rather than implying instant access.
A public receipt
Opt in to being listed and the project gets an /oss page with its handled counts, and a badge for the README that links back to it.
Hard calls go to a person
Security, licence and hostile-tone signals stop the loop and escalate to a person instead of getting a bot reply.
Where it stops and asks you
On a public project, merging stays yours until you hand it over
On OSS Free, and on the verified OSS status a public repository can apply for, the bot merges nothing until your maintainer.yml sets pr.auto_merge: true. A person reviews a verified OSS application; approval is never automatic. A first-time contributor's pull request waits for your approval by default. One from an outside or first-time contributor that touches CI configuration or your policy files is never merged by the bot, whatever your policy says: you review it and merge it yourself. Security, licence and CLA questions always come to you.
Read the OSS verification rulesGo deeper
See the projects we maintain
The OSS directory lists the public repositories whose maintainers opted in, with the issues and PRs handled on each.
Browse the OSS directory
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.