Website and application maintenance, handled by AI agents

A bug to fix, a dependency to update, a field to add: you ask in one sentence, an AI agent makes the change in the code, and you approve the merge request after checking the preview. Every job shows its cost.

Create my spaceBook a demo
  • A request in one sentence
  • A merge request to approve
  • A visible cost for every task
Aurore Studio
Customer portal
Previewportal.example-services.com
  • Fix: contact form on SafariDone
  • October dependency updatesDone
  • Company ID field at sign-upIn review
  • API documentation updateRunning
Merge request ready to approveApprove

Why website maintenance falls behind

Once the site or app is live, maintenance comes after everything else. Small issues pile up until they become a large project.

Fixes that wait

An annoying but non-blocking bug stays for weeks because the contractor has no slot.

Dependencies never updated

Libraries age, known vulnerabilities pile up, and updating becomes risky.

Documentation that falls behind

Nobody remembers how the app works, or why a given choice was made.

What maintenance by your agents covers

This is application maintenance and support work: fixes, updates and improvements. Agents do it in your repository, and you approve.

Bug fixes

You describe the bug and the page it affects. The agent finds the cause, fixes it and opens a merge request.

Dependency updates

A recurring task opens the update every month. The agent updates the libraries and checks the build.

Small improvements

A field, some copy, a column, an export: one sentence in a task is enough to start the work.

Preview

Every change produces a preview. You check it before the change goes live.

Documentation

The documentation lives in the repository, and agents update it when you ask.

Cost per task

Every job shows its cost in euros. You know what each fix and each improvement costs.

Online store
To handle3ResolvedIgnored
  • TypeError: Cannot read properties of undefined (reading 'price')src/checkout/summary.tsx · v2.14.0Regression214events
  • UniqueConstraintViolationException: duplicate key order_refsrc/Controller/OrderController.php · v2.14.0Task #31812events
  • ChunkLoadError: Loading chunk 412 failedapp/catalogue/page.tsx · v2.13.2New6events

How maintenance works with ERHA

Your website or app becomes an application in an ERHA project. Every request follows the same path, from task to merge request.

  1. 01You connect the applicationThe GitHub or GitLab repository, the branch, and hosting on Vercel or Upsun if you have it.
  2. 02You report it in one sentenceIn a task, or from a Slack or Discord message that opens the task. The Start button gives it to the right agent.
  3. 03You approve the merge requestHugo reviews the code, the task goes to review with its preview, and you approve the change.

An example: taking over a customer portal

A twenty-five-person services company has a customer portal built three years ago by a contractor who no longer maintains it.

  1. The portal's GitLab repository is connected to an ERHA project.
  2. A recurring task opens the dependency update every month.
  3. Bugs reported by support become tasks, fixed in a merge request with a preview.
  4. The manager approves each merge request and follows the cost of each task.

Outcome

The app is up to date again, and every change has its task, its merge request and its cost.

The ERHA building blocks involved

ProjectsThe application, its repository, hosting, recurring tasks, previews and documentation.AgentsNora, Julien and Marc depending on the part involved, Hugo to review every change.

Frequently asked questions

Can you maintain a site built by another contractor?

Yes, if the code is in a GitHub or GitLab repository. Agents work in the repository as it is, without changing how your code is organised.

Who approves changes before they go live?

You do. You choose the application's delivery mode: a merge request to approve, or a direct push to the branch. Either way, a preview is produced.

Do agents have access to production?

Agents work on the code, in an isolated environment. Going live goes through your repository and your hosting, according to the delivery mode you chose.

How is this different from a standard maintenance contract?

Every request becomes a task you can follow, with its merge request, its preview and its cost.

How is the cost of maintenance calculated?

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.SolutionsApp developmentWeb, API and mobile built by your agents, in your repositories.TeamsTech and ITDevelopment, maintenance and documentation handed to agents on your repositories.IndustriesWeb agencies and studiosClient projects, developer agents in your repos, previews and cost per task.

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 spaceBook a demo