Question 1

What is Cerbi?

Accepted Answer

Cerbi is a customer-hosted application logging governance system. Cerbi Scanner finds risky logging before production, CerbiShield manages policy and evidence, CerbiStream can enforce policy inside selected applications, and Cerbi Gateway can enforce signed policy at the OpenTelemetry boundary for selected OTLP log traffic.

Question 2

Do I need to replace my existing logger or observability platform?

Accepted Answer

No. Cerbi is designed to work with existing logging frameworks and destinations. Use CerbiStream where in-process enforcement is appropriate, Cerbi Gateway for selected OTLP log traffic, or both. Existing Splunk, Datadog, Elastic, Azure Monitor, OpenTelemetry, SIEM, APM, dashboards, and alerts can remain in place.

Question 3

What is Cerbi Gateway?

Accepted Answer

Cerbi Gateway is a customer-hosted OpenTelemetry governance boundary. It accepts selected OTLP log traffic, applies signed Cerbi policy, records governance evidence, and forwards governed logs to the customer's configured downstream destination. Gateway is available as an optional CerbiShield enforcement path and remains dormant until explicitly configured.

Question 4

How is Cerbi priced?

Accepted Answer

CerbiShield is priced by monthly governed event volume. Current Marketplace plan model: a 14-day Trial, One at $49/month for up to 100M events, Pro at $149/month for up to 1B events, and Pro++ at $299/month for up to 10B events. From February 1, 2027 UTC, US monthly prices become One $99, Pro $299, and Pro++ $999; Trial remains $0. New purchases use the price effective at purchase. Existing subscriptions retain their price through the current billing term; renewal uses the price effective then. Confirm local prices and terms in Microsoft Marketplace; Azure infrastructure costs are separate. Customers above 10B can contact Cerbi for custom capacity, deployment sizing, and commercial terms; custom capacity is not currently a self-service Marketplace plan.

Question 5

What is Cerbi AI Logging Governance?

Accepted Answer

Cerbi AI Logging Governance is a CerbiShield Pro++ deployment capability, separate from the Cerbi AI assistant, for connected AI telemetry metadata, scanner findings, runtime log observations, storage posture, policy outcomes, and redacted governance evidence. It is disabled by default and does not store raw prompts or responses by default.

Question 6

Does Cerbi route or relay raw logs through Cerbi infrastructure?

Accepted Answer

No shared Cerbi raw-log relay is required. CerbiStream runs in-process. Cerbi Gateway, when used, is deployed in the customer environment and forwards selected OTLP log traffic to customer-configured destinations. CerbiShield is deployed in the customer Azure tenant as the governance control and evidence plane.

Question 7

How does Cerbi support compliance and audit work?

Accepted Answer

Cerbi provides policy controls and evidence for logging-governance programs: versioned rules, deployment targeting, violations, validation results, reporting, RBAC, and audit history. These capabilities can support compliance work but are not themselves a certification or legal conclusion.

Question 8

Does CerbiShield run in my Azure tenant?

Accepted Answer

Yes. CerbiShield is deployed inside the customer Azure subscription. The control plane, evidence stores, and supporting services use customer-hosted Azure resources rather than a shared Cerbi data plane.

Question 9

How should I start evaluating Cerbi?

Accepted Answer

Start with Cerbi Scanner against a representative repository, review the findings, define a bounded policy, then choose the least disruptive enforcement path for the pilot: CerbiStream inside a selected application, Cerbi Gateway on selected OTLP log traffic, or both.

Question 10

How do customers add AI systems to Cerbi?

Accepted Answer

Customers use explicit governed paths. They can scan selected AI repositories in CI, optionally upload scanner evidence to CerbiShield Pro++, and route selected runtime AI logging metadata through CerbiStream, Cerbi Gateway, or another governed logging path. Cerbi does not automatically crawl all tenant AI usage.

Common questions,
answered directly.

Platform

Enforcement

Pricing & Plans

CerbiShield Dashboard

Deployment & Security

Compliance & Adoption

Need to evaluate your specific architecture?

Start with the logging-control gap.

Common questions,answered directly.

Platform

What is Cerbi?

Do I need to replace my existing logger or observability platform?

How should I start evaluating Cerbi?

Is AI required?

What does AI Logging Governance cover?

How do customers add AI systems?

Enforcement

What is the difference between CerbiStream and Cerbi Gateway?

Does Gateway require a Cerbi SDK in every application?

Does Cerbi Gateway replace OpenTelemetry Collector?

Does Cerbi route or relay raw logs through Cerbi infrastructure?

What throughput does Gateway support?

Is Gateway generally available?

Pricing & Plans

How is CerbiShield licensed?

What happens if we temporarily exceed our monthly licensed capacity?

What are the current Marketplace plan tiers?

Is AI Logging Governance included with the Cerbi AI assistant?

Where should I confirm final commercial terms?

CerbiShield Dashboard

What can I do in CerbiShield?

Can Cerbi retain evidence of governance activity?

Can policy be validated before broader rollout?

Deployment & Security

Does CerbiShield run in my Azure tenant?

How is Gateway policy protected?

Does Gateway expose an unrestricted public OTLP endpoint?

Where does customer telemetry go?

Compliance & Adoption

How does Cerbi support compliance and audit work?

Does Cerbi make us HIPAA, GDPR, PCI DSS, SOC 2, or ISO 27001 compliant?

Can Cerbi be adopted incrementally?

Need to evaluate your specific architecture?

Start with the logging-control gap.

Common questions,
answered directly.