Plan a monitoring budget

Use the budget planner to create a reviewable annual estimate. The portal’s Usage & budget page shows private and public accepted ingestion, estimated cost and account limits after the usage backend is deployed. It starts in observation mode. These measurements do not create invoices or charge a payment method.

Start with monthly private ingestion

The planner defaults to known private GB. To estimate from activity instead, select the modeled method and combine branches, servers, VDI and temporary capacity. Their default fleet sizes add up. Changing selections recalculates those totals; then edit them to fit your environment. Do not count one VM in multiple cohorts.

Modeled collection uses actual calendar month lengths. Online time is never billed. Workday schedules use your entered monthly average. A logged-out desktop can still be a reporting agent.

Make the telemetry assumption explicit

Use known monthly accepted GB when available. Otherwise review the monitoring profile’s checks, interval, records per execution and bytes per record. Profiles are illustrative, not measured production benchmarks. Account for additional host metrics, discovery, labels and artifacts.

Show finance a normal year and a busy year

Enter growth through December, the number of busy months and a usage uplift. The planner puts busy months at year-end and applies the uplift to modeled activity and data. Add a contingency reserve for procurement. This is a scenario, not a statistical confidence interval or an enforced cap.

Separate cost from cash timing

Annual billing pays the base upfront in January and bills overages monthly. Allowances reset monthly without rollover. The average monthly allocation is not the amount of every invoice. Review the 12-month breakdown and compare Team and Business against retention/support requirements as well as total cost.

Public ingestion (separately quoted), tax, FX, your infrastructure, model-provider charges and separately contracted capacity, retention and support are excluded. Confirm the final commercial scope before committing a budget.

Carry the assumptions into an enquiry

Download the CSV for procurement, or choose Review this budget / Book a demo with this budget. The planner stores a short brief in your browser session and adds it to an editable form. Nothing is sent until you submit that form. The handoff expires after 24 hours and does not include your portal inventory or credentials.

Measured usage and enforcement

The usage ledger uses UTC calendar months. Reporting requests reserve the current and following minute, with a maximum two-minute tail after the last successful request. Renewals do not count overlapping minutes twice. A lease is truncated at month-end. Offline historical samples do not reconstruct past runtime; uploading a backlog can renew a current reporting lease.

Accepted telemetry is measured as the deterministic protobuf encoding of normalized measurement labels, metrics, detail, fidelity, subject and target. Identity, server stamp and transport framing are excluded. One decimal GB is 1,000,000,000 bytes. The server records the acceptance and durable delivery intent in one PostgreSQL transaction. Retries with the same tenant and record ID do not add usage, including retries in later months.

The estimate includes the monthly base plus private and public ingestion beyond their separate allowances. Public bytes are not billed as private data. Public rates and allowances require provider provisioning; public execution time has no charge. Each additional usage line rounds to the nearest cent. This backend estimate uses monthly list prices; annual prepayment, tax and separately contracted services are not included.

A user with billing management permission can set the monthly budget, reporting concurrency limit, overage permission and ephemeral enrollment mode. Only the seeded Owner role has billing management by default. Changes are audited. Observation mode measures usage without enforcing financial or capacity limits. Identity conflicts are still refused.

With enforcement enabled, new telemetry is refused if it exceeds its source allowance or account budget. Private reporting leases are refused for capacity or identity conflicts, never for accumulated hours or exhausted ingestion budget. Public execution stops renewing at its ingestion allowance or account budget. Allowing overages permits additional usage only up to the budget. Already accepted data remains eligible for delivery. A lower budget takes effect immediately for subsequent admissions; previously accepted usage is not reversed.

Agents can continue local checks and use their bounded spool during a refusal. A long refusal can fill that spool and cause data loss. The limit does not promise to stop local checks. Limits reset with the UTC month; the account budget and policy remain in effect.

Budget events appear in the portal at 50%, 80% and 100%, including the monthly base, alongside reporting refusals and identity conflicts. These are in-app events, not email or webhook notifications. The meter begins when the backend is deployed; existing historical telemetry is not backfilled.

Updated launch catalog and shared public usage

Team is $299/month with 10 GB of private ingestion, then $6/GB. Business is $999/month with 50 GB, then $8/GB. Public terms are separately provisioned: $12/GB of telemetry plus $0.50/GB of recorded final HTTP response-body bytes, including partial bodies. There are no agent-hour fees.

Eligible shared cluster probes and coalesced HTTP, DNS, TCP and direct-echo reports split one physical measurement equally across distinct tenant accounts. Extra checks in one account do not multiply its share. Per-check metadata and destination-specific measurements remain dedicated. Allocated shared telemetry starts at $0.50 per decimal GB for Team and Business, configurable by the provider; this is a separate rate from public HTTP response-body traffic. Public response bytes from a shared report are also divided across its beneficiaries.

Shares remain provisional for 24 hours after the first accepted report. A new subscriber within that window reduces earlier accounts’ shares through credits booked to the original UTC day and month. New subscribers after settlement are refused; existing reference retries do not add usage. Private and public allowances remain separate, and each covers dedicated ingestion before shared ingestion. Monthly price snapshots stay fixed. Replication, indexes and backup copies do not multiply billable ingestion.

See usage and settlement for the portal breakdown. These development estimates do not activate invoicing or payment collection.