I built Logly because I kept doing the same annoying thing after every release. Open git log. Copy the commits. Paste into a doc. Try to make "fix auth bug" and "refactor user service" sound like something a human would want to read. Spend 20 minutes on something that should take 2. Every developer I know does this. Nobody talks about it because it feels too small to complain about. But it adds up. And more importantly, it's completely solvable. The problem wasn't writing. It was the translation layer between what a commit says and what a user needs to understand. That's exactly what AI is good at. So I built the simplest version: paste your repo URL, AI reads your commits, drafts a changelog, you edit and ship. The build process had one honest detour. My first approach was more ambitious, let users map custom domains and host their changelogs directly. Spent time on it, hit real infrastructure complexity, and eventually made the call to cut it. Not because the idea was wrong. Because it was solving a problem users hadn't asked for yet.

logly

Turn commits into beautiful changelogs

Turn commits into beautiful changelogs