Commercial Plan Billing Logic¶

The TrueWatch Commercial Plan uses a pay-as-you-go model, with the workspace as the billing unit. The billing cycle is calculated by day: at midnight each day, data from the previous calendar day is settled, and the bill is synced to the Billing Center.

Settlement Process¶

1. Calculate the data volume generated by each service in the workspace separately;
2. Generate billing details based on the measured traffic;

3. Sync the billing data to the Billing Center and deduct payment according to the selected settlement method.

   • Direct settlement through the Billing Center (top-up, Prepaid Card)
   • Settlement via cloud provider deduction (Huawei Cloud, Alibaba Cloud, AWS, Microsoft Azure, etc.)

Concepts¶

Billing Items¶

Metrics Billing Method¶

Metrics are billed by data points by default, and billing by time series is also supported.

Data Points¶

Counts all reported data points of all metrics within the storage retention period (per 10 million data points).

Time Series¶

Counts the number of tag combinations for each metric among the metric data reported through DataKit on that day (per 1,000/day).

For more details, see Time Series Logic Explained.

Logs¶

Billing methods are provided based on feature usage and storage mode.

Standard Storage¶

By default, billing is metered by the number of log data entries. If you need to use the billing by ingested volume model, contact your Account Manager.

Billing by Number of Data Entries¶

Counts the number of newly reported data entries per day, including data generated by logs, events, and other features (per 1 million data entries/day).

Billing by Ingested Volume¶

Counts the log ingestion traffic reported by users, billed by data volume before compression (per GB/day).

Long-term Storage¶

Long-term log storage is billed by the amount of log data stored beyond the standard storage duration (per GB/day). The scope covers all log data within the total long-term storage period that exceeds the standard storage period; data within the standard storage period is not billed again.

Index Advanced Matching¶

After enabling "Advanced Matching" for a log index, the system matches and processes log data through the central Pipeline according to the configured conditions.

In addition to the charges for the logs themselves, Advanced Matching is billed by the actual amount of data processed by the central Pipeline (per GB/day). For specific billing rules, see Central Pipeline.

Tracing¶

The billing scope for tracing includes Application Performance Monitoring (APM) and Agent monitoring data. Traces from Agent monitoring are counted with deduplication by trace_id, and Spans are counted by the number of newly added entries per day.

The system intelligently selects the billing method based on actual usage:

• If Trace count ≥ Span count/10, billing is based on Trace count;
• Otherwise, billing is based on Span count.

Application Profiling¶

Counts the number of reported application profiling data entries (per 10,000 entries/day).

RUM PV¶

Counts the number of page views reported from user visits (per 10,000 PV/day).

Session Replay¶

Counts the number of session_id values with has_replay: true (per 1,000 Sessions/day).

Network¶

Counts the number of host values in the network data reported by eBPF in the workspace (per host reporting network data/day).

Synthetic Monitoring¶

Synthetic Monitoring has two billing items: "Test Execution Count" billing and "Synthetic Test Data Storage" billing.

Test Execution Count:

When a synthetic test task is enabled and test results are returned through the test nodes provided by TrueWatch, the number of newly added synthetic test data entries in each hour is counted at hourly intervals (per 10,000 API Tests/day).

Each Browser Test execution counts as 10 executions, and each execution of other test types counts as 1 execution.

When self-hosted test nodes are used, the billable count is calculated at 1/10 of that for public test nodes, i.e., each Browser Test execution is billed as 1 execution, and each execution of other test types is billed as 0.1 executions.

Synthetic Test Data Storage:

Counts the number of newly reported synthetic test data entries per day (per 1 million entries/day).

Data Observability¶

Counts the number of valid job runs (Runs) added each day, billed per 1,000 Runs/day.

The same run is billed only once; multiple status reports during a run do not increase the billable count.

The unit price varies with the selected data storage duration, supporting 3 / 7 / 14 / 30 / 60 / 90 days. See Commercial Plan Billing Price Details for specific prices, and Data Storage Policy for how to configure the storage duration.

Triggers¶

Counts the total number of scheduled task executions per day based on Monitors, AI Monitors, Smart Monitoring, SLOs, Generate Metrics, and more, plus the execution calls of official advanced functions and the total number of DataKit or OpenAPI query calls (per 10,000/day).

Calculation Examples¶

1. Standard case: executing 1 "change detection" → 5 Triggers

2. Detection interval exceeded: executing 1 "outlier detection" with a 30-minute detection interval → base 5 + excess portion (30-15=15 minutes, 15/15=1) → Total: 6

3. Multiple detections with interval exceeded: executing 2 "range detections" with a 60-minute detection interval → base 2×5=10 + excess portion (60-15=45 minutes, 45/15=3) → Total: 13

Data Forwarding¶

There are two types of billing based on the data forwarding archive type.

Sensitive Data Scanning Traffic¶

Counts the raw traffic size of sensitive data scanned based on scanning rules (per GB/day).

For example, if log data entry A needs to be scanned and all three fields within the entry require masking rule processing, the system bills the masking scans for the three fields separately.

Security Detection Scanning Traffic¶

Counts the size of data actually scanned by security detection rules each day (compressed) (per GB/day).

