Billing
VARICON billing is designed around a simple principle:
Detection is free. Understanding is paid.
This section explains how billing works across pricing, usage, metering, and product surfaces.
Unlike traditional infrastructure tools, VARICON does not charge for raw traffic, logs, or test execution. It charges when anomalies enter the intelligence layer and become billable analysis units.
What this section covers
Billing model
Understand the conceptual model behind billing and why VARICON prices intelligence instead of infrastructure.
Usage and metering
See where usage is counted, how billable units are created, and where the paid boundary begins.
Product and implementation
Explore the product-facing and implementation-facing parts of the billing system.
Core concepts
Billable unit
The core billing unit is:
1 enriched anomaly = 1 billable unit
Free layer
Always free:
- anomaly extraction
- fingerprinting
- report generation
- CLI usage
- GitHub Action usage
Paid layer
Billable when enabled:
- classification
- severity scoring
- remediation hints
- advanced interpretation
Why this model exists
VARICON is built to be:
- easy to adopt
- transparent to developers
- aligned with actual value
- safe by default
That means teams can run the open-core system freely and only pay when deeper anomaly understanding becomes useful.
Recommended reading path
If you are new to VARICON billing:
If you are evaluating cost and adoption:
Summary
Billing in VARICON is not based on traffic volume.
It is based on when anomaly data becomes useful intelligence.
VARICON does not charge for running the pipeline. It charges for extracting meaning from anomalies.