Your releases, in the room where your team already is
Chronik watches the repositories you choose and posts a readable summary the moment a release goes out — no bots to babysit, no tokens to hand over.
Then choose a channel. Two steps, and no access token ever leaves your side.
Built for the side that ships
Most integrations are written for the reader — a feed you subscribe to. This one is written for the person cutting the release: you choose which repositories are announced, where each one goes, and what the message says.
It arrives because GitHub said so
No polling, no schedule, no window in which a release exists and nobody has been told. GitHub sends the event, and the announcement follows it — which is also why nothing here needs a token that keeps working while you sleep.
Release notes that survive the trip
Headings stay headings, lists stay lists, tables stay readable and a code block keeps its shape. Notes written in GitHub-flavored Markdown are rendered for each destination rather than pasted into it — the failure that looks like nothing went wrong.
Free, and not a trial
No seat count, no per-repository price, no plan that expires and takes your rules with it. What it costs to run is small enough that charging for it would cost more than the running does.
Hosted in the EU
Servers, database and backups are in the European Union, and the list of who else processes anything is written down rather than implied. That is a statement you can check, in the imprint and the privacy policy below.
Then choose a channel. Two steps, and no access token ever leaves your side.