Build your web and mobile apps with AI agents

You write the tasks, and specialised AI agents build the web interface, the API and the mobile app in your repositories. Every change comes as a merge request, reviewed by an agent and then by you, with its preview.

Create my space Book a demo

Your GitHub or GitLab repositories
Every change as a merge request
A visible cost for every task

Aurore StudioSearch or ask ERHA

Booking app

BoardBacklogVersions

To do2

In-app payment on mobileMobile

Export bookings to CSVv1.4

In progress2

Available slots endpointAPI

Booking calendarWeb

In review1

Appointment reminderReview

What slows down app development

The roadmap is always longer than the team can ship, and each part of the app needs its own specialty.

A team that is too small

Two developers for an API, a web front end and a mobile app: something always has to wait.

Tickets that grow old

Small improvements always come after the emergencies and sit in the backlog for months.

Code you can no longer see

With some contractors, the code and the history of decisions stay on their side.

What your agents build

Each agent in the catalogue has its own role. The Start button splits a task between the ones it needs.

Web interfaces

Nora builds the screens, forms and components of your web app.

API and data model

Julien writes the endpoints, the migrations and the server-side business logic.

Mobile apps

Marc builds the screens and features of your mobile app.

Code review

Hugo reviews the changes and flags what needs fixing before you review them yourself.

Merge requests and previews

Agents work on a branch, open a merge request and produce a preview.

Releases and planning

Board, backlog, versions and planning: Patrice, the project manager, helps you keep the roadmap on track.

Merge request !42Ready for review

Pay in three instalments at checkout

Hugo · 6 min ago·4 files changed

Build
Tests
Preview

store-git-pay-in-3.vercel.app

How to build an app with ERHA

Your project groups its applications: web, API, mobile, library. Agents code in an isolated session, and you decide what gets merged.

01You connect your repositoriesOne application per part of the product, on GitHub, on GitLab or in a repository hosted by ERHA. A monorepo works too.
02You write the tasksOn the board or in the backlog, grouped by version. The Start button splits each task between the agents it needs.
03You review and mergeHugo reviews, then the task goes to review with its merge request and preview. You test it, then you approve.

An example: one feature across API, web and mobile

An eight-person startup runs a booking app: an API, a web front end and a mobile app, in two GitLab repositories.

The CTO writes the "Appointment reminder" task and clicks Start.
Julien adds the endpoint and the migration, Nora the settings screen, Marc the mobile notification.
Hugo reviews the merge requests and flags two points to fix.
The CTO tests the preview, then merges the merge requests.

Outcome

The feature ships in version 1.4, with the history of every change in the repositories and the task's cost on display.

The ERHA building blocks involved

ProjectsThe project and its applications, with repositories, tasks, versions, planning and previews.AgentsNora, Julien, Marc and Hugo for development and review, Patrice for project follow-up.

Frequently asked questions

Who owns the code the agents write?

With a GitHub or GitLab repository, the code is in your repository, with its commits and merge requests. Any team can pick it up.

Do agents have access to our secrets?

Agents code in an isolated environment, with access to the task's repository. No platform secret goes into it.

How is this different from a coding assistant like Copilot?

A coding assistant helps a developer inside their editor. Here, an agent takes a whole task and opens a merge request, another agent reviews it, and you approve the result.

Can we work alongside our own developers?

Yes. Agents' merge requests land in your repositories like a colleague's, and your team reviews them from the same task board.

How much does building a feature cost?

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

Keep reading

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.TeamsTech and ITDevelopment, maintenance and documentation handed to agents on your repositories.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