> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/readme/quanto-custa-o-power-monitor.md).
# How much does Power Monitor cost?
Understand how the Power Monitor monthly fee is calculated: tiers by number of monitored items, daily average of the cycle, onboarding fee, and 30-day free trial period.
Power Monitor is billed monthly, and the price is **set automatically by the number of items (artifacts) monitored** in your tenant. There is no plan to choose: the more items monitored, the higher the monthly fee tier.
{% hint style="success" %}
You start with a **30-day free trial period**, with no credit card required. See [How does the 30-day trial work?](/en/perguntas-frequentes/licenciamento/como-funciona-o-trial-de-30-dias.md)
{% endhint %}
***
## Monthly fee tiers
Standard table, in Brazilian reais (BRL):
| Monitored items tier | Monthly fee |
| --------------------- | ----------- |
| Up to 100 items | R$ 99,90 |
| 101 – 200 items | R$ 199,90 |
| 201 – 500 items | R$ 259,90 |
| 501 – 1,000 items | R$ 359,90 |
| 1,001 – 2,000 items | R$ 459,90 |
| 2,001 – 5,000 items | R$ 699,99 |
| 5,001 – 10,000 items | R$ 899,90 |
| 10,001 – 20,000 items | R$ 1.499,00 |
| Over 20,000 items | R$ 1.999,00 |
{% hint style="info" %}
**The tier that applies to your organization is always the one shown in Power Monitor itself**, in **Billing** (administrator access). Specific commercial terms, organizations outside Brazil, and other currencies may have their own table. The first tier is the minimum price: even if the number of monitored items is zero, the monthly fee of the lowest tier is still charged.
{% endhint %}
***
## What counts as an item?
An **item** (or artifact) is any of the 34 Power BI and Microsoft Fabric content types that Power Monitor inventories inside workspaces: reports (including paginated), semantic models, dashboards, dataflows, notebooks, data pipelines, lakehouses, warehouses, mirrored databases, eventstreams, eventhouses, KQL databases, and other Fabric items.
Two important rules:
* **Only items from monitored workspaces count.** Workspaces you left out of monitoring are not included.
* **Workspaces, capacities, gateways, connections, and users do not count as items.** They are monitored, but they are not included in the billing base.
The full list is in [What counts as an artifact for pricing purposes?](/en/perguntas-frequentes/licenciamento/o-que-e-contado-como-artefato.md)
***
## How the billed quantity is determined: daily average
Power Monitor records the number of monitored items **once a day**. At month-end closing, the quantity used to determine the tier is the **arithmetic mean of the days measured in the cycle, rounded down**. In other words: an isolated peak does not determine your invoice.
**Example:** if on four measured days the tenant had 100, 100, 100, and 501 items, the average is (100 + 100 + 100 + 501) ÷ 4 = 200.25, rounded down to **200 items**. The billed tier is **101 – 200 items**, not the tier of the day with the highest volume (501).
Calculation rules:
* **Days in the trial period** are recorded, but they **are not included** in the average.
* A day without measurement does not count as zero: it is simply left out of the calculation.
* Items **deleted in the tenant** stop being counted starting on the day Power Monitor detects the deletion (days already measured are not recalculated).
* The calculation is done on the **month already closed**: a month's invoice is generated at the beginning of the following month.
In **Billing**, the administrator follows the tiers, the current tier, the visual explanation of how the average was calculated, and the day-by-day audit of the count (with the list of items counted on each day).
{% hint style="warning" %}
**Pay attention to the monitoring scope.** By default, workspaces discovered in new scans are added **outside** monitoring and do not increase the invoice until someone monitors them. If an administrator turns off the monitored workspace selection (starting to monitor all of them), **all workspaces start counting immediately**, which may change the month's tier. Learn more in [Workspaces](/en/power-monitor/governanca/workspaces.md).
{% endhint %}
***
## First month and trial period
* The trial period lasts **30 days** and does not generate charges.
* At the end of the trial, the subscription is **activated automatically** (you agree to this during installation). If you do not want to continue, request cancellation **before** the end of the period. See [Can I cancel Power Monitor?](/en/perguntas-frequentes/duvidas-gerais/posso-cancelar-o-power-monitor.md)
* The first monthly fee is **prorated** for the days of use between the end of the trial and the end of that month.
***
## Onboarding fee (setup)
In addition to the monthly fee, a **one-time onboarding fee** may be due, covering the initial configuration and the activation of the organization:
* The current price is provided by Power Tuning and can be checked on the platform.
* It becomes due when the organization becomes a paying customer (end of the trial period).
* It can be paid in **1, 2, or 3 installments**, charged together with the monthly fees. The installment plan is chosen in **Billing** and can only be changed **until the end of the trial period**.
* It can be waived, fully or partially, under a commercial condition agreed with Power Tuning.
***
## Due date and payment methods
* **Due date:** defined by the administrator during installation (the recurrence rule and, depending on it, a day of the month between 1 and 28 or a number of days) and adjustable later in **Billing**.
* **Payment methods:** boleto (Brazilian bank slip) or PIX, through the payment link of each invoice.
* Invoices, installments, and payment links are available in **Billing**.
***
## Managed Monitoring (additional service)
In addition to the platform, Power Tuning offers **Managed Monitoring**, in which our team of specialists acts on the critical alerts of your environment 24/7. Power Monitor is already included in the plans of this service. See the [Managed Monitoring plans](/en/managed-monitoring/monitoramento-gerenciado/planos.md).
***
## Frequently asked questions
Items I did not want were added. Will I be charged for them?
Only if they are in monitored workspaces, and only by the month's average. A high volume on a few days has a proportional weight in the average. If the items should not be monitored, remove the workspace from monitoring (or delete the items in the tenant): from then on they stop being counted in the next daily measurements.
Will I be notified when I change tiers?
There is no need to "upgrade": the tier is adjusted automatically by the month's average. In **Billing** you can see how many more items you can monitor before moving to the next tier.
Is there a discount for an annual contract or a custom condition?
Specific commercial terms can be negotiated with our team. [Contact us on WhatsApp](https://powermonitor.com.br/whatsapp).
## Related pages
* [What counts as an artifact for pricing purposes?](/en/perguntas-frequentes/licenciamento/o-que-e-contado-como-artefato.md)
* [How does the 30-day trial work?](/en/perguntas-frequentes/licenciamento/como-funciona-o-trial-de-30-dias.md)
* [Billing](/en/power-monitor/faturamento.md)
* [How do I install Power Monitor?](/en/readme/como-instalar-o-power-monitor.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.powermonitor.com.br/en/readme/quanto-custa-o-power-monitor.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.