> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/platform/control-panel/billing/contract-terms.md). # Contract terms ### Cloud services Billing follows a pay-as-you-go model with no fixed contract period by default, a minimum commitment of just one hour, and you only pay for the capacity you use. ### Monthly billed (binding) services The following services are billed monthly and may include a binding contract period: * Dedicated servers * Internet connectivity * Colocation Unless otherwise agreed, these services renew monthly with a one-month binding period. Any different contract term will be clearly specified in the quotation or agreement before signing. For complete details on all terms and conditions, please refer to our [general terms & conditions](https://glesys.com/terms-policies/general-terms-and-conditions). --- # 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.glesys.com/platform/control-panel/billing/contract-terms.md?ask=&goal= ``` `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.