Deploy CerbiShield
Use the Marketplace deployment so the governance control and evidence plane lives inside your Azure tenant.
Pricing + evaluation
Start by proving one control.
CerbiShield pricing is based on governed-event volume. The buying journey should be just as clear: discover risk for free, prove one real workload in Azure, then size production by the telemetry you actually govern.
01Choose how to evaluate
Path A / discovery
Find a real reason to care first.
Use the free Scanner when you have not yet identified the workload, field, or logging behavior worth governing. No runtime deployment is needed for this first step.
01Scan a repository
02Review concrete findings
03Choose a candidate workload
04Decide whether runtime governance is warranted
Path B / production-style proof
Prove the governance lifecycle in your Azure tenant.
Use the 14-day CerbiShield evaluation when you already have a representative workload and want to prove policy, rollout, enforcement behavior, and evidence.
01Deploy CerbiShield
02Choose Stream or Gateway
03Activate one policy
04Verify the governed result and evidence
02What happens after Start
Remove trial ambiguity before the Marketplace click.
A buyer should know what the evaluation will ask of them, what success looks like, and what Cerbi is not going to replace.
Evaluation outcome
One real control, on one real workload, with a downstream result and an evidence trail.
Open the control plane
Verify Dashboard access, role context, service health, and the environment Cerbi will govern.
Choose one workload
Keep the first proof bounded. Pick one application or OTLP path with a real logging risk.
Define one control
Create or select the governance policy you want to test: redact, drop, block, or otherwise constrain representative telemetry.
Select the enforcement boundary
Use CerbiStream for a selected application integration or Gateway for an existing OTLP path where that better matches the estate.
Verify and review evidence
Confirm the governed downstream result, rollout state, violation behavior, health, audit context, and evidence record.
03Plan model
Pay for governed volume, not another seat matrix.
Commercial meter
Governed events
Deployment
Customer Azure
Enforcement
Stream / Gateway
AI telemetry
Pro++ opt-in
| Plan | Price | Governed volume | Best fit | Action |
|---|---|---|---|---|
01Trial | $014 days | Evaluation | Prove deployment and one representative governance workflow in your Azure tenant. | Start trial |
02One | $79/ month | Up to 25M governed events / month | Smaller production estates that need centralized policy, evidence, and operational visibility. | View Marketplace |
03Pro | $249/ month | Up to 250M governed events / month | Growing platform and security teams expanding governance across more production telemetry. | View Marketplace |
04Pro++ | $499/ month | Up to 1B governed events / month | High-volume production estates and teams adding AI Logging Governance for connected AI telemetry evidence. | View Marketplace |
AI Logging Governance for Pro++
Separate from the Cerbi AI assistant.
AI Logging Governance gives Pro++ customers metadata-first visibility across connected AI logging paths: observed systems, provider and model metadata, scanner findings, runtime log observations, storage posture, policy outcomes, and redacted evidence. It is disabled by default, does not provision the Cerbi AI assistant, and does not store raw prompts or responses by default. See /ai-governance for the current scope. Confirm final commercial availability in the active Microsoft Marketplace listing or an approved private offer.
More than 1 billion governed events per month?
Cerbi supports custom high-volume capacity in the customer's Azure tenant. We validate peak volume, policy complexity, telemetry destinations, regional requirements, and resilience targets, then recommend deployment sizing and commercial terms. Custom capacity is not currently a self-service Microsoft Marketplace plan and does not imply a bespoke product fork.
04What stays yours
Your Azure tenant
CerbiShield is deployed into the customer Azure environment rather than operating as a shared raw-log relay.
Your observability stack
Existing downstream tools can remain in place. Cerbi adds governance before selected telemetry continues to them.
Your operating choice
Use the enforcement boundary that fits the workload. Cerbi does not require every application to adopt one identical runtime pattern.
05Common objections
Know the answer before procurement asks.
01Do I have to replace my logging or observability stack?+
No. Cerbi is designed to govern selected telemetry before it continues to existing destinations. Splunk, Datadog, Azure Monitor, Elastic, OpenTelemetry, SIEM, APM, and existing dashboards can remain in place.
02Does Cerbi require every workload to use the same enforcement model?+
No. CerbiStream and Cerbi Gateway are alternative or complementary enforcement boundaries. A team can use in-process enforcement for selected workloads and a Gateway boundary where existing OTLP estates make that the better fit.
03Is AI Logging Governance the same as the Cerbi AI assistant?+
No. The Cerbi AI assistant helps teams operate Cerbi by assisting with rule writing, suggestions, explanations, and onboarding. AI Logging Governance is a separate Pro++ deployment capability for connected AI telemetry metadata, scanner findings, runtime log observations, storage posture, and redacted evidence. It is disabled by default and does not store raw prompts or responses by default.
04Does Cerbi govern every AI model, agent, and tool action today?+
No. The current Pro++ scope is AI Logging Governance for explicitly connected sources: AI telemetry metadata, scanner findings, runtime log observations, storage posture, policy outcomes, and redacted evidence. Universal enterprise-wide discovery and autonomous agent action governance remain roadmap work. See /ai-governance for the current scope.
05Does customer raw telemetry have to pass through Cerbi-hosted SaaS infrastructure?+
That is not the core product architecture. CerbiShield and Gateway are customer-hosted in Azure, and the customer telemetry path stays within the customer's environment and existing downstream architecture.
06What is the easiest way to start without deploying the platform?+
Run the free Cerbi Scanner against a repository. It is the low-friction discovery path for deciding whether there is enough real logging risk to justify a runtime pilot.
07What is the 14-day trial meant to prove?+
The useful goal is not merely that the Dashboard loads. It should prove deployment, policy activation, one selected enforcement path, the downstream result, and the governance evidence around that control.
08How is paid usage licensed?+
The current commercial model is based on monthly governed-event volume rather than per-seat pricing. Final availability and terms are confirmed in Microsoft Marketplace or an approved private offer.
Not ready for Azure yet
Find the first risk for free.
Start with a repository and leave with concrete findings you can use to decide whether runtime governance deserves a pilot.
Run ScannerReady to prove the runtime model
Take one workload through the full lifecycle.
Deploy CerbiShield, select Stream or Gateway, activate one control, verify the result, and review the evidence.
Start 14-day trial