Skip to content
dvnt.io

Resources · glossary

SLA (service level agreement)

A written commitment from the provider on availability and response time: what counts as an outage, how quickly someone will deal with it, and what happens if they fail to.

Also called
  • SLA
  • service level agreement
  • uptime guarantee
  • support agreement
  1. 01

    What an SLA should contain

    A definition of an outage and its severity, support hours, response time (when someone replies) and resolution time (when it works again), the channel for reporting issues and the consequences of missing the targets. Without the last point an SLA is a declaration, not a commitment.

  2. 02

    Response time is not resolution time

    This is the most common misunderstanding. “Response within 4 hours” means someone will acknowledge the report, not that the site will be back. These two numbers must be kept separate in the contract.

  3. 03

    What it costs

    The shorter the times and the wider the support window, the higher the price, because someone has to be available. A 24/7 SLA for a brochure site is usually overpaying; for a shop at the peak of the season it can be cheaper than an hour of downtime.

  4. 04

    How to work it out

    It makes sense to start with the cost of downtime: how much the company loses per hour of unavailability. Only that number tells you what SLA you need.

In practice

Related terms

  • Website maintenanceOngoing care of a live website: hosting, updates, backups, monitoring and small content changes. A cost you pay every month, whether or not anyone included it in the implementation quote.
  • Vendor lock-inDependence on a single provider, where switching tools or vendors is so costly that it stops being a real option. It is rarely a decision, usually a side effect.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.