Service Level Agreement
Response targets and support boundaries for DefenX maintenance and support plans.
Last updated: November 2026
1. Purpose
This document describes the support response targets associated with DefenX maintenance plans. It is a draft structure and must be matched to the signed plan before use. Response targets describe the time to acknowledge and begin work; they are not a guarantee of resolution time.
2. Support channels
Basic Maintenance support is provided by email with a response target within 24 hours. Business Maintenance includes priority support with a response target within 4 hours. Custom Support includes a tailored SLA with a 1-hour critical response target and a direct developer Slack channel where agreed.
3. Monitoring
Basic Maintenance includes uptime monitoring at a 15-minute interval. Business Maintenance includes real-time 24/7 uptime and SSL ping. Custom Support monitoring is defined in the custom agreement. Monitoring results are operational signals, not a public uptime certification.
4. Severity and prioritization
Incidents are prioritized by impact on the live service, the number of users affected and the availability of a workaround. A critical incident generally means the service is unavailable or a security issue requires immediate containment. Final severity definitions should be agreed in the signed SLA.
5. Exclusions
Response targets may be affected by outages at third-party providers, client-side network failures, missing access, unauthorized changes, force majeure events or issues outside the agreed maintenance scope.
6. Service credits
No service credits or financial penalties are promised on this website. Any credits, remedies or reporting obligations must be stated explicitly in the signed custom SLA.
7. Reporting
Maintenance work is logged. Reporting frequency and the format of health or patch summaries should be confirmed in the applicable plan or custom agreement.