> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zenmeter-docs/zenmeter-and-monetization/zenmeter-quick-overview.md). # Zenmeter Quick Overview Learn how Zenmeter's lightweight, subscription-based system manages usage and limits, deducting and logging usage in real time against each customer's single subscription of features, add-ons, users, **Zenmeter has been designed to be lightweight, fast to deploy and set up, and easy to connect to billing systems like Stripe.** Zenmeter is a subscription-based system for managing usage and limits. It’s designed for products where: * A customer has one main subscription * They can buy add-ons on top * They can have multiple users * They consume usage-based features over time ### Zenmeter is built around subscriptions > Everything runs inside a single subscription. That subscription is the source of truth for: * Users * Features * Add-ons * Usage balances Product owners set up products, pricing, and usage rules in a configuration step. At runtime, each customer has one main subscription that controls everything. #### That subscription: * Holds the features the customer can use * Includes any add-ons they’ve purchased * Tracks users on the account * Manages usage balances (like credits or limits) #### When a feature is used: * Zenmeter looks up the correct meter and rate * Deducts usage from the right balance * Logs the action for audit and reporting Add-ons don’t create a separate system—they simply extend the main subscription. --- # 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.nalpeiron.com/zenmeter-docs/zenmeter-and-monetization/zenmeter-quick-overview.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.