> For the complete documentation index, see [llms.txt](https://docs.elite.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elite.cloud/faq/pricing-partnership.md).

# 計費模式與合約

本頁解答費用與合作模式相關問題：為什麼勤英科技能提供更具競爭力的雲端價格與折扣、既有 RI / Savings Plans 是否仍有節費空間，協助您快速做出採購與導入決策。

<details>

<summary>為什麼勤英可以幫助您節費？</summary>

1. **規模折扣 :** 我們的規模越大，價格上就越有談判空間，單一帳號也有機會拿到更好的條件。
2. **RI / Savings Plans 規劃與重配 :** 很多企業其實「有買」，但常見狀況是：覆蓋率不足、錯估週期、到期沒補、或使用狀況改變等而造成浪費。我們會先檢查覆蓋率與到期狀況，再給您重配/補強建議。

了解更多：[為什麼勤英給您的價格更有優勢？](/product-overview/why-elitecloud-is-cheaper.md)

</details>

<details>

<summary>若帳號已持有生效中的 RI 或 Savings Plans，是否仍具節費空間？</summary>

可以，而且常常還有空間。

原因是企業使用情況會變，但 RI/SP 不一定可以調整。報告會優先檢查：

* **覆蓋率**：是否其實覆蓋不到你主要的用量
* **到期時間**：是否快到期或已產生折扣空窗
* **組合是否匹配**：週期/付款方式/承諾是否符合您現在的使用情況

了解更多：[為什麼勤英給您的價格更有優勢？](/product-overview/why-elitecloud-is-cheaper.md)

</details>


---

# 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.elite.cloud/faq/pricing-partnership.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.