logg reads the commits behind every release and writes the changelog — published to your page, your product, your API, and your team before you've closed the terminal.
npm i -g @logg/cli && logg loginLive
On the wire
Scheduled digests and per-project webhooksv2.4.0
9 seconds, tag to told
01—How it works
Release, tag, or PR merge — GitHub, GitLab, or Bitbucket. Pick the detection mode that matches how your team ships.
Commits, merged PRs, provider release notes, and the completed Linear issues behind the release — deduplicated into one picture.
Claude drafts a categorized entry — features, fixes, breaking changes — in your project's own voice.
Your public page, your product, your API, your team channels. One entry, every surface, the same moment.
02—What it writes
One release rarely means one story. Entries can now tag each item with an audience, and public pages grow a tab row so each reader sees their own cut of the log.
Features
Improvements
03—Why logg
Every team means to keep a changelog. Then the sprint ends, the tag goes out, and the record falls a version behind — then five. logg exists so the record keeps itself: every release read, written, and published the moment it happens, in a voice you would have used yourself.
Read our record04—Where it lands
Public page
logg.sh/your-project
React
@logg/react
Embed
one iframe, any site
REST API
cors · rate limited
MCP server
readable by agents
CLI
@logg/cli
Slack / Discord
posted on publish
RSS
per-project feed
05—Pricing
$0
Free during early access
$29
Per month · $24 annual
$79
Per month · $66 annual