Service level agreement.

What we commit to on uptime, support and security patches, how we measure it, and what you get back if we miss it.

Last updated 16 October 2026 · Live status at status.grovs.io

grovs Cloud · Scale and Enterprise

99.9%monthly uptime
30 daysChecked every minute from 3 regions
First response to a critical issue
4 hours
Patch for a critical vulnerability
7 days
Credit if we miss the uptime
Up to 50%

1. Who this covers

This agreement sets out what we commit to, and what you get back if we miss it. Which parts apply depends on how you run grovs:

  • grovs Cloud, Scale and Enterprise plans: the uptime commitment (sections 2 to 5) and support response times (section 6).
  • Self-hosted Enterprise: support response times (section 6) and security patch times (section 7). grovs runs on your infrastructure, so its uptime is in your hands, and we help you keep it up.
  • grovs Cloud Free and Growth, and Community: no uptime commitment. Support is by email and community channels, on a best-effort basis.

Where your order form sets different terms, the order form applies.

2. Uptime commitment

We commit to 99.9% monthly uptime for each covered service. That allows at most 43 minutes and 49 seconds of downtime in a 30-day month.

Uptime = (minutes in the month − downtime minutes) ÷ minutes in the month

Covered services

  • Link service: link resolution, redirects and deferred deep links on your domains.
  • SDK and ingestion API: the endpoints the iOS, Android and web SDKs send events to.
  • Messaging API: accepting push and in-app messages for delivery.
  • Dashboard and REST API.

Delivery by Apple (APNs) and Google (FCM) is outside our control and isn't covered. Our part, accepting the message and handing it to them, is.

3. How downtime is measured

We check every covered service once a minute from at least three regions. A minute counts as downtime when either of these is true:

  • Checks fail from two or more regions, or
  • More than 5% of valid requests to the service return a server error (HTTP 5xx) in that minute.

Downtime starts at the first failing minute and ends when checks pass again. Every incident, with its start and end time, is published at status.grovs.io, where you can subscribe to updates.

4. What doesn't count as downtime

  • Planned maintenance announced as described below.
  • Problems caused by your apps, servers, network, DNS records or configuration, or by changes you make.
  • Requests over the rate limits in your plan, or traffic that breaks the terms of service.
  • Outages of Apple, Google or other providers outside our control, and events beyond reasonable control such as natural disasters or large-scale internet outages.
  • Features marked beta or preview.

Planned maintenance

Most maintenance causes no downtime. When it might, we announce it at least 5 business days ahead by email and on the status page, schedule it between 22:00 and 06:00 CET, and keep it under 4 hours a month. Anything beyond that counts as downtime.

Urgent security fixes may need shorter notice. If they cause downtime, it counts.

5. Service credits

If monthly uptime for a covered service falls below 99.9%, you get a credit on that month's fee:

< 99.9%

Below 99.9%

More than about 44 minutes of downtime in a month.

Credit on the month's fee

10%

< 99.5%

Below 99.5%

More than about 3.6 hours of downtime in a month.

Credit on the month's fee

25%

< 99.0%

Below 99.0%

More than about 7.3 hours of downtime in a month.

Credit on the month's fee

50%

Claiming a credit

  • Email [email protected] within 30 days of the end of the affected month. The incident time from the status page is enough; you don't need your own logs.
  • We confirm within 10 business days and apply the credit to your next invoice. If your contract has ended, we refund it.
  • Credits for one month are capped at 50% of that month's fee, and are your remedy for missed uptime.

6. Support response times

For Scale, Enterprise and self-hosted Enterprise customers. You set the severity when you open a ticket; we may change it with you if the impact turns out different.

P1

Critical

Production is down or data is at risk, with no workaround.

First response

4 hours, any day

Updates: hourly until resolved

P2

High

A core feature is broken for many users.

First response

8 business hours

Updates: every business day

P3

Normal

A feature misbehaves and a workaround exists.

First response

2 business days

Updates: as progress is made

P4

Low

Questions, requests and minor issues.

First response

5 business days

Updates: when answered

Business hours

09:00–18:00 CET, Monday to Friday. Critical issues are handled any day, around the clock.

A named engineer

Every Enterprise customer has one engineer who knows their setup.

Urgent contact

Critical issues go through the urgent contact in your onboarding pack.

Incident reports

After a critical incident, a written report within 5 business days.

7. Security patches for self-hosted

When a vulnerability is confirmed in grovs, we ship a patched release within these times, and tell you the moment it's ready:

9.0+

Critical

CVSS 9.0 to 10.0

Patched release within

7 days

7.0+

High

CVSS 7.0 to 8.9

Patched release within

30 days

4.0+

Medium

CVSS 4.0 to 6.9

Patched release within

90 days

< 4.0

Low

CVSS below 4.0

Patched release within

Next release

Patches ship as versioned images with upgrade notes, for the current release and the one before it. Report a vulnerability to [email protected]; we acknowledge reports within 2 business days.

8. Changes to this agreement

We may improve this agreement at any time. We won't reduce what we commit to during your current contract term, and we announce any change at least 30 days before it takes effect.