ChangelogPilot Reviews and Details

Questions & Answers

1. What's the story behind ChangelogPilot?

   ChangelogPilot came out of a six-year stint as a startup CTO. We shipped real improvements most weeks and were never good at telling customers about it — there was always something that looked more urgent than writing the update, so the update didn't get written. That felt reasonable at the time and it was wrong: communicating what you shipped is part of the product, not housekeeping. What finally changed is that AI models got good enough to read a merged pull request and draft a genuine, customer-facing summary — close enough to approve rather than rewrite. So I built ChangelogPilot to make the writing step disappear: connect a GitHub repo, and each changelog entry gets drafted from what actually merged. It's a small, bootstrapped team in New Zealand, built for the small SaaS and dev-tool teams where the gap between shipping speed and telling-people speed is widest.

2. Which are the primary technologies used for building ChangelogPilot?

   • Language & runtime: TypeScript on Bun
   • Web framework: Hono (server-rendered HTML)
   • Frontend: HTMX + Tailwind CSS (Chart.js for analytics views)
   • Database: PostgreSQL with Drizzle ORM
   • AI drafting: Anthropic Claude
   • Billing: Stripe
   • Observability: OpenTelemetry + Pino
   • Hosting: Fly.io

3. Why should a person choose ChangelogPilot over its competitors?

   Most changelog tools compete on how nice the editor is or how the published page looks. That helps if writing was already happening — but for small teams (2–20 people) the real problem is that writing the changelog keeps getting deprioritised, so it just doesn't happen. ChangelogPilot is built for that failure mode: connect your GitHub repo, and every merged PR gets drafted into a customer-ready entry automatically — categorised as feature, fix, improvement, or breaking, with internal PRs filtered out. You review and publish to a hosted page in under a minute. You should choose it if you've tried a manual changelog tool, felt the guilt of the dusty page, and want the changelog to basically write itself.

4. How would you describe the primary audience of ChangelogPilot?

   ChangelogPilot is built for bootstrapped and small-team SaaS companies, developer tools, and API providers — teams of two to twenty who ship continuously but update their changelog once a month, if that. They care about keeping customers informed but don't have a dedicated writer, so summarising each week's PRs keeps getting deprioritised. They live in GitHub, value self-serve setup with no sales calls, and want the changelog to reflect what actually shipped without someone having to sit down and write it.

5. What makes ChangelogPilot unique?

   ChangelogPilot drafts from your merged GitHub PRs directly — not from notes you type after the fact, and not from customer feedback — so the changelog reflects what actually shipped, in words your customers can read. Most changelog tools give you a nicer editor and still expect you to write each update. ChangelogPilot assumes the writing itself is the obstacle and removes it: it reads your PRs, drafts a customer-ready entry in plain English, categorises it (feature, fix, improvement, breaking), and filters out internal PRs automatically. Your job drops from "write a changelog" to "approve a draft" — usually under a minute.