For public repositories
Free for open source. Every feature.
Your users' coding agents upgrade your library from whatever they remember. Give them your real changelog — versions, breaking changes, migration steps — and we'll cover the bill.
How to apply
Three steps, about two minutes.
- 01
Create a changelog
Sign up free and pick a short name for your project. Your changelog lives atrelease-ripple-roadmap.lovable.app/your-project. - 02
Link it from your README
Add your changelog link anywhere in the README — a line of text or a badge both work.README.md[](https://release-ripple-roadmap.lovable.app/your-project) - 03
Verify in one click
In the dashboard, open Billing, paste your repository URL and press verify. We check it on the spot and switch your workspace over.
Eligibility
What we check
Automatically, using public GitHub information. No account access needed.
- Public repositoryThe repo is public on GitHub.
- The original, not a forkForks and archived repositories don't qualify.
- Open-source licenseGitHub recognises an open-source license, such as MIT or Apache-2.0.
- README links backThe README contains a link to your LogPulse changelog.
| What you get | Free | Open source |
|---|---|---|
| Structured JSON feed: versions, breaking changes, migrations, deprecations | ||
| Remote MCP server and version-diff API for coding agents | ||
| Publish from agents and CI with API keys | ||
| Published releases | Up to 10 | Unlimited |
| AI release notes from GitHub, written in your tone | 3 to try | Unlimited |
| Auto-draft on every merged PR or GitHub release | ||
| Email subscribers | Up to 100 | Unlimited |
| Email newsletter blast on publish | ||
| Embeddable widget, hosted changelog & public roadmap | ||
| Reactions, comments, upvotes & scheduled publishing | ||
| Team members | Just you | Up to 5 |
| Remove “Powered by LogPulse” badge | ||
| Custom domain on request (changelog.yourdomain.com) |
Questions
The fine print, in plain words
Building a commercial product? See Pro.