Why we have a public changelog
Most software companies don't publish their changelogs publicly. They ship quietly, announce the occasional "big release" in a blog post, and leave customers guessing about what's actually happening. We do it differently for three reasons:
- It holds us accountable. When you commit to publishing a changelog every week, you ship every week. It's a forcing function.
- It builds trust. Technical buyers want to see a pattern of steady shipping before they commit to a platform. The changelog is proof.
- It helps you use MY LAURA better. New features are no good if you don't know they exist. The changelog tells you exactly what showed up this week.
Recent releases
What will appear here
Each changelog entry will include:
- Date — when the change went live in production
- Type — new feature, improvement, bug fix, integration, or security
- Summary — what changed, in plain language
- Why it matters — the specific user problem it solved
- Links — to relevant help documentation or feature pages
Entries will be grouped by week so you can scan the history quickly.
How to get notified of new releases
Three ways:
- In-app notifications. Significant releases show up as a notification in your MY LAURA inbox when you log in.
- Email digest. Weekly digest email that summarizes everything shipped that week. Opt in from your account settings.
- RSS feed. Coming soon — we'll publish the changelog as RSS for anyone who wants to pull it into a reader.
Want to request a feature? Email laura@getmylaura.com. Every request from a real customer gets read, usually by Laura personally. Many of them end up on the roadmap.