> For the complete documentation index, see [llms.txt](https://docs.saas.haut.ai/haut.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saas.haut.ai/haut.ai/legal/service-license-agreement-sla-and-maintenance.md).

# Service License Agreement (SLA) and Maintenance

This page collects an upper level information covering maintenance-related questions about Haut.AI Services

## **What are Haut.AI's critical SLAs?**

Specific SLAs may vary by contract. We generally commit to high service availability, rapid response times for critical issues, and regular system updates.

For precise SLA details, please refer to your specific agreement or contact your account manager.

***

## **How does Haut.AI handle critical issues?**

We prioritize critical issues such as:

* SaaS API downtime (described in [SaaS API Overview](/haut.ai/developers/saas-api-overview.md)),
* LIQA downtime (described in [LIQA](/haut.ai/haut.ai-features/liqa.md))

Our team is equipped to respond promptly to ensure minimal disruption to your services. If you encounter any of the aforementioned problems, please reach out to Haut.AI **immediately**.

***

## **How often does Haut.AI update its algorithms and features?**

We continuously improve our algorithms and add new features. We roll out updates regularly and ensure that they do not disrupt existing integrations. There is no official schedule for releases, but they normally happen 1-2 times per month.

***

## When does Haut.AI inform you about the scheduled maintenance?

Scheduled Maintenance means Haut.AI's scheduled routine maintenance of the services.

* Haut.AI notifies clients at least one week (seven days) in advance about the incoming Scheduled Maintenance.
* Haut.AI typically performs Scheduled Maintenance once per month.

***

## When does Haut.AI inform you about the breaking changes?

Breaking Changes means irreversible changes to Haut.AI services that remove or significantly alter the already existing API methods covered in [SaaS API Overview](/haut.ai/developers/saas-api-overview.md).

* Haut.AI notifies clients at least one month (30 calendar days) in advance about the incoming Breaking Changes.

***

{% hint style="warning" %}
Not a Haut.AI client yet?
{% endhint %}

<a href="https://haut.ai/book-a-demo?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button primary" data-icon="user-vneck">Book a demo</a> <a href="https://haut.ai/product/ai-skin-analysis?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button secondary" data-icon="external-link">Platform overview on haut.ai</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.saas.haut.ai/haut.ai/legal/service-license-agreement-sla-and-maintenance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.