We want to hear how Chron is working in your workflow — and we'll thank you properly for sharing.
No form. No survey. Just a real answer to one question:
What does Chron catch that you would have otherwise missed?
That's it. One sentence or five paragraphs — whatever you have.
Why we're asking
Chron just crossed 6,000 downloads. We know it's running in real teams, on real codebases, in real compliance workflows. But download numbers don't tell us what actually matters to people using it.
We're building the next layer — evidence connectors, board-ready intelligence reports, a live UI — and the most useful thing you can give us right now is a real story. Not a feature request. A story.
What you get for sharing
We don't think "thank you for your feedback" is enough. So here's what we're offering:
1. We feature you.
If you share a case study (your org, your workflow, what Chron surfaced), we'll feature it in our next article — with full credit to you and your team. Public signal for your work.
2. We gift you a coffee.
For any substantive feedback — one paragraph minimum — we'll send you a Buy Me a Coffee gift directly. Small, but real.
3. Early access to NitivAI.
If you're dealing with compliance at scale — SOC 2, ISO 27001, EU AI Act — and want early access to the commercial governance layer we're building on top of Chron, tell us. We'll move you to the front of the list.
You can get one, two, or all three. Your call.
Two ways to share
Public: Open a thread in GitHub Discussions — your story becomes part of the community record and helps the next person deciding whether Chron is worth trying.
Private: DM @sirinivask here on dev.to, or reach out directly if you'd prefer the conversation stays internal. Enterprise workflows often can't go public — that's fine.
Chron is local-first. Your audit trail lives on your machine. No cloud, no vendor lock-in. If that's been useful to you, we'd love to know how.
Top comments (0)