Founder of CerbiSuite — tackling logging chaos & governance for cloud teams

by

Hey everyone

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)

So I’m building CerbiSuite — Unified Logging Governance:

  • CerbiStream – a lightweight structured logger with governance baked in

  • CerbiShield – a governance dashboard to define logging rules, enforce them, and prove compliance

  • Future phases: routing + ML-driven anomaly/scoring on top of the metadata

Site’s here if you’re curious:

Right now I’m:

  • Prepping a Product Hunt launch for CerbiSuite — Unified Logging Governance

  • Talking to engineers, SREs, and founders about how they actually handle logging, compliance, and “oh no, legal wants an audit” moments

  • Trying to validate what’s genuinely useful vs. founder fantasy

I’d love to connect with:

  • Folks who’ve wrestled with log sprawl / high observability costs

  • People building devtools who’ve gone from “neat side project” to paying customers

  • Anyone who’s done governance or compliance in a way that didn’t make devs hate them

Happy to share what I’ve learned about logging, governance, distributed systems, or selling into enterprises as a solo dev. Looking forward to learning from this community.

15 views

Add a comment

Replies

Best

Thanks for reading this — I’m really looking for blunt, practical feedback.

If you work with logs / observability, I’d love to know:

  1. What tools are you using now?

  2. Biggest pain or “this is dumb but we live with it” moment in your logging setup?

  3. Would benchmarks + a sample CerbiStream config be enough for you to try it on a side project?

Happy to trade feedback on your product too.

Quick update if anyone’s curious to see this in motion instead of just reading about it:

I just put together:

  • A short Cerbi overview video – why I’m building it and how the pieces fit

  • A CerbiStream demo walking through a realistic .NET API that might handle PII and how the logging/governance behaves

  • A public repo with the demo implementation:
    👉

If you’re the type who wants to see code and actual behavior before forming an opinion, this is probably the best snapshot of where Cerbi is right now.

Specific feedback I’d love:

  • What feels overbuilt / “this is too much ceremony”?

  • What feels missing for “I’d actually try this on a real service”?

  • Anything about the DX that would make you bail immediately?

Also happy to trade: if you’re working on a devtool and want a blunt review from an architect / enterprise side, I’m in.