Source: https://quadevs.com/software-maintenance/

Title: Software maintenance and application support | quadevs

[Home](https://quadevs.com/)/ Software maintenance and application support

# Software maintenance and application support

An owner for a product already in production: incidents, small changes, upgrades and the routine work that keeps the next incident away.

[Tell us about your project](https://quadevs.com/contact/)  [or email us](mailto:hello@quadevs.com)

**Software maintenance** starts the day after launch. Someone has to answer alerts, fix what breaks, add small features, keep frameworks on supported versions and write down how the system fails. We do this for products we built and for products we inherit from other teams.

## Support we provide

An incident posts to Slack or Telegram with diagnostics; an engineer follows the runbook, and the fix, the upgrade and the handover notes land in turn.

- ### Monthly hours

  A fixed budget of hours each month for incidents, changes and upkeep.
- ### Alerts with context

  Incidents posted to Slack or Telegram with diagnostics attached.
- ### Failure runbooks

  Written steps for each failure we have seen in your system.
- ### Version upgrades

  Frameworks, packages and servers kept on supported versions.
- ### Website maintenance

  WordPress and PHP sites updated, and hosted on LiteSpeed under contract if you want.
- ### Team handover

  Runbook, dashboards and a recorded walkthrough when your own team takes over.

## Systems we look after

- [Trading operations terminal](https://quadevs.com/case/trading-terminal/)

  A single operations person runs dozens of trading bots on our platform, and Telegram pages the on-call with the PnL context included.
- [HEDIS measurement pipeline](https://quadevs.com/case/hedis-pipeline/)

  Incidents in our HEDIS engine reach Slack together with the diagnostics for the stuck order.
- [WordPress site fleet](https://quadevs.com/case/wordpress-fleet/)

  Hosting and upkeep for tens of WordPress sites are fixed contract lines for their owners.
- And many more projects

  [All case studies](https://quadevs.com/cases/) [Ask about your project](https://quadevs.com/contact/)

How a build turns into ownership: [how we engage](https://quadevs.com/process/). Older products brought up to date first: [legacy modernization](https://quadevs.com/legacy-modernization/).

## How maintenance starts

1. ### Current state

   Describe the product, its hosting, how incidents reach someone today and what keeps breaking.
2. ### Access and alerts

   We get read access, route alerts to a channel you choose and write the first runbook.
3. ### Monthly cycle

   Hours go to incidents first, then to the agreed list of fixes and upgrades.

**And much more.** [Ask about your project](https://quadevs.com/contact/)

## Common questions

What do your application support services cover?

Monitoring, fixes, updates of the runtime and its libraries, and small changes, on a monthly plan or by the hour.

## Who answers when your product goes down at night?

Describe the product, where it runs and how incidents are handled now.

### Your project brief
