Fizlog

can an entry from the CI api land as a draft so i can clean up the wording before it goes live? my deploy messages are not something users should read lol

The pricing logic here is exactly right — changelog tools for indie projects shouldn't cost more than the hosting. One script tag with Slack alerts and a public page out of the box covers 90% of what solo builders actually need. Does the widget support custom styling to match the product's branding?

One script tag with plain PHP and MySQL and no build step is a refreshing constraint. Two practical questions: is the publish-from-CI API idempotent, so a retried deploy job does not post the same entry twice, and can entries carry a tag such as feature or fix so the widget can filter them?

Can the widget follow the host site's theme and be navigated entirely by keyboard? Those details would help developers assess integration and accessibility.

$0.99/mo for unlimited projects is refreshingly honest pricing. Does the widget show an "unread" dot or a count for returning users, so they notice new entries without opening it? And can entries be scheduled to publish at a set time, for releases that go out overnight?

Built this because every changelog tool I found was priced for teams with 50 seats, not a side project with a dozen users. Plain PHP + MySQL, no build step — happy to answer questions about the stack or the $0.99/mo launch pricing.

The deploy-script API plus RSS in a no-build PHP/MySQL widget is a pragmatic fit for small SaaS teams. Can the widget show unreleased roadmap entries separately from published updates?

The deploy-script API plus RSS in a no-build PHP/MySQL widget is a pragmatic fit for small SaaS teams. Can the widget show unreleased roadmap entries separately from published updates?

Can changelog entries be exported as Markdown for keeping a copy in the repo?

One script tag for a hosted changelog widget, public page, RSS, and Slack or Discord alerts, built on plain PHP and MySQL with a free single-project tier, keeps SaaS release notes from needing another heavyweight stack. If you ever need AI for the business, PZERO is at pzero.studio.

Publishing release notes from a deploy script through the API is the part I'd actually use. Can the widget filter entries by platform? I ship separate iOS and Android release notes, so one shared feed would confuse people on each side.

Played with the live demo on the landing page. The panel opens fast, the shadow DOM really does keep the host styles out, and the RSS feed is clean: one item per entry with the [New]/[Improved]/[Fixed] type in the title and a stable #entry anchor as the guid, so readers won't show duplicates. Small accessibility note from the demo: with the panel open, pressing Escape doesn't close it, and the bell button has no aria-expanded and the panel no dialog role, so a screen reader user doesn't hear that anything opened. Since it gets embedded into other people's apps, Esc-to-close plus those two attributes would save every customer from patching it themselves.

The deploy-script API is the standout for me — publishing release notes straight from CI means the changelog never goes stale, which is the failure mode of every changelog I have ever maintained. Curious whether entries can be scheduled ahead of a release or if they go live immediately on publish. The $0.99/mo pricing also makes this an easy yes for side projects.

The API to publish from CI is the part I like most. Release notes written by hand are usually the first thing that stops when a team gets busy. Does the public changelog page get its own indexable URL per entry, or is it one long page?

Nice to see a widget that ships as one script tag. How does it behave on a site with a strict Content-Security-Policy? I just added a few third-party badges to my own site and learned the hard way that an asset host that redirects (say to www) gets blocked even when the original host is allowlisted. It would help to document the exact script-src / connect-src / img-src hosts the widget needs, and whether the shadow DOM styles are injected inline (which would need style-src 'unsafe-inline').

The hosted changelog page plus RSS is the part I would use most; the in-app widget is nice, but the public page is what you can link from an email or a Discord announcement. Practical question: does the script tag load the widget asynchronously and without blocking render? On a client-facing app the first paint matters more than the what's-new bubble, so a small deferred script with a cached JSON feed would be ideal. Also curious whether the widget shows an unread dot per user or just per browser.