Back to Home
Doc Ref: OTL-SLA-5.0Tier-1 Enterprise Support

Service Level Agreement (SLA)

Enterprise Availability, Priority Matrix & Support Commitments • Effective Date: September 2026

Core Enterprise SLA Metrics at a Glance

99.9%Uptime Commitment< 43.8 min/mo unscheduled
≤ 15 MinP1 Critical Response24/7/365 live triage
< 1 HourRPO (Recovery Point)Automated hourly snapshots
< 2 HoursRTO (Recovery Time)Rapid failover & restore
1.0

Scope of Service & Deployment Topologies

This Service Level Agreement ("SLA") governs the technical support, availability standards, incident remediation, and maintenance services provided by Oduk Tech Limited to enterprise clients subscribing to our Managed Services, Cloud Hosting, or Enterprise Support Retainers across Kenya and Tanzania.

Systems covered under this SLA include:

  • ERPNext Core & Frappe Applications: Core relational databases, web application workers, and automated background jobs (Redis, Celery).
  • SACCO & Microfinance Core Engines: Member deposit ledgers, mobile loan disbursement webhooks, and interest calculation cron jobs.
  • Healthcare Information Management Systems (HIMS): Emergency triage queues, inpatient admissions, laboratory telemetry, and pharmacy dispensing modules.
  • Statutory Fiscal Middleware: KRA eTIMS invoice signing gateways and TRA EFDMS fiscal transmission endpoints.
  • Managed Cloud Infrastructure: Dedicated application servers, database instances, reverse proxies, and automated SSL certificate lifecycles.
2.0

99.9% Availability Commitment & Measurement Formula

Oduk Tech Limited commits to maintaining a Monthly Availability Percentage of not less than 99.9% for all hosted production applications. System availability is monitored 24/7/365 via automated multi-region ping monitors checking synthetic API health probes at 60-second intervals.

Availability Calculation Formula:Monthly Uptime % = [ (Total Scheduled Minutes in Month - Unscheduled Downtime Minutes) / Total Scheduled Minutes in Month ] × 100

* Note: In a standard 30-day month (43,200 scheduled minutes), 99.9% uptime allows for a maximum cumulative unscheduled downtime threshold of 43.2 minutes.

Exclusions from Uptime Calculations:

Unscheduled downtime excludes: (a) pre-notified scheduled maintenance windows; (b) broad-scale telecommunication carrier failures (e.g. national fiber backbone cuts or Safaricom national gateway outages); (c) client-directed server shutdowns or unapproved modifications to host configurations; and (d) events of force majeure.

3.0

Scheduled Maintenance Windows

To preserve system integrity and deploy security patches, scheduled maintenance is conducted under the following parameters:

Off-Peak Window:Sundays between 01:00 AM and 04:00 AM East Africa Time (EAT), when enterprise transactional traffic is lowest.
Advance Notice:Minimum of five (5) business days written notice dispatched to designated technical liaisons.
Duration Cap:Scheduled maintenance is strictly capped at a cumulative maximum of 4 hours per calendar month.
4.0

Four-Tier Incident Severity Matrix & Target Response Times

Incidents reported to our engineering operations desk are classified into four distinct severity tiers, each backed by legally binding response and resolution commitments:

Severity LevelOperational Impact DescriptionInitial ResponseWorkaround SLAResolution Target
P1 - Critical BlockerComplete production system outage; database failure; POS tills halted at retail checkout; SACCO core deposits offline; hospital emergency triage paralyzed. No workaround exists.≤ 15 Minutes (24/7/365)≤ 2 Hours≤ 4 Hours
P2 - Major DegradationCore business module severely impaired (e.g. KRA eTIMS invoice signing offline while standard sales order works; mobile money callbacks delayed > 15 min; batch payroll processing halted).≤ 1 Hour (8am-8pm)≤ 4 Hours≤ 8 Hours
P3 - Moderate DefectNon-critical functional bug; isolated report calculation discrepancy; non-blocking UI formatting issue; single user permission configuration conflict. Operational workaround exists.≤ 4 Business Hours≤ 12 Hours≤ 24 Business Hours
P4 - Minor InquiryGeneral how-to questions; routine report configuration requests; bulk data import queries; new staff onboarding requests; cosmetic template adjustments.≤ 8 Business HoursN/ANext Sprint Release
Incident Progression Protocol: For Severity 1 (P1) incidents, our incident commander issues written status updates via SMS, email, and dedicated WhatsApp bridge every 30 minutes until full resolution is verified.
5.0

Service Credits & Financial Accountability

We stand behind our availability commitments with direct financial accountability. If Oduk Tech fails to achieve the monthly 99.9% uptime threshold, Licensee is eligible to receive Service Credits applied against the following month's support and hosting invoice:

Monthly System AvailabilityService Credit EntitlementApplication Method
≥ 99.90%0% (SLA Target Fully Met)Standard billing
99.00% – 99.89%10% CreditDeducted from next monthly hosting/support retainer
98.00% – 98.99%15% CreditDeducted from next monthly hosting/support retainer
< 98.00%25% CreditDeducted from next monthly hosting/support retainer

* To receive service credits, Licensee must submit a written claim to sla@oduktech.com within thirty (30) calendar days following the conclusion of the affected billing month.

6.0

Backup Policies, Disaster Recovery & RPO / RTO

Business continuity is guaranteed through redundant backup architectures and strict disaster recovery parameters:

Recovery Point Objective (RPO) ≤ 1 Hour

Automated incremental database transaction log replication runs every hour. In the event of catastrophic primary hardware failure, data loss is guaranteed to not exceed 60 minutes of transactional records.

Recovery Time Objective (RTO) ≤ 2 Hours

Our automated orchestration scripts and hot-standby container mirrors enable full system restoration, DNS failover, and database integrity verification within 120 minutes of declared disaster.

Offsite Geo-Redundancy: Daily encrypted full database dumps are replicated to an isolated geographic region with automated SHA-256 integrity checksum verification.
7.0

Client Prerequisites & Responsibilities

Achievement of these SLA commitments relies upon the cooperative fulfillment of the following operational prerequisites:

  • Designated Technical Liaisons: Client shall designate up to three (3) primary technical contacts authorized to report Severity 1 & 2 incidents and sign off on resolution verifications.
  • Network Infrastructure: Client maintains stable local area networking, branch power backup (UPS/generator), and internet connectivity required to access the cloud environment.
  • On-Premise Access Credentials: For on-premise deployments, Client provides timely and secure VPN or SSH bastion access to allow Oduk Tech engineers to perform diagnostics.
8.0

Incident Reporting, 24/7 Escalation & Contacts

Enterprise incidents must be reported through our prioritized escalation pathways:

Kenya Incident Desk (Nairobi HQ)

Emergency 24/7 Hotline: +254 726 444 005 / +254 702 568 824

Technical Escalation Lead: Billy Frankline (CTO & Co-Founder)

Lead Solutions Engineer: Oscar Adwar (+254 727 870 117)

Physical Address: Valley View Park, Parklands, Nairobi, Kenya

Tanzania Incident Desk (Dar es Salaam)

Emergency 24/7 Hotline: +255 754 710 459

Country Operations Lead: Emmanuel Majwala

Business Development: Moses Njue (+254 799 182 130)

Support Email: support@oduktech.com

Enterprise Support Portal: Log into your dedicated support desk at support@oduktech.com with your corporate contract ID for prioritized automatic queue placement.
© 2026 Oduk Tech Limited. All Rights Reserved.