Founder of CerbiSuite — tackling logging chaos & governance for cloud teams
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: https://www.cerbi.io
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.
Replies