A product changelog your customers notice
Ship, announce, and let customers see the product moving — on your domain, in your brand, without a support suite attached.
Most changelogs go stale because writing them is a separate chore that lands on whoever has the least context. Meanwhile the tools that promise to fix it want you to adopt a whole feedback-and-tickets platform, priced per seat, just to publish release notes.
On your own domain, in your brand
Serve the page from your domain and match your product: brand colour, logo, header copy, light or dark — plus custom CSS when you want it exact.
Customers hear about it
Email subscribers get notified on publish; webhooks post a rich card into Slack or Discord for your team and community.
Speak your customers’ languages
Publish per-locale translations of an entry; the public page offers a language switcher and falls back gracefully.
Your team, with roles
Invite teammates as owner, admin, editor or viewer. Collaborators never count against anyone else’s plan.
> draft this week's changelog from main
Agent → groups the merges:
## Faster exports, SSO fixes
- Exports now stream (10× larger files)
- Fixed SAML login for Okta
- New: bulk archive
You review → Publish → subscribers emailed,
Slack card posted, page live on your domain.Questions
- Do I need to adopt a feedback board or ticketing tool?
- No. Changelore is changelog-first. If you already run feedback in GitHub Issues or Linear, keep it there — this only publishes what you shipped.
- Can we remove Changelore branding?
- Yes, on Pro. The public page then carries only your brand.
Changelore is launching soon
The changelog written from your code. Join the waitlist for early access.
Join the waitlist