Use cases
Maintenance for open source, on the public record
Triage, review and releases for public repositories. Every action logged, every comment disclosing that it is automated, 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. Public repositories can apply for verified OSS status, which waives the bill; verification is reviewed by a human, not granted automatically. Every project we maintain gets a page under /oss showing what was handled, so the claim is checkable rather than asserted.
Free for verified public repos
Apply from the dashboard. A human reviews it, approval is not automatic, and we say so rather than implying instant access.
A public receipt
Each project gets an /oss page with its handled counts, and a badge for the README that links back to it.
Contributors are never deceived
Every comment states that it comes from an automated agent. Non-disclosure is a bug, not a configurable option.
Go deeper
See the projects we maintain
The OSS directory lists every public repository the agent looks after, with the issues and PRs it handled.
Browse the OSS directoryPut a fleet of AI developers to work
Bring your own keys and your own boxes, drop a .dz/maintainer/maintainer.yml, and let the loops run. Audited end to end. Access is invite-only.