> For the complete documentation index, see [llms.txt](https://docs.simptel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simptel.com/tf-platform/administration/organizations/billing.md). # Billing This article provides an overview of topics and tasks related to managing your TF Platform Billing accounts. We provide subscriptions through the **Microsoft Azure Marketplace** and **Google Cloud Marketplace**.\ Our model combines **metered billing** with subscription commitments, ensuring flexibility and predictable coverage. *** ### Billing Models #### 1. Metered Billing * Pay for actual usage (e.g., Monthly Active Users, token operations, data transfer, storage). * Consumption is tracked per project and invoiced through your marketplace account. #### 2. Fixed Subscriptions * Choose **monthly** or **annual** subscriptions. * Pricing includes **service-level agreements (SLAs)** for guaranteed performance and support. * Annual subscriptions are discounted compared to monthly. *** ### Key Notes * Subscriptions include already purchased usage and SLA terms. * All invoicing and payments are handled through your chosen marketplace (Azure or Google). *** ### Next Steps For detailed pricing, plan comparisons, or to activate a subscription, please contact our **Sales team**. --- # 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.simptel.com/tf-platform/administration/organizations/billing.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.