How Billing Works
VARICON uses a usage-based billing model aligned with one core idea:
You pay for understanding anomalies, not just detecting them.
Two layers of value
VARICON separates billing into two distinct layers:
1. Detection (Open Core)
- Local extraction
- Fingerprinting
- Basic summaries
This layer is free and runs entirely in your CI.
2. Intelligence (Paid Layer)
- Remote enrichment
- PII detection
- Severity scoring
- Remediation hints
This is where billing happens.
What gets metered
Billing is based on:
- Number of anomalies processed
- Enrichment requests
- Volume of data analyzed (optional future dimension)
Each anomaly can trigger:
- 0 → free (local only)
- 1 → paid (enriched)
Usage flow
- CI generates anomalies
- CLI processes them locally
- Optional: anomalies are sent to enrichment API
- Enrichment adds intelligence
- Usage is metered per anomaly
Safety boundary
Billing operates after projection rules:
- Public mode → safe, redacted
- Private mode → full data (controlled environments only)
This ensures:
- no accidental PII leakage
- predictable billing inputs
Fail-open principle
If enrichment fails:
- anomalies are still returned
- billing does not occur
This guarantees:
- CI never breaks
- users are never charged for failed requests
Summary
- Detection is free
- Intelligence is paid
- Billing is per anomaly
- System is fail-open and safe-by-default
Next steps
Last updated on