← Back to HexTyx

Service Level Agreement

Effective: July 28, 2026  ·  FAVZ Group  ·  Wyoming, USA

Last Updated: July 28, 2026 Applies to: Pro and Enterprise plan subscribers

1. Overview

This Service Level Agreement ("SLA") describes AIZA's commitments regarding platform availability, performance, incident response, and the remedies available to subscribers when those commitments are not met.

Free plan users are not covered by this SLA but benefit from the same infrastructure on a best-efforts basis.


2. Availability Commitments

2.1 Uptime Targets

Plan Monthly Uptime Target Downtime Allowance/Month
Pro 99.5% ~3.6 hours
Enterprise 99.9% ~43 minutes

2.2 Definition of Uptime

"Uptime" means the Service is accessible and scan submissions are being processed. Uptime is measured monthly, excluding scheduled maintenance windows.

2.3 What Is Not Counted as Downtime

The following are excluded from downtime calculations: - Scheduled maintenance (with advance notice per Section 5) - Downtime caused by factors outside AIZA's control (see Section 9) - Scan failures caused by the target AI endpoint being unavailable or unresponsive - Degraded performance of a target AI system under test - Free plan interruptions - Beta features explicitly marked as experimental

2.4 How We Measure

Uptime is measured from AIZA's infrastructure monitoring. Status history is published at status.hextyx.com.


3. Performance Standards

3.1 API Response Times

Endpoint Target Response Time (p95)
GET /health < 200ms
POST /scans (submission) < 2 seconds
GET /scans/{id} (status poll) < 500ms
GET /scans/{id}/results < 3 seconds
GET /scans/{id}/report/{format} < 5 seconds

These targets apply under normal load conditions. Performance during peak usage or unusually large scan result sets may vary.

3.2 Scan Processing

AIZA does not guarantee scan completion times. Scan duration depends on the number of phases enabled, the target endpoint's response speed, and rate limit delays configured by the user. Typical scan durations range from 5 minutes to 2 hours.


4. Incident Response Times

4.1 Severity Classification

Severity Definition Examples
P1 — Critical Full service outage; no scans can be submitted or processed Platform completely unreachable; authentication failure affecting all users
P2 — High Significant degradation affecting core functionality Scan submissions failing for >25% of users; report downloads failing
P3 — Medium Partial degradation; workarounds available Specific report format unavailable; slow scan processing
P4 — Low Minor issue; minimal user impact UI cosmetic issues; non-critical feature unavailable

4.2 Response Time Commitments

Severity Initial Response Status Update Frequency Target Resolution
P1 — Critical 30 minutes Every 30 minutes 4 hours
P2 — High 2 hours Every 2 hours 24 hours
P3 — Medium 1 business day Every business day 5 business days
P4 — Low 3 business days Weekly Next release cycle

Response times run from the time AIZA becomes aware of the incident, either through our monitoring or through a support ticket submitted by a subscriber.

Enterprise subscribers receive dedicated incident response via a named account contact. Contact details provided at account activation.


5. Scheduled Maintenance

5.1 Notice Requirements

Plan Advance Notice
Pro 48 hours
Enterprise 5 business days

5.2 Maintenance Windows

Scheduled maintenance is performed during low-traffic windows, typically: - Preferred window: Sunday 02:00–06:00 UTC - Duration: Typically 1–2 hours; maximum 4 hours per window

5.3 Emergency Maintenance

In cases of critical security patches or infrastructure failures, AIZA may perform emergency maintenance with less notice. We will communicate via status.hextyx.com and email as promptly as possible.


6. SLA Credits

If AIZA fails to meet the uptime commitment in Section 2.1 in a given calendar month, affected subscribers are eligible for service credits as follows:

6.1 Credit Schedule

Monthly Uptime Achieved Credit as % of Monthly Fee
99.0% – below target 10%
95.0% – 98.99% 25%
90.0% – 94.99% 50%
Below 90.0% 100%

6.2 How to Claim Credits

Submit a credit request to billing@hextyx.com within thirty (30) days of the end of the affected month. Include: - Your account email - The affected dates and times - Reference to our status page entries if available

Credits are applied to future invoices. Credits are non-transferable and have no cash value.

6.3 Maximum Credit

Total credits in any calendar month shall not exceed 100% of that month's subscription fee. Credits are the sole and exclusive remedy for SLA breaches.

6.4 Credit Exclusions

Credits are not available where: - Downtime resulted from your actions or configuration - Your account has unpaid invoices - The claim is submitted outside the 30-day window - Downtime occurred during a free trial period


7. Support

7.1 Support Channels

Plan Channel Hours
Free Community forum, docs Self-service only
Pro Email support Business days, 09:00–18:00 UTC
Enterprise Email + dedicated Slack channel 24/5 (weekdays)

7.2 Support Response Times (Non-Incident)

Plan Initial Response
Pro 1 business day
Enterprise 4 business hours

7.3 Out of Scope

Support does not include: - Security consulting or interpretation of scan results - Advice on how to remediate specific vulnerabilities - Custom scan development - Integration development

These services are available as professional services engagements — contact sales@hextyx.com.


8. Data Backup and Recovery

8.1 Backup Schedule

8.2 Recovery Time Objective (RTO)

Scenario Pro Enterprise
Full platform restoration 4 hours 2 hours
Database restoration from backup 8 hours 4 hours
Single account data recovery 3 business days 1 business day

8.3 Recovery Point Objective (RPO)

In the event of data loss requiring backup restoration, the maximum data loss is: - Pro: Up to 24 hours of data - Enterprise: Up to 1 hour of data (point-in-time recovery)


9. Exclusions — Force Majeure

AIZA's SLA commitments do not apply to unavailability caused by:


10. Status Page and Incident Communication

Current status and historical incident records are available at:

status.hextyx.com

All users can subscribe to status page notifications by email or webhook. Enterprise subscribers receive direct notification for P1 and P2 incidents affecting their account.


11. SLA Review

This SLA is reviewed annually. AIZA reserves the right to update uptime targets, response times, and credit schedules with thirty (30) days advance notice to subscribers. Updates will not reduce commitments during an active annual subscription term without the subscriber's consent.


12. Contact

Support: support@hextyx.com Billing / Credits: billing@hextyx.com Enterprise Account: Your named account manager or enterprise@hextyx.com