> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/license/readme.md).

# License

MaiAgent 私有雲與地端部署的版本政策、維運支援政策、部署環境需求，以及各季度版本的版本說明與升級說明。

本區（License）寫給採用 MaiAgent 私有雲或地端部署的 IT 主管、專案窗口與建置團隊。私有雲與地端採季度版本，每季發布一版，並提供版本說明與升級說明。

## 依需求找文件 <a href="#find-by-need" id="find-by-need"></a>

| 你想知道                         | 看這裡                                                                  |
| ---------------------------- | -------------------------------------------------------------------- |
| 多久發布一版、舊版支援多久                | [版本政策](/license/policies/version-policy.md)                          |
| 更新怎麼發布、問題怎麼分級與回報             | [維運支援政策](/license/policies/support-policy.md)                        |
| 部署前環境要符合哪些條件                 | [部署環境需求](/license/deployment/requirements.md)                        |
| 2026 Q3 的版號、驗證範圍、需開通或另行部署的功能 | [2026 Q3 版本說明](/license/id-2026-q3/release-notes.md)                 |
| 從 2026 Q2 升級會改變什麼            | [從 2026 Q2 升級到 2026 Q3](/license/id-2026-q3/upgrade-from-2026-q2.md) |

主機規格、部署型態與功能對照等技術細節，見[技術人員手冊](https://docs.maiagent.ai/tech/platform-development/system-requirements)。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maiagent.ai/license/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
