← Kembali ke Beranda
STANDAR JAMINAN KETERSEDIAAN INFRASTRUKTUR & WAKTU TANGGAP

Service Level Agreement (SLA)

Komitmen formal ketersediaan infrastruktur komputasi awan, target penanganan insiden operasional, dan jaminan waktu tanggap tiket resmi Kuril Dev Studio.

Status Kepatuhan: Efektif Per 18 November 2026 • Versi: 1.0 • Entitas: Kuril Dev Studio
01

Komitmen Ketersediaan Layanan (99.9% Uptime Commitment)

Sebagai entitas Venture Studio & Micro-SaaS Holding, Kuril Dev Studio berkomitmen menyediakan infrastruktur aplikasi awan yang andal, aman, dan berkinerja tinggi. Kami menetapkan target ketersediaan layanan produksi tahunan minimum sebesar 99.9% Uptime untuk seluruh lini produk mandiri aktif (termasuk ProduKu).

Target Produksi
99.9%

Operasional 24/7/365 dengan arsitektur failover Anycast edge global.

Topologi Jaringan
Anycast Edge

Distribusi 300+ Point of Presence global dengan isolasi fault lokal.

Pemulihan Bencana
RPO < 1 Jam

Pencadangan data berkala terenkripsi otomatis dan replikasi basis data hot-standby.

02

Jendela Pemeliharaan Terjadwal (Maintenance Windows)

Demi menjaga kepatuhan keamanan siber dan pembaruan patch sistem, pemeliharaan terjadwal diatur dengan standar berikut:

  • Pemberitahuan Dini: Setiap pemeliharaan terjadwal yang berpotensi menyebabkan interupsi layanan akan diumumkan minimal 24 jam sebelumnya melalui banner sistem atau pemberitahuan surel resmi.
  • Jam Pemeliharaan di Luar Jam Sibuk: Pemeliharaan terjadwal hanya dilaksanakan pada jendela waktu off-peak (pukul 01.00 – 04.00 WIB) guna meminimalkan dampak terhadap alur kerja pengguna.
  • Pemeliharaan Darurat: Untuk penambalan kerentanan siber kritis (*zero-day exploit*), tim teknis berhak mengeksekusi patch keamanan darurat dengan pemberitahuan sesegera mungkin.
03

Matriks Tingkat Keparahan Insiden & Waktu Tanggap

Setiap laporan insiden teknis diklasifikasikan ke dalam 4 tingkatan keparahan operasional dengan target respons terukur:

Severity 1 (Kritis / Critical) < 1 Jam

Layanan inti atau gateway transaksi pembayaran lumpuh total; tidak ada alternatif operasional.

Target Resolusi: < 4 Jam
Severity 2 (Tinggi / Major) < 4 Jam

Penurunan performa signifikan atau fitur penting terganggu, namun sistem inti masih merespon.

Target Resolusi: < 12 Jam
Severity 3 (Sedang / Minor) < 12 Jam

Kendala fungsionalitas non-esensial dengan ketersediaan alternatif kerja (*workaround*).

Target Resolusi: < 24 Jam
Severity 4 (Rendah / Inquiry) < 24 Jam kerja

Pertanyaan umum seputar penggunaan, bantuan konfigurasi akun, atau permohonan informasi.

Target Resolusi: 1 - 2 Hari kerja
04

Target Waktu Tanggap Kanal Departemen

Untuk memastikan korespondensi tepat sasaran, alur penanganan tiket komunikasi diatur dengan Service Level Agreement (SLA) spesifik:

Departemen Keamanan Siber (Security)
SLA Tanggap: < 12 Jam (Investigasi insiden & kerentanan prioritas tinggi).
Layanan Dukungan & Transaksi (Support)
SLA Tanggap: < 24 Jam (Verifikasi pembayaran, aktivasi fitur, kendala teknis).
Departemen Hukum & Privasi (Legal)
SLA Tanggap: 1 - 3 Hari Kerja (Kepatuhan UU PDP, hak data subjek, audit regulasi).
Kemitraan Korporat (Company)
SLA Tanggap: 1 Hari Kerja (Due diligence perbankan, kelembagaan B2B, audit PJP).
05

Kompensasi Kredit Layanan (Service Credit Policy)

Apabila dalam kurun waktu satu bulan kalender ketersediaan layanan produksi terbukti secara objektif turun di bawah ambang batas 99.0% akibat insiden internal sistemik Kuril Dev Studio, pelanggan berbayar aktif berhak mengajukan kompensasi berupa Kredit Perpanjangan Langganan pro-rata.

