Service Level Agreement

Effective June 17, 2026 7 min read

1. Overview & Scope

This Service Level Agreement ("SLA") describes the availability commitment and support response targets for the Strata service and forms part of the agreement between Kronisys Inc. ("Kronisys") and the customer organization identified in the applicable Order Form ("Customer"), consisting of our Terms of Service and any executed Order Form or enterprise agreement (the "Agreement").

This SLA applies to the production Strata service for customers on an active, paid enterprise subscription, and only while the Agreement is in effect and Customer is not in material breach (including non-payment). It is the express availability commitment referenced in, and a negotiated exception to, the "as available" provision and warranty disclaimer of the Terms of Service.

Capitalized terms not defined here have the meaning given in the Terms of Service. Where this SLA and the Terms of Service conflict, the Terms of Service control except as to the specific availability commitment and service-credit remedy set out below.

2. Definitions

  • "Core Service" means user authentication and the AI chat experience of the production Strata service. Capabilities that depend on Customer-connected extensions or third-party providers are addressed in Section 6.
  • "Monthly Uptime Percentage" means ((Total Minutes in Month − Downtime Minutes) ÷ Total Minutes in Month) × 100, calculated per calendar month.
  • "Downtime" means a period during which the Core Service is unavailable to Customer, as measured by Kronisys's monitoring, excluding any time attributable to an Exclusion under Section 6.
  • "Scheduled Maintenance" means maintenance for which Kronisys provides advance notice under Section 5.
  • "Service Credit" means the credit calculated under Section 7, issued as Customer's sole and exclusive remedy for a failure to meet the Uptime Commitment.

3. Uptime Commitment

Kronisys will use commercially reasonable efforts to make the Core Service available with a Monthly Uptime Percentage of at least 99.9%, measured per calendar month.

A 99.9% commitment corresponds to approximately the following maximum monthly Downtime:

Monthly Uptime PercentageApprox. allowed Downtime (30-day month)
99.9% (committed)~43 minutes 12 seconds
99.95%~21 minutes 36 seconds
99.99%~4 minutes 19 seconds

4. Measurement & Reporting

Uptime is measured by Kronisys's monitoring and telemetry at the service edge. Downtime is measured in whole minutes; partial minutes round in Customer's favor. Customer may request a Monthly Uptime report for any month in which it believes the Uptime Commitment was not met, and Kronisys's monitoring records are the authoritative source for determining Downtime.

5. Scheduled Maintenance

Kronisys may perform Scheduled Maintenance during defined maintenance windows. Time during Scheduled Maintenance does not count as Downtime.

  • Standard window. Sundays, 02:00–06:00 UTC.
  • Notice. Kronisys will provide at least 48 hours' advance notice of Scheduled Maintenance expected to cause unavailability of the Core Service.
  • Emergency maintenance. Maintenance to address a security vulnerability or imminent threat may be performed with shorter or no notice; Kronisys will notify Customer as soon as reasonably practicable. Emergency maintenance does not count as Downtime.

6. Exclusions

Downtime does not include, and the Uptime Commitment does not apply to, unavailability caused by:

  • Scheduled Maintenance or emergency maintenance under Section 5;
  • third-party providers and sub-processors outside Kronisys's reasonable control, including Microsoft Azure platform incidents, Microsoft Foundry or AI model-provider outages or rate limiting, and Microsoft 365 / Microsoft Graph (Outlook, OneDrive, SharePoint, Teams) availability;
  • Customer-connected resources, such as a Customer SQL Server database that is offline, paused, throttled, or unreachable, or Customer network, firewall, or VPN issues;
  • Customer's own configuration or use not in accordance with the documentation, including suspended organizations, exceeded usage or rate limits, or use that violates the Usage Policy;
  • force majeure events;
  • beta, preview, or evaluation features identified as such; and
  • Customer's equipment, software, or local connectivity.

7. Service Credits

If Kronisys fails to meet the Uptime Commitment in a given calendar month, Customer may request a Service Credit calculated as a percentage of the monthly fees for the affected Service for that month:

Monthly Uptime PercentageService Credit (% of monthly fee)
At or above 99.9%0% (commitment met)
Below 99.9% and at or above 99.0%10%
Below 99.0% and at or above 95.0%25%
Below 95.0%50%
  • How to claim. Customer must submit a credit request to legal@kronisys.com within 30 days of the end of the month in which the failure occurred, including the dates and times of unavailability and any supporting records.
  • Maximum. Total Service Credits in any single month will not exceed 50% of that month's fees for the affected Service.
  • Form. Service Credits are applied against future invoices, are non-refundable, and have no cash value.

Sole remedy. Service Credits are Customer's sole and exclusive remedy for any failure by Kronisys to meet the Uptime Commitment. Service Credits count toward, and do not increase, the aggregate liability cap in the Terms of Service.

8. Support & Response Targets

Kronisys provides support by email and through the in-app support assistant during business hours (Monday–Friday, Eastern Time), with on-call coverage for Severity 1 issues. The targets below are initial response targets, not resolution guarantees. Severity is assigned by Kronisys in good faith based on impact, in consultation with Customer.

SeverityDescriptionTarget initial response
Sev-1 — CriticalCore Service down or unusable for all or most users, with no workaround1 hour
Sev-2 — HighMajor functionality impaired; significant business impact; limited workaround4 business hours
Sev-3 — MediumMinor functionality issue; moderate impact; reasonable workaround exists1 business day
Sev-4 — LowQuestion, cosmetic issue, or feature request; minimal impact2 business days

Kronisys will use commercially reasonable efforts to work toward resolution of higher-severity issues with appropriate urgency. Security vulnerability reports follow the timelines in the Security & Responsible Disclosure Policy.

9. General

This SLA applies only to the production Service and only while the Agreement is in effect and Customer is current on payment and not in material breach. It does not apply to free, trial, beta, preview, or evaluation use. This SLA is subject to the limitations of liability and other terms of the Terms of Service, which control in the event of any conflict except as to the specific availability commitment and Service-Credit remedy stated here. Kronisys may update this SLA on at least 30 days' notice for changes that take effect at the start of a renewal term, consistent with the Terms of Service.

10. Contact Information

Questions about this SLA, or to submit a Service Credit request, can be sent to: