FounderizerAn agent that fixes the bug
It reads the repository you gave it, pushes the fix, runs your own checks, and tells you what it ran.
The problem
The bug is reported on Friday and fixed on Tuesday, because between the two there is a week of other work. Nothing about it was hard. It was queued behind you.
What the agent does
- Reads the repository you chose, through a GitHub App you installed in your own organisation.
- Writes the fix, pushes it, and runs the checks that are already in your repository — yours, not ours.
- Tells you what it ran and what it got, so the report is the evidence and not a claim.
- Stops at whatever your repository stops at. A protected branch is still protected.
What you grant it
- A GitHub App in your own organisation, on the repositories you choose. GitHub hands the private key to your hub. We hold no token.
- Your own Claude plan, signed in on the machine that runs the agent.
- Whatever your repository already demands of a push: reviews, checks, branch rules.
How a grant works, and why a narrow one costs you less than it looks, is its own page: deciding what an agent may reach.
Where it stops
It has no access to a repository you did not choose, and no way to grant itself one. Anything outside the grant reaches your phone as a question.
The honest limit
It will sometimes be wrong in a way a person would not be. Your checks and your branch rules are what catch that, so an agent is worth most in a repository that already has them.
Questions
Do you get access to my code?
No. Each customer installs their own GitHub App in their own organisation, and GitHub hands the private key to their hub. We have no token, no key and no way in.
Can it push straight to my main branch?
Only if your repository lets anything push straight to it. The agent acts with the access you gave it and GitHub enforces your rules, not ours.
Which repositories can it reach?
The ones you selected when you installed the App, and no others. Changing that selection is your action in GitHub.
The other jobs
Answering customer email
Your mail, in your words, with the ones it should not answer by itself passed to you.
Watching the money
A refund, a failed payment, a complaint: it checks what happened, acts inside the limit you set, and asks when it is outside it.
Shipping the small thing
The feature you never get to. A commit, a deploy, and a note saying what changed.
Keeping watch
Work it keeps without being asked: it checks on its own schedule, and what it finds it sees through to the end.
What it costs, and what you carry before you pay. Anything you want to put to us plainly first: support@founderizer.com.