> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/faq/ocdr.md). # Does Archera Support On Capacity Demand Reservations (OCDR)? ## OCDR Support No, Archera does not currently support managing or provisioning On Capacity Demand Reservations (OCDR) in Azure, AWS or Google Cloud, and has no plans to support them in the future. Handling these resources falls outside Archera's core competency of cloud commitments and providing an insurance guarantee on top of those particular commitments as our customers choose. For example with GPU workloads, see [How do Guaranteed Commitments Work for Instances with Low Capacity like GPUs](/help-center/guaranteed-commitments/low-capacity-instances.md). ## Managing OCDR Customers can manage their own OCDR through their respective cloud platform portals (Azure, AWS, etc.) ## Related Resources * [How do Guaranteed Commitments Work for Instances with Low Capacity like GPUs](/help-center/guaranteed-commitments/low-capacity-instances.md) * [How Does Commitment Discount Attribution Work in Archera?](/help-center/billing/discount-attribution.md) * [Could Archera Change or Impact My Application?](/help-center/faq/could-impact-application.md) --- # 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.archera.ai/help-center/faq/ocdr.md?ask=&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.