Nitrozen is a product changelog platform for SaaS teams that need a clear, public way to publish product updates. It is built around three jobs that usually get split across docs sites, email tools, and in-app banners: writing release notes, hosting a readable public changelog page, and showing those updates inside the product itself. The product lives at https://nitrozen.io and first went live around 14 February 2026 as a dedicated changelog platform (distinct from any earlier use of the nitrozen.io domain for unrelated content).
Who Nitrozen is for is straightforward. Indie founders and small SaaS product teams use it when they want users to see what shipped without maintaining a custom changelog page. Product managers use it to keep a dated history of New, Improvement, Fix, and Announcement entries in one place. Developers use it when changelog publishing should sit next to the release process rather than in a separate marketing workflow. Agencies and multi-product shops use multi-project support so each product gets its own changelog page and slug from a single dashboard. The common thread is the same: people who ship software regularly and need a lightweight, branded channel for product communication.
At its core, Nitrozen is a hosted changelog. You create a project, write entries in Markdown, assign a category badge, and publish. Public changelog pages are available on a clean URL so anyone can read updates without logging in. Entries can be organized as New, Improvement, Fix, or Announcement, with color-coded badges that make scanning a long feed easier. Markdown covers the formatting teams already expect: headings inside the entry body, lists, emphasis, and code blocks when a change needs a snippet. Multi-project support means one account can run changelogs for several products, each with its own page and slug, instead of mixing every release into a single feed.
The embeddable widget is the second surface. Adding a single script tag to a site or app loads Nitrozen asynchronously so it does not block page rendering. The widget fetches the latest entries, can show a notification badge for new updates, and opens a panel of recent changelog items without sending the user away from the product. That pattern is aimed at product teams who want “what’s new” inside the app rather than only on a marketing site. Free-plan accounts already include the public page, Markdown, category badges, and the embeddable widget, so early teams can try both the public and in-app paths before paying.
Pricing is freemium by design. The Free plan is $0 per month with no credit card required: one project, five entries per month, a public changelog page, Markdown, category badges, and the embeddable widget. That is enough to validate the workflow for a single product without committing budget. Pro is $9.99 per month for one project, up to 100 entries per month, everything in Free, plus custom domains, priority support, 30-day analytics, and API access. Business is $29.99 per month for up to ten projects, 1,000 entries per month per project, everything in Pro, 90-day analytics, dedicated support, and team collaboration marked as coming soon. An early-bird Lifetime Deal is $49 one-time for three projects, 100 entries per month per project, custom domains, 90-day analytics, the widget, and API access. If a paid subscription ends, the plan stays active until the billing period closes, then downgrades to Free; projects and entries are not deleted. The freemium shape exists so a team can publish real updates on day one, prove that users and teammates actually read the feed, and only then unlock domains, higher entry limits, analytics, and API automation.
