If you are shopping for a changelog tool, you have probably noticed that the feature lists all converge. Everyone has a widget, a hosted page, some analytics, and a screenshot of a tidy "what's new" panel. Feature tables are where these tools look identical.
Pricing models are where they stop looking identical, and that is the part that decides what you pay in a year.
Here is what to actually check, using Beamer as the reference point since it is the tool most people compare against first.
What Beamer costs
Beamer's published pricing, as of July 2026:
| Plan | Monthly | Annual | MAU cap |
|---|---|---|---|
| Free | $0 | $0 | 1,000 (1 teammate) |
| Starter | $59 | $49/mo | 5,000 |
| Pro | $119 | $99/mo | 10,000 |
| Scale | $299 | $249/mo | 50,000 |
Extra users run $50/month per additional 5,000 MAU. The Feedback module (roadmap, idea voting) and the NPS module are separate add-ons at $99/month each.
None of that is a criticism. Beamer is a capable product engagement platform, and if you want announcements, segmentation, surveys, and a feedback board in one dashboard, the price is reasonable for what it does. The problem is that a lot of people buying it only ever wanted the changelog.
The pricing axis matters more than the feature list
Notice what Beamer bills on: monthly active users.
Think about what that means over time. Your changelog workload is basically constant. You ship something, you write a paragraph about it, you publish. That work is the same whether 500 people use your app or 50,000.
Your bill is not constant. It scales with your app's success. Cross 10,000 MAU and you are on a $119/month tier for the same paragraph you were writing at $0. Cross 50,000 and it is $299. You did not use more of the tool. You just grew, and the tool is priced to capture that growth.
This is the single biggest thing to check when comparing changelog tools, and it is the thing feature tables never show you. Ask one question of every tool on your list:
If my traffic goes up 10x and my publishing habits do not change at all, what happens to this bill?
If the answer is "it goes up a lot," you are not buying a changelog. You are buying a percentage of your own growth.
A checklist for comparing changelog tools
Beyond the pricing axis, these are worth checking before you commit, roughly in order of how often they bite people later:
-
Is the widget CSS-isolated? If it renders into your page's normal DOM, it inherits your global styles and your resets fight its layout. Shadow DOM isolation is the fix. Ask, or open devtools on their demo and look for a
#shadow-root. - Does the widget fail silently? A marketing widget must never break the host app. If their CDN has a bad day, your product should not.
- What happens when you stop paying? Does the hosted page stay up, redirect, or 404? Your changelog URLs may be linked from release emails and docs.
- Can you get your content out? Look for an export or an RSS feed. Release notes are writing you own.
- Does the free tier carry a badge? Many do, including mine. That is a fair trade for free, but you should know before you embed it, not after.
- How much of the product is add-ons? A cheap base tier plus two mandatory $99 modules is not a cheap tool.
- Do you actually need segmentation? It is the feature most often used to justify the jump to a higher tier, and the one solo products least often need. If everyone sees the same feed, do not pay for targeting.
That list is the whole point of this post. Run it against any tool, including the one I build.
Where Patchlog fits, and where it does not
Full disclosure: I build Patchlog, so treat this section as the biased part and check it yourself.
It exists because of the pricing axis above. It is a drop-in changelog widget plus a hosted page, priced flat at $7/month (or $5/month billed yearly) rather than per monthly active user. Traffic growth does not change the bill. The free tier gives you one project and 25 updates, and it shows a small "Powered by Patchlog" badge, which is how the free tier pays for itself.
The install is one tag, no SDK and no npm install:
<script src="https://cdn.patchlog.io/widget.js"
data-project="your-project-id"
data-position="bottom-right"
async></script>
It renders in a Shadow DOM, so it does not collide with your CSS, and it works the same in React, Vue, Rails, or plain HTML.
Now the honest part, because a comparison post that only lists strengths is an ad. Patchlog does not have:
- User segmentation or targeting. Everyone sees the same feed.
- NPS surveys, roadmaps, or feedback boards.
- Email notifications or digests.
- A public API.
Those are real gaps, not roadmap teases. If you need to announce a feature to enterprise accounts only, run NPS surveys, or collect and vote on feature requests, Patchlog is the wrong tool and Beamer or Canny is genuinely the better buy. Pay them.
The decision rule
It comes down to one question: are you buying a changelog, or a product engagement platform?
If you need segmentation, surveys, feedback boards, and a team dashboard, buy the platform. Those tools are priced the way they are because they do a lot, and the MAU model is the standard way that category charges.
If what you actually want is for your users to notice you shipped something, you want a widget, a hosted page, and a flat bill. Anything that meters your changelog against your own growth is charging you for the wrong variable.
Either way, check the pricing axis before the feature table. The feature table is where these tools look the same. The pricing axis is where they differ, and it is the one you live with.
Top comments (1)
the sharper version of this is that MAU is a meter you cannot control and mostly cannot forecast. your changelog workload is flat, but the bill moves with how well your marketing is going, so a good quarter shows up with an invoice attached to it.
worth being fair to the vendor though: MAU is not arbitrary on their side, because widget traffic genuinely does scale their infra and support. the mismatch is that the buyer's value does not scale on the same axis. that is the actual test when comparing any of these, and it is a better one than the feature table: does the meter track the value you get from the tool, or does it track your own success at something unrelated to it.
the same trap turns up in partner and affiliate tooling, where the meter is tracked revenue or number of partners, so the tool gets more expensive exactly as the thing you were trying to grow starts working.