All Docs
FeaturesSaaS FactoryUpdated March 11, 2026

Public Changelog & Product Update Feed

Public Changelog & Product Update Feed

SaaS Factory automatically maintains a public-facing changelog for every product it manages. As the autonomous agent pipeline ships releases each night, those releases are immediately published to a live, user-visible feed at /changelog — no manual effort required.

Overview

The public changelog turns SaaS Factory's continuous delivery pipeline into a visible trust signal. Every release cut by the platform appears on the changelog page, complete with a narrative blog post written by the AI release agent.

How It Works

1. Releases Are Generated Automatically

The SaaS Factory pipeline creates a record in the releases table each time a version is shipped. Each record includes:

  • Version number — e.g. 1.0.120
  • Title — a short human-readable headline for the release
  • Release notes — structured description of what changed
  • blogPost field — a richer narrative written by the AI agent, suitable for public consumption
  • Timestamp — when the release was published

2. The Public /changelog Route

Each managed product includes a /changelog page in its template. This page:

  • Is publicly accessible — no authentication required
  • Renders release entries in reverse-chronological order (newest first)
  • Displays both the structured release notes and the blogPost narrative
  • Updates automatically as new releases are cut — zero manual publishing steps

3. Content Rendering

The blogPost field is rendered as rich markdown, supporting:

  • Headers and subheadings
  • Bullet lists and tables
  • Code blocks (for technical detail)
  • Inline emphasis

This allows the AI agent to produce polished, readable update posts that communicate the value of each release to non-technical users as well as developers.

Configuration

No configuration is required. The public changelog page is part of the standard product template and activates automatically when the first release is created.

If you wish to customise the appearance of the changelog page, edit the changelog route and associated components in your product's codebase. The data source (releases table) is managed by the SaaS Factory platform and should not be modified directly.

Internal vs. Public Changelog

SaaS Factory products include two changelog surfaces:

SurfaceAudienceAuth RequiredLocation
Changelog modalSigned-in users (in-app notifications)YesIn-app modal via changelog-modal.tsx
Public changelog pageAll visitorsNo/changelog

Both surfaces read from the same releases table, so content is always consistent.

Why a Public Changelog?

Leading developer tools (Cursor, v0, Bolt.new, Replit, Lovable) all maintain public changelogs. Research consistently shows that visible, frequent shipping:

  • Builds trust — users see that the product is actively maintained
  • Reduces churn — subscribers feel they are getting ongoing value
  • Drives word-of-mouth — interesting releases get shared
  • Differentiates from abandoned software — a timestamped history of improvements is proof of life

For SaaS Factory-managed products, the changelog is a direct, automated proof point of the platform's core promise: your product improves every night.

Related

  • Changelog — live release history
  • Release Management — how the platform cuts and tags releases
  • Beast Mode — the multi-agent supercycle that powers nightly improvements