Your commits already tell your product's story. Publish it.

Changelogs are the chore everyone skips, so users never hear what shipped. DeployLog turns the commits you already wrote into a published changelog, straight from your pipeline, no dashboard detour.

Start free with GitHub See live demo

Free forever for three projects. No credit card.

Publish from your pipeline

Ship the changelog the same way you ship code, from the CLI or a GitHub Action.

CLI

$ deploylog push --from-git --ai-summarize --publish
  Reading 7 commits since v1.3.2
✓ Drafted "v1.4.0: Dark mode and faster search"
✓ Published to page, widget, RSS, email

GitHub Action

- uses: deploylogdev/action@v1
  with:
    api-key: ${{ secrets.DEPLOYLOG_API_KEY }}
    project: my-app
    ai-summarize: true

widget

This widget is live

It's running on this page, pointed at DeployLog's own changelog. Embed it on your site with one script tag.

<script
  src="https://cdn.deploylog.dev/widget.js"
  data-project="your-project-id"
  defer
></script>

workflow

How it works

Write

Draft in the dashboard, push from the CLI, or let the GitHub Action run on every release tag.

Publish

One click to publish. Write the Markdown yourself, or take an AI draft from your commits.

Delivered everywhere

Public page, embeddable widget, RSS + JSON feeds. Email digest to subscribers on Pro.

features

Everything in one place

Embeddable widget

About 4 KB gzipped. Shadow DOM. Drop one script tag on any site.

See the live demo

RSS + JSON feeds

Your users can subscribe in their reader. JSON for anything programmatic.

Why changelogs matter

CLI

`deploylog push --from-git` drafts entries from your recent commits.

deploylog on npm

GitHub Action

Runs on release tags. Files a draft unless you set `notify-subscribers: true`.

Action on the Marketplace

Email digests

Your subscribers get the changelog in their inbox when you publish.

How digests work

AI summarize

Paste commits. Get a changelog entry. Claude Haiku, under the hood.

See it in the pipeline

Manual

A manual is your product's set of numbered chapters, and a chapter is one page whose factual sentences are anchored to your code. A recorded value that moved is drift. The `manual` check annotates findings on a pull request, and with `fail-on: drift` it fails when a cited value moved.

Read DeployLog's own manual

Straightforward pricing

Start free. Upgrade when you outgrow it.

Free

$0/forever

Everything you need to publish a public changelog.

3 projects
Hosted changelog page
Embeddable widget (DeployLog branding)
RSS + JSON feeds
CLI + GitHub Action
Import from GitHub Releases
5 AI summaries per month
5 manual generations per month

Start free

Pro

Recommended

$19/month, or $190/year

For individuals and teams that publish often.

Everything in Free
Unlimited projects
Remove DeployLog branding
Email subscribers + digests
Advanced analytics
Widget customization
Unlimited AI summaries
20 manual generations per month

On the roadmap

Custom domain

Start Pro

Need team features like SSO, roles, or private changelogs? Email the DeployLog team.

Questions

Do my users need an account to read the changelog?: No. Your public changelog page is readable by anyone, and the widget works without login. Only publishing needs an account: one owner account per organization today.
Can I use my own domain?: Custom domains are on the Pro roadmap and not live yet. Today every changelog lives at deploylog.dev/p/<slug>/changelog.
What does the CLI do?: `deploylog push` sends an entry from your terminal. `--from-git` reads recent commits. `--ai-summarize` drafts a clean entry with Claude Haiku, which you review before publishing.
How does the widget affect my page speed?: The widget is about 4 KB gzipped, isolated in Shadow DOM, and loaded with `defer`. It does not block render.
Can I cancel anytime?: Yes. Cancel from the Stripe Customer Portal. You keep Pro features until the end of the billing period, then drop to Free.