Jarvisby TheSEO
EN
Language · same pageNLNederlands/jarvis/vertrouwen/sla/ENEnglish (UK)/en/jarvis/trust/availability-and-support/ESEspañolnot translated yetWe do not remember your choice and never redirect you automatically.
OPS.J03 · to be decided No binding uptime or response time claim yet
JarvisTrustAvailability
OPS.J03 · availability and supportversion 0.2 · to be decided

Promise what we can measure.

A service level agreement only becomes binding once monitoring, escalation, maintenance and compensation are set up technically and operationally.

The incident process To the trust centreno binding uptime or response time claim yet · six decisions still open
FIG.L01: A service table with the values not in it yetOPS.J03 · to be decided

Six empty fields are more honest here than six percentages

The headline of this page says: promise what we can measure. So here is the form that a service level agreement eventually becomes, with the six decisions still open and an empty field next to each. Below that are the four principles that already apply today and that we can actually demonstrate.

~/jarvis/trust/availability-and-support · open-decisions[note] no commitment
what has not been settledsix open decisions
service window and measurement method for availabilitynot settled yet
exclusions for planned maintenance and external AI providersnot settled yet
P0, P1 and P2, first response and update frequencynot settled yet
support channels per plan and escalation pathnot settled yet
service credits or other remediesnot settled yet
maintenance windows and advance noticenot settled yet
what already appliesdesign principles
incidents get an owner and a status
planned changes get a rollback plan
provider outages are visibly separated from Jarvis outages
critical customer actions stay auditable
# six empty fields, and that is the point: without measurement a percentage about availability or response time is a guess, and a guess does not belong in a commitment

Open decisions

  • service window and measurement method for availability;
  • exclusions for planned maintenance and external AI providers;
  • P0, P1 and P2 definitions, first response and update frequency;
  • support channels per plan and escalation path;
  • service credits or other remedies;
  • maintenance windows and advance notice.

What already applies as a design principle

Incidents get an owner and a status; planned changes get a rollback plan; outages at an external provider are visibly separated from outages in Jarvis; critical customer actions stay auditable.

What applies today

As long as no service level agreement has been made, the arrangements in the terms that apply to you hold: consumer or business. There is no commitment on this page about uptime or response time, because we cannot measure those yet.

Section · Next stepreachable 24/7
Book a call