---
title: "Ongoing support & SLAs"
url: "https://parone.dev/services/support-sla/"
description: "After launch, someone who knows the system is on call. Monitoring, incident response, maintenance and continuous improvement under a defined service level."
---

[← Services](/services/)Run

# Ongoing support & SLAs

After launch, someone who knows the system is on call.

Monitoring, incident response, maintenance and continuous improvement under a defined service level.

[Start a project](/contact/) [See the work →](/work/)

## When clients call us

01You launched and the build team moved on

02Incidents get fixed slowly because nobody owns the code

03Partners need contractual uptime and response times

## What we deliver

-   0124/7 monitoring and alerting
-   02Incident response with defined SLAs
-   03Security patches and dependency upgrades
-   04Performance and cost reviews
-   05Monthly roadmap of improvements
-   06Quarterly architecture review

## Tools we use

-   PagerDuty
-   Datadog
-   Sentry
-   Status pages
-   Runbooks
-   Postmortems

We pick tools your team can hire for and maintain. If you already have a stack, we work in it.

## How we approach it

01The builders staySupport comes from the engineers who built the system.

02Response times in writingSeverity levels, response times and escalation paths, agreed up front.

03Budget for improvementA share of every month goes to making the platform better.

Often paired with [Cloud infrastructure & DevOps→](/services/cloud-devops/)[Fractional CTO / embedded teams→](/services/fractional-cto/) [All services→](/services/)