Try Cerbi

See Cerbi catch risky logs in 2 minutes

No Azure required. No login. Pick the path that matches how you work — browser demo, CLI scanner, hosted playground, or enterprise pilot.

Browser demo requires no account. GitHub account required for Codespaces. Azure subscription required for tenant pilot.

All paths

Six ways to try or evaluate Cerbi. All free. None require Azure.

Just exploring

Browser demo

No login required

See Cerbi intercept and redact risky log fields in real time — directly in your browser. No GitHub account, no Azure, no install. Click play and watch governance run.

No account required. Runs entirely in your browser.

Developer

Scan your repo

Scan your own code

Install the Cerbi Scanner CLI and run it against your own codebase. Read-only. Nothing leaves your machine. Supports C#, Go, Java, Node/TypeScript, and Python.

No account required. No code upload.

Platform / security lead

Codespaces

Fastest — no local setup

Open the demo repo in GitHub Codespaces. Everything is preconfigured: unsafe sample logs, governance rules, a working policy file, and the run-demo script. Ready in about 60 seconds.

GitHub account required. Usage may count against your GitHub quota.

Platform / security lead

Docker Compose

Local demo — under 5 minutes

Clone the demo repo and run the compose stack locally. No cloud account required. Runs on any machine with Docker installed.

Requires Docker Desktop or Docker Engine.

Enterprise buyer

Azure pilot readiness

Tenant-deployed

CerbiShield deploys into your Azure tenant — no SaaS data plane, no log forwarding to Cerbi infrastructure. This path walks through what a 30-day pilot looks like and what your team needs to prepare.

Azure subscription required for tenant deployment.

Security or legal reviewer

Procurement / trust packet

Compliance & legal

Security questionnaires, DPA, subprocessor list, architecture overview, and data-handling policies — all in one place. No sales call needed to access these documents.

All documents are publicly available without login.

What happens in the demo

Five steps from your code to governed telemetry.

1

Code / Repo

Your existing codebase

2

Cerbi Scanner

Static analysis, no code changes

3

Governance Policy

Rules checked in to version control

4

Findings & Fixes

JSON, SARIF, Markdown output

5

Safe Telemetry

Governed logs reach downstream tools

Terminal walkthrough

Clone the repo, run one script, read findings. That is the entire demo.

cerbi-log-risk-demo
git clone https://github.com/Zeroshi/cerbi-log-risk-demo
Cloning into 'cerbi-log-risk-demo'...
cd cerbi-log-risk-demo
./scripts/run-demo.sh
Scanning 4,831 log statements across C#, Java, Go, Python, Node/TypeScript...
HIGH AuthService.cs:88 token logged in structured field
HIGH CheckoutService.java:112 cardNumber exposed via log4j2
HIGH user_handler.py:67 ssn in stdlib logging call
MED api/orders.go:43 raw request body logged via zap
MED webhook.ts:91 auth_token exposed in Winston
27 risky log calls found. See scan-results/ for JSON, SARIF, Markdown.

What you'll see

  • Unsafe logs with PII, secrets, tokens, raw payloads, and high-cardinality fields
  • Governance profile rules mapped to each finding
  • Scanner findings with file, line, and severity
  • Markdown, JSON, and SARIF output
  • CI/CD gate example — one flag flips report mode to gating mode
  • Before/after governed telemetry comparison

After the demo

Scanner findings become governance evidence. When findings matter across teams, CerbiShield adds centralized policy, scoring, audit history, and runtime enforcement — deployed into your Azure tenant.

Ready to see what your logs are leaking?

The browser demo takes two minutes. The scanner runs on your own code in under five. No login required for either.

No Azure required. No code upload. No login.

NEXTChoose your next proof

Use CerbiStream inside selected applications, Cerbi Gateway at the OpenTelemetry boundary, or both. CerbiShield keeps policy, rollout, violations, audit, and evidence under one governance program.

One initial workload/Customer-hosted in Azure/Existing destinations remain
Cerbi | Logging & OpenTelemetry Governance Before the Sink