Service Level Agreement (SLA)

Our uptime commitments, incident response tiers, and service credit terms for commercial production deployments.

Last updated August 30, 2026 · Effective August 30, 2026

Effective Date: August 30, 2026 Entity: Kuklabs Inc. (Delaware, USA)

This Service Level Agreement ("SLA") sets forth the availability targets and support response benchmarks for commercial subscriptions of KukBook / KukERP.


1. Monthly Uptime Commitment

Kuklabs commits to maintaining a Monthly Uptime Percentage of at least 99.9% for Core Production Services during each calendar month.

$$\text{Uptime Percentage} = \frac{\text{Total Minutes in Month} - \text{Downtime Minutes}}{\text{Total Minutes in Month}} \times 100$$

Core Production Services Covered:


2. Service Credit Schedule

If Kuklabs fails to meet the 99.9% Monthly Uptime Percentage, eligible commercial customers are entitled to request Service Credits as follows:

Monthly Uptime PercentageService Credit (% of Monthly Subscription Fee)
99.0% to < 99.9%10% Credit
95.0% to < 99.0%25% Credit
< 95.0%50% Credit

*Service credits are applied against future invoice billing cycles and are non-refundable for cash.*


3. Support Severity Levels & Response Targets

Severity LevelDescription / CriteriaTarget First ResponseTarget Resolution / Workaround
P1 — CriticalTotal system outage, catastrophic data write failure, or primary web app down for all users.< 1 Hour (24/7/365)< 4 Hours
P2 — MajorCore module degraded (e.g. invoice creation or payment sync down), but partial platform operational.< 4 Hours (Business Days)< 12 Hours
P3 — MinorNon-critical functionality defect, report rendering glitch, or UI styling issue with standard workaround.< 8 Hours (Business Days)Next scheduled maintenance release
P4 — RequestGeneral inquiry, onboarding guidance, or feature request.< 24 Hours (Business Days)N/A

4. SLA Exclusions

Downtime does not include unavailability resulting from:

  1. Scheduled Maintenance: Maintenance windows announced at least 48 hours in advance via our Status Page, conducted during off-peak weekend hours.
  2. Third-Party Upstream Outages: Widespread outages of public cloud providers (e.g. a regional loss at our cloud hosting provider) or third-party bank payment gateway downtime.
  3. Customer Actions: Uncoordinated load testing, misconfigured customer DNS records, or compromised client credentials.
  4. Force Majeure Events: War, natural disasters, acts of government, or national internet infrastructure outages.