I built a tool that tracks whether your code still matches the original requirement
Hey guys, I'm an engineer/lurker here who has built a new product called Stoney! I am the solo founder/engineer on this project.
I built this because requirement drift is one of those problems every dev team has but nobody has good tooling for. A requirement gets written, gets built, and then six months later something changes quietly and nobody connects it back to the original ticket. The failure mode I kept seeing: a requirement like "free tier users get 100 requests/day" starts as a Jira ticket, gets built out, and slowly drifts until different parts of your codebase enforce it differently. No alert fires. No test fails. A customer just gets a weird experience and nobody knows why.
Stoney connects the dots from ticket to code to live API. It builds a registry of the business rules your system actually enforces, watches your repos for drift, and when something breaks it shows you the PR that caused it, the ticket that authorized it, and who owns the rule.
Connect your GitHub, Jira, and Slack in a few clicks and you're running in under 10 minutes. No config files, no manifests.
Free tier is permanent, no card required. Would love honest feedback from anyone. Am I hitting the mark here or is there a gap in what you would expect to see? You can find my product at stoneydev.com