I m building CerbiSuite: governed logging for teams that need structured logs without accidental PII/PHI leaks or schema chaos.
This week I shipped the first end-to-end scoring pipeline: CerbiStream + logger plugins emit a lightweight scoring event (violations, required field misses, redaction hits no raw log bodies), and a new Scoring API ingests it and writes to Postgres with idempotent semantics. The goal is to make governance measurable over time (drift, coverage, risk), not a doc people forget.
In parallel I ve been doing a ton of voice-of-customer work cost sprawl, inconsistent fields across services, compliance reviews where nobody can prove what s logged, and dashboards that break whenever one team just adds a property.
Targeting a January release, aligned with Microsoft as we finalize Marketplace/ISV readiness.
I m Thomas, a principal architect-turned-founder working mostly in cloud-native backend systems (.NET, Azure, distributed apps, all the usual suspects).
Over the last few years I kept running into the same mess at every company:
Logs scattered across tools
Observability bills creeping into this can t be right territory
Zero governance on what people log (PII everywhere, no standards, no consistency)
I m gearing up to launch CerbiSuite, a governance-first approach to .NET logging that aims to stop sensitive data before it hits your SIEM and to keep logs consistent across teams.
