Start a project

/08 Service

Maintenance & support

We take responsibility for systems in production, including systems that we did not build. We patch, monitor, and improve them, and report every month.

/01 Problems and fixes

Where this work often fails, and how we prevent it.

  1. /01
    The problem
    The original team left, and nobody knows how the system works or what can break.
    What we do
    We start with a written assessment of the code, the infrastructure, and the risks. You see what we found before we accept responsibility.
  2. /02
    The problem
    Dependencies age for years until a security issue forces an urgent upgrade.
    What we do
    We apply dependency and security patches on a fixed schedule. Critical issues get a patch within the time that we agreed with you.
  3. /03
    The problem
    An outage starts at night, and nobody answers the phone.
    What we do
    We monitor the system and respond to incidents within agreed response times. Each incident gets a timeline and a written review.
  4. /04
    The problem
    Small requests wait for months, because no budget exists for them.
    What we do
    Each month includes hours for small improvements. You set the priorities, and the monthly report shows what we did.

/02 Deliverables

What this service gives you.

You receive

  • A written risk assessment of the code and the infrastructure
  • Dependency and security patches on a fixed schedule
  • Monitoring, alerts, and agreed response times
  • A timeline and a written review for each incident
  • Monthly hours for small improvements
  • A monthly report on health, incidents, and response times

Typical work

  1. 01Support for a platform after the original vendor leaves
  2. 02Patches and monitoring for a business-critical system
  3. 03Dependency upgrades for a system that is years out of date
  4. 04Incident response with agreed response times
  5. 05A steady reduction of a backlog of small bugs

/03 Ways to engage

Three engagement models.

  • /01

    Do you have a defined project?

    Project delivery

    • One senior team from the first call to launch
    • A signed definition of done for every milestone
    • Working software to review every week
    • Handover to your team, or Ongoing ownership by ours
  • /02

    Do you need more senior engineers?

    Dedicated team

    • Engineers picked for your stack and your industry
    • Daily work inside your tools and meetings
    • A monthly check on fit and results
    • Monthly changes to team size, with notice
  • /03

    Do you have a system that must not stop?

    Ongoing ownership

    • An assessment of the system before we accept it
    • A fixed monthly budget and agreed response times
    • Security patches, monitoring, and on-call coverage
    • A written report every month

/04 FAQ

Questions clients ask first.

Do you have a different question? Ask us directly

Will you adopt a system another team wrote?

Yes. We designed this service for that case. We do a short assessment first, so both sides know the risks before the agreement starts.

How does this service relate to Ongoing ownership?

Ongoing ownership is the engagement model for this service. It sets a monthly budget and response times by severity. We report our actual response times every month.

Can we end the agreement?

Yes, with the notice that the agreement states. All code, documentation, and access stay in your accounts. We plan the transfer with the new team, step by step.

/05 Related

/ Next step

Talk to us about maintenance & support.

Send a short note about your system and your constraints. We reply within one working day.

Start a project hello@aeontechnologies.io