Today we are introducing ChangeLayer as a broader home for software teams that need to communicate product progress clearly.
For a long time, the core of the product was changelogs. That is still true in an important way. Changelogs remain one of the clearest ways to create a durable record of what shipped and help customers stay informed.
But over time, it became obvious that software teams do not just need a changelog.
They need a fuller product communication system that helps them explain what launched, what is coming next, and how those updates connect across the life of a product.
That is the direction this launch represents.
What ChangeLayer now includes
ChangeLayer is built around three connected parts of product communication:
- Changelogs for the durable record of shipped work
- Release Notes for launches that need more context and explanation
- Roadmaps for planned work, in-progress work, and the larger story of where the product is heading
Each of these solves a different problem, but they work better when they live together instead of being split across separate tools and scattered workflows.
Why Release Notes matter
Many product updates need more than a short changelog entry.
When a launch affects workflow, changes how a feature works, or deserves a clearer explanation, teams need a format that can go deeper without becoming messy.
That is why we added Release Notes.
Release Notes make it easier to explain:
- what changed
- why it matters
- who should care
- what a user should do next
They help teams move from a raw shipped update to a clearer customer-facing narrative.
Why Roadmaps matter
Customers and internal teams rarely think only about what shipped today. They also want to understand direction.
That is where Roadmaps come in.
Roadmaps help product teams show:
- what is planned
- what is currently in progress
- how ideas turn into shipped outcomes
When Roadmaps connect naturally with changelogs and Release Notes, the full product story becomes easier to follow. Users can see where work started, what changed along the way, and how the result was ultimately delivered.
Why this is bigger than a changelog product
The more we built, the clearer it became that the product was growing beyond the scope of a single changelog tool.
We are building toward a broader layer for software product communication and product management, one that gives teams a cleaner way to manage launches, updates, roadmap visibility, and the systems around them.
That does not mean changelogs are becoming less important. It means they now sit within a bigger and more complete workflow.
What this means going forward
This launch opens the door for a wider range of product capabilities in the future.
We already have more in the pipeline, and the goal is straightforward: help software teams manage product communication from one place with less friction and better clarity.
If you have used us for changelogs so far, that core experience remains central. What is changing is the scope of the platform around it.
This is the beginning of a broader direction, and we are optimistic about where it leads.
If you want the story behind the rename itself, read why we rebranded from Chxngelog to ChangeLayer.