About Calethia

Every audit pulled engineers off their work to re-prove controls that were already working. Calethia exists so GRC can prove it without them.

Our Story

I have been the person taking screenshots of GitHub. Audit season meant the same song and dance of updated screenshots and sign-offs on the same Google Docs, from engineers who had already signed them six months earlier. Product security filed exceptions for hundreds of CVEs. The incident response team dug through old tickets to close findings. The exercise only showed that I could produce a PDF on demand, and it made compliance the team nobody wanted an email from. I don't blame them.

Before I could ask anyone for evidence, I had to find which policy applied to a control. One version sat on a Confluence page nobody had touched in three years. A Google Doc contradicted it. Nobody owned either, and I spent more hours reconciling policy documents than doing the security work they described.

Most of the time compliance serves sales, which needs the report, more than security, which needs the risk reduced. I think GRC should reduce risk, not just document it.

You hired smart GRC engineers and compliance experts. Calethia puts them to work. They write policies as code in Git, tie each policy to the controls they back, and review changes the way you review a pull request. They retrieve evidence themselves, so you don't hand the job to a black-box platform and wait. Nobody screenshots anything.

Founder-led

Meet the founder

Daniel Wyleczuk-Stern

Founder, Calethia

Daniel founded Calethia after seeing audits repeatedly pull security engineers away from building controls. His background in security operations and offensive security shaped Calethia's engineering-first approach to compliance.

Want to learn more?

We'd love to show you how Calethia can help your team.