Error Count¶

Counts the number of newly added associated error data entries per day, including error data reported to Error Tracking (per 1,000 data entries/day).

Scheduled Reports¶

The number of times scheduled reports are sent per day in the workspace (per send/day).

Central Pipeline¶

Counts the volume of log data actually processed by the Central Pipeline each day (per GB/day).

SMS¶

Counts the number of SMS messages sent that day (per 10 messages/day).

Phone Calls¶

Counts the metered times of phone notifications per day (per count/day). Metered times and actual dialed times are counted separately; a single call may correspond to multiple metered times. The actual billable usage and amount are subject to the current bill.

The phone broadcast language is determined by the Workspace Language. Metered times are calculated based on the complete broadcast content after truncation:

Metered times = number of characters in the complete broadcast text ÷ billing unit of the corresponding broadcast language, rounded up. If the same text is played repeatedly within a single call, the character count is calculated as one text.

For example, a Chinese broadcast of 100 characters counts as 1, and 101 characters counts as 2; an English broadcast of 300 characters counts as 1, and 301 characters counts as 2.

You can control the content length in Phone Broadcast Character Limit. When the rule of 1 count per 300 characters applies, setting the broadcast limit to 600 characters means each call is expected to be metered at most 2 times; actual metered times are calculated based on the final broadcast length.

TOBY AI¶

TOBY AI Service Subscription¶

Counts the plan tier and subscription fee of the TOBY AI service in the workspace.

Billing cycle: The activation date is used as the base date of the subscription cycle, and renewal occurs automatically on the same date each month. If that date does not exist in the current month, renewal occurs on the last day of that month, without changing the original cycle base date for subsequent months. For example: if activated on January 31, renewal in February occurs on February 28/29, and renewal in March still occurs on March 31.

Plan Upgrade

Owners of SaaS Commercial Plan or Enterprise Plan workspaces can self-service activate or upgrade to the Pro or Team plans under Management > TOBY AI without manual review. Once the Billing Center balance is sufficient and the charge succeeds, the plan entitlements take effect. If a paid plan is upgraded within its current effective cycle, the expiration date remains unchanged, and the plan credit difference is granted pro rata for the remaining time of the cycle. The actual deduction amount is subject to the final settlement in the Billing Center. For cases that do not support self-service or Enterprise custom plans, contact your Account Manager.

Downgrades and cancellation of renewal take effect after the current subscription cycle ends; pending operations can be revoked before they take effect. For the operation entry and how to handle excess Agents, see Manage Plans.

Complimentary Credits

Activation, Upgrade, and Renewal Examples¶

Assume the current workspace's Pro and Team complimentary credits per cycle are 40,000 and 120,000 Credits, respectively:

• First activation of Pro: after the charge succeeds, a new subscription cycle begins and 40,000 Credits are granted.
• Upgrade to Team within a cycle: if exactly half of the current cycle remains, the credits granted are (120,000 - 40,000) × 1/2 = 40,000 Credits, and the expiration date of the current cycle remains unchanged.
• Team renewal: after a successful renewal, 120,000 Credits are granted for the new cycle, and unused plan credits from the previous cycle are not carried over.

This example only illustrates the granting of plan credits and does not represent the amount payable for the upgrade. The actual credit allowance is subject to the current workspace plan information, and the fee is subject to the settlement result in the Billing Center.

By Credits¶

Counts the total Credits consumed on that day by TOBY AI Agents, TOBY AI TruePilot, AI Monitors, and AI Smart Monitoring (per 10 Credits/day).

AI Monitor credit consumption: each time a detection is executed, Credits are deducted based on the actual consumption of that detection. The configured "credit budget per detection" is used to control the credit consumption of a single detection and does not mean that this amount is deducted each time; each detection is additionally counted as 1 Trigger.

AI Smart Monitoring credit consumption: each time a detection is executed, Credits are deducted based on the actual consumption of this AI analysis; each detection is additionally counted as 100 Triggers.

Billing method: TOBY AI Credits use a prepaid recharge model (pay first, use later). Usage-based postpaid settlement is not supported. Owners of SaaS Commercial Plan or Enterprise Plan workspaces can self-service purchase Credits from Management > TOBY AI > Recharge Credits when the AI plan is Basic, Pro, or Team and the site has recharge enabled. The fee is deducted from the Billing Center balance. See Prepaid Credits for details. If you do not meet the conditions for self-service recharge, contact your Account Manager to handle it; if you meet the conditions, you may also choose the manual channel.

Deduction rules: the system first uses complimentary plan credits for deduction. After plan credits are used up or expire, it continues to deduct prepaid credits. Prepaid credits do not expire. When the credit balance is used up, features that consume credits cannot be used until you recharge.

Even if the credit balance is sufficient, reaching the daily credit limit may limit continued use; workspace owners can adjust this limit on the subscription page.

Credits Unit Price

Usage Analysis¶

In Plans & Billing > Usage Analysis, the "Log Raw Ingested Volume (Bytes)" chart of the Commercial Plan is displayed broken down by log index, and the statistic name uses the format count(“Index”), where Index is the log index name.

Further Reading¶

You may also want to learn more about: