Every week, indie founders and small teams ship real improvements to their products — and most of that work never gets communicated to the people using it. Writing a changelog entry for every merged PR is tedious, easy to postpone, and usually the first thing to get skipped when things get busy.
Buoylog exists to close that gap. It watches the pull requests you merge on GitHub, turns them into plain-language release notes with Claude, and publishes them on a changelog page you can host under your own domain — no writing required, just a quick review before it goes out.
A buoy marks a fixed point at sea — something sailors can navigate by. A log is the record of a ship's journey. Buoylog marks every release you ship and keeps the record your users can follow.
Buoylog is built and run independently, with a strong bias toward shipping useful software over polish for its own sake. If something's broken or missing, it's usually a fast fix — not a ticket in a backlog.
Connecting Buoylog installs a GitHub App scoped to read-only access on pull requests and repository metadata — nothing more. Many changelog tools rely on a classic OAuth flow that requests GitHub's broad repo scope, which technically grants write access to your entire codebase even though the tool only ever reads PR titles and descriptions. Buoylog was built the other way around: it asks for exactly what it needs to do its job, and nothing your security team would have to think twice about.
Questions, feedback, or just want to say hi? Get in touch.