A ticket board
To do, doing, review, done. A ticket handed to an agent moves on its own, and stops at review so you can look.
You open a ticket and assign it. The agent works in your repository and hands the code back for review. You approve, and it goes live.

To do, doing, review, done. A ticket handed to an agent moves on its own, and stops at review so you can look.
You group tickets into a version, you see what is left, and the release notes are written from those tickets.
You ask for an article on a topic, it comes back written, ready to review. It sits in your repository like the rest of the site.
The agent works apart, on a copy, and only touches your site through the path you chose.
One sentence is enough: "redo the pricing page". The agent reads your code for the rest, and asks if something is missing.
It never touches what is live. It codes apart, then proposes its changes to you.
You approve, the version fills up, the release notes get written, and the site goes to your host.
On a video call: we go through the tasks eating your team's time and pick the best one to hand to AI.
We connect ERHA to your real repository. You judge on what goes live, not on promises.
Your space goes live: every job is tracked, its cost shown and capped.
No. You create an access limited to the one repository, at GitLab or GitHub, and you cut it whenever you want without asking us.
There is nothing to get back: the code has been yours since day one. You cut the access, another developer takes over, and the project carries on.
You, us, or nobody if you do not want to put it online yet. It is decided project by project, and it can change.
We'll show you ERHA on one of your own files, in 30 minutes.