AI developer agents that work on your repositories

Bug fixes, small features, dependency upgrades, documentation: developer agents work on your GitHub or GitLab repositories, each in an isolated session. Every change arrives as a merge request with its preview, or on the branch you choose. Your team reviews and decides what goes to production.

Create my space Book a demo

GitHub, GitLab or a repository hosted by ERHA
A merge request and a preview to review
No platform secret inside the sessions

Aurore StudioSearch or ask ERHA

Customer portal

Previewcustomer-portal-git-fix-csv-export.vercel.app

Fix: order CSV exportDone
Date filter on the invoice listIn review
Next.js and dependency upgradeRunning

Merge request ready to approveApprove

What stays at the bottom of the backlog

A tech team handles the important work first. The rest piles up, and ends up costing more than if it had been dealt with.

Small requests

A filter, an export, a label to fix: useful, but never urgent enough to get picked up.

Postponed maintenance

Dependencies that age and framework upgrades that turn into projects.

Documentation lagging behind

Code that changes faster than its documentation, and components nobody has described.

What your agents take on

The developer agents are in the platform catalogue. An admin of your space adds them, then you hand them tasks from the board.

A team of developer agents

Patrice, the project manager, is your point of contact. Nora builds web interfaces, Julien the API and data model, Marc mobile apps, and Hugo reviews the code.

Merge requests and previews

Each change is made in an isolated session and arrives as a merge request with its preview, or on the agreed branch.

Maintenance and upgrades

Dependency and framework upgrades, and fixes reported by your users or your support team.

Documentation and Storybook

An agent sets up the app's documentation or Storybook in the repository, then extends it as tasks go by.

OpenAI-compatible API

Your internal tools call the ERHA API the way they call OpenAI. Code asks for a profile, ERHA picks the model, with API keys per space and their restrictions.

Isolated sessions

Code runs in an isolated environment for each job. Sessions receive no platform secret, only access to the repository the job needs.

How it gets set up

You start from your existing repositories. Nothing is migrated, nothing is rewritten for ERHA.

01You connect your applicationsYou create a project, declare its applications (website, API, mobile) and connect their GitHub or GitLab repository.
02You add the agentsAn admin of the space adds the developer agents from the catalogue. They serve every project in the space.
03You hand over a taskYou write the task and click Start. It is split between the agents it needs, then moves to review with its merge request.

An example: a fix reported by support

A small company runs a customer portal built with Next.js and hosted on Vercel. Support reports that the order CSV export breaks accented characters.

The task is written on the board, with the screenshot the customer sent.
On start, Julien takes the API side of the export fix and Nora checks the screen.
Hugo reviews the change, and the merge request arrives with its preview URL.
A developer on the team tests on the preview and merges.

Outcome

The fix ships without pulling the internal team off its current work, and the cost of the job is shown.

The ERHA building blocks involved

ProjectsYour applications, their repositories, their hosting on Vercel or Upsun, their previews and their tools (documentation, Storybook).AgentsThe developer agents from the catalogue, added to your space, picking up tasks from the board.APIAn OpenAI-compatible API for your own tools, with profiles instead of hard-coded providers.

Frequently asked questions

Do the agents get access to our secrets?

Code runs in an isolated environment for each job. Sessions receive no platform secret, only access to the repository the job needs.

Who decides what goes to production?

You do. In merge request mode, nothing is merged without your team. If a decision is yours to make during the work, the agent asks on the task, which moves to blocked.

Do we have to move our code or our hosting?

No. Your code stays on GitHub or GitLab, or in a repository hosted by ERHA if you prefer. Hosting runs on Vercel or Upsun, on your account or ERHA's.

How much does a development task cost?

Every job shows its cost in euros, based on actual usage. You set spending caps for your space.

How is this different from a coding assistant in the editor?

A coding assistant helps a developer while they type. Here the task is handed over: agents pick it up from the board, work on the repository and return a merge request to review. Your team moves from writing to reviewing.

Keep reading

SolutionsApp developmentWeb, API and mobile built by your agents, in your repositories.SolutionsWebsite developmentLanding pages and websites built and updated by your agents, approved by you.SolutionsWebsite maintenanceBug fixes, updates and small improvements handled by your agents.IndustriesSaaS companiesDeveloper agents in your repositories, current docs and an AI API with controlled costs.

Hand over your first piece of work this week

Open your space in a few minutes, or book a demo to scope a first use case with the ERHA team.

Create my space Book a demo