SaaS Changelog and Status Page

This package builds two pages that answer the questions SaaS customers otherwise send to support: a changelog that shows what shipped this week, and a status page that shows whether the product is working right now. Both sit on your own domain, in your brand, and both can be followed by email so customers hear about changes before they go looking.

The changelog

Each entry has a date, a title, tags such as New, Improved and Fixed, and a screenshot or short GIF. You write entries in MDX or a CMS, and an RSS feed lets Zapier, Buffer or a reader app pick them up. From Business up, subscribers receive new entries by email through Resend, Postmark or Loops. Premium adds a "What's new" widget inside your app with an unread dot, which shows existing users the changes that affect them without a separate announcement.

The status page

• Components such as API, dashboard, webhooks and email delivery, each with its own state.
• Incidents posted from a short admin form, moving through investigating, identified, monitoring and resolved, with timestamped updates.
• On Business and Premium, states come from checks in Better Stack, UptimeRobot or Checkly, or from pings your own scheduler sends, with 90 days of history per component and notices for planned maintenance.
• Premium lets subscribers follow only the components they use and posts incidents to your Slack or Discord.

When the product itself is down

The status page runs on hosting separate from your app, so an outage on your servers does not take it offline, and the admin form works from a phone. The page reports what your checks and your team say; it does not improve uptime, and incident wording stays with you. Monitor subscriptions and email sending fees are billed by those providers.