Simple pricing based on governed log volume
One dimension: monthly governed event volume. No feature tiers, no hidden seats, no data egress fees. We enforce monthly totals — not rolling averages.
Why governance
> Security tools govern code.
> CI tools govern builds.
> IAM governs access.
> Logs have no governance layer.
Deployment & licensing
Deployment & Licensing Truth
CerbiShield and the governance control plane are deployed entirely in your tenant. Your log data never leaves your infrastructure.
Licensing is based on governed log events per month.
Usage is counted per billing month.
If you exceed your tier in a month, Cerbi continues operating for the rest of that month.
Starting the next billing month, Cerbi enforces your tier cap.
Once the cap is reached, additional events are not accepted until you upgrade.
Your applications keep running normally. Only Cerbi event intake is affected.
Plans
For teams introducing telemetry governance.
Ideal for small teams and early production services beginning to apply governance to their telemetry pipelines.
For multi-service production systems.
Designed for growing platforms with multiple services where telemetry governance needs to be enforced consistently across environments.
For high-volume platforms and regulated workloads.
Built for production platforms operating at scale where telemetry governance, compliance visibility, and operational stability are critical.
Architecture
Cerbi validates and governs telemetry before it reaches observability platforms such as Splunk, Datadog, or Azure Monitor. By enforcing schema validation, sensitive field protection, and governance metadata at runtime, teams prevent telemetry issues before they propagate through monitoring systems.
Overage & enterprise
Overage policy
For workloads exceeding 1 billion events per month, contact Cerbi for volume pricing.
Contact UsCost estimator
We estimate monthly using 30.4 days
How to Interpret These Savings
These estimates reflect log volume reduction achieved through enforced governance policies. CerbiShield operates independently of log volume and does not charge per event, per gigabyte, or per query, which makes savings predictable as systems scale.
Why These Savings Scale
CerbiShield separates governance cost from data volume. As log volume grows, observability costs typically increase, while CerbiShield's governance cost remains fixed and predictable. This allows savings from reduced logging to scale over time without introducing new operational or pricing risk.
Estimates only. Vendor pricing varies by plan, region, retention, and indexing options. This models ingestion baselines to illustrate potential impact. Verify against your own bills.
Cost drivers
Platform notes
Built to Scale Without Cost Surprises
CerbiShield is designed to operate at scale without becoming a performance bottleneck or introducing usage-based costs. Governance is enforced efficiently and scales linearly as environments grow.
// Internal benchmarks confirm negligible infrastructure overhead
// vs. downstream observability ingestion costs.
Cerbi does not replace your existing log platforms. It governs what gets logged before data reaches tools like Datadog, Splunk, Azure Monitor, or ELK — helping teams control cost, enforce structure, and reduce noise.
Feature comparison
All capabilities included on every plan
There are no feature-based tiers. Licensing is based on throughput only.
| Feature | one | pro | pro++ |
|---|---|---|---|
| Governed log events per month | 25M | 250M | 1B |
| Unlimited applications and environments | |||
| Governance profiles and schema rules | |||
| Structured logging enforcement | |||
| PII and PHI field controls | |||
| Log scoring and classification | |||
| Dashboards and operational visibility | |||
| Role-based access control (RBAC) | |||
| Governance audit history | |||
| Reporting and data export | |||
| Multiple deployment targets | |||
| High-throughput ingestion and scoring |
Licensing is based on throughput only. All features are always enabled.
Pricing is provisional for Marketplace previews. Final terms, limits, and SLAs are confirmed in order forms or private offers. Cerbi governs schemas, scoring, and redaction while leaving log routing entirely under customer control.
Have questions? Check the FAQ or contact us.