Klaim kompensasi wajib diajukan melalui email ke support@kuril.dev dalam waktu selambat-lambatnya 7 (tujuh) hari kalender setelah insiden dinyatakan selesai, dengan melampirkan log atau bukti terdampak.

06

Pengecualian Komitmen SLA (Exclusions)

Perhitungan komitmen uptime dan jaminan respon SLA tidak berlaku dalam kondisi:

  • Kejadian Keadaan Kahar (*Force Majeure*), termasuk bencana alam, perang, kebakaran, atau gangguan telekomunikasi nasional.
  • Gangguan transmisi pada jaringan internet publik internasional atau penyedia ISP lokal pengguna.
  • Tindakan ilegal, pelanggaran Ketentuan Layanan, atau eksploitasi API yang dilakukan oleh pengguna secara sepihak.
  • Jendela pemeliharaan terjadwal yang telah diumumkan sebelumnya sesuai prosedur resmi.
01

Service Availability Commitment (99.9% Uptime)

As an independent Venture Studio & Micro-SaaS Holding, Kuril Dev Studio is dedicated to delivering resilient, scalable, and high-performance cloud application infrastructure. We uphold an annual operational commitment of at least 99.9% Uptime across all active production software ventures (including ProduKu).

Production Target
99.9%

24/7/365 availability backed by automated global edge failover routing.

Network Topology
Anycast Edge

Distributed 300+ Point of Presence global infrastructure with local fault isolation.

Disaster Recovery
RPO < 1 Hour

Automated periodic encrypted database snapshots and hot replicas.

02

Scheduled Maintenance Windows

To maintain robust cybersecurity compliance and platform stability, routine maintenance follows strict operational guardrails:

  • Advance Advisory: Routine maintenance expected to impact service availability is announced at least 24 hours in advance via system status banners or official email bulletins.
  • Off-Peak Execution: Scheduled engineering windows are strictly conducted during off-peak hours (01:00 – 04:00 Western Indonesia Time / UTC+7) to minimize operational disruption.
  • Emergency Security Hotfixes: For critical zero-day vulnerabilities, the engineering team reserves the right to deploy emergency hotfixes immediately with prompt post-deployment disclosure.
03

Incident Severity & Response Latency Benchmarks

Technical incidents are categorized into 4 operational severity tiers with enforced initial triage and resolution targets:

Severity 1 (Critical) < 1 Hour

Core application failure or complete checkout transaction outage; zero operational workaround.

Target Resolution: < 4 Hours
Severity 2 (Major) < 4 Hours

Substantial degradation of key platform functionality; core systems operational with constraints.

Target Resolution: < 12 Hours
Severity 3 (Minor) < 12 Hours

Non-critical issues or minor UI/workflow anomalies with an available operational workaround.

Target Resolution: < 24 Hours
Severity 4 (Inquiry) < 24 Business hours

General inquiries, setup assistance, API integration questions, or feature feedback.

Target Resolution: 1 - 2 Business days
04

Departmental Response Latency Guarantees

To ensure queries reach designated teams with minimal overhead, support queues adhere to enforced response standards:

Cybersecurity & Disclosure
SLA Response: < 12 Hours (Coordinated vulnerability triage & threat alerts).
User Support & Disputes
SLA Response: < 24 Hours (Billing validation, access provisioning, technical bugs).
Legal Affairs & Privacy
SLA Response: 1 - 3 Business Days (Data subject rights, compliance audits).
Corporate Affairs & Liaison
SLA Response: 1 Business Day (Banking due diligence, B2B institutional relations).
05

Service Credit Compensation Policy

If production platform availability falls below the 99.0% threshold within a given calendar month due to verified internal outages, active paying customers qualify for pro-rated Service Credits applicable toward future billing cycles.

Credit claims must be submitted to support@kuril.dev within 7 calendar days following incident resolution, accompanied by verifiable impact timestamps.

06

Commitment Exclusions

Uptime targets and guaranteed response latencies do not apply under the following scenarios:

  • Force Majeure events, including natural disasters, acts of war, regional infrastructure failures, or national telecoms blackouts.
  • Network routing issues originating within public internet peering exchanges or end-user Internet Service Providers.
  • Unauthorized platform abuse, breach of the Terms of Service, or unapproved API rate flooding.
  • Pre-announced maintenance windows executed within official off-peak parameters.