DEV Community

Srinivas Kondepudi
Srinivas Kondepudi

Posted on

We hit 3,600+ installs with zero marketing, here's what we learned building Chron

Six months ago I couldn't find a single tool that answered: what exactly did my AI coding assistant do in that session?

Not the output. The actions. The tool calls. The secrets it may have seen. The suggestions I accepted, and the ones I didn't.

So I built Chron.

What drove the traction

The problem is real and getting worse, developers want a record, security teams want visibility, nobody had a tool for both.

SIEM integrations. The moment we shipped chron connect splunk/sentinel/crowdstrike, enterprise security teams took notice. They don't want a new dashboard, they want events in the tools they're already monitoring.

The compliance angle. A community member pointed out Chron directly addresses OWASP AISVS C13 and NIST AI RMF logging requirements. That single comment spread further than anything we wrote.
What surprised us

Cross-platform demand. We built for Claude Code first. The moment we shipped chron connect codex for ChatGPT Codex, weekly installs jumped. People aren't loyal to one AI tool, they need audit coverage across all of them.

Where we are

3,657 installs. Zero marketing. Heading to 4,000.

npm install -g chron-mcp

What problem would make you install an AI audit tool without anyone telling you to?

Chron

Top comments (0)