Release communication, operationalized
Draft once. Publish to your changelog, widget, email, feeds, API, and webhooks. Add proof when rigor matters.
Hosted surfaces
Changelog, widget, docs
AI + automation
Drafts, schedules, MCP
Distribution
Email, feeds, webhooks
Trust layer
Signing, analytics, audit trail
What teams use it for
Publish launches without copy-paste chaos
Start from real engineering work, then ship one clean update everywhere.
Keep release notes inside the product
Use the widget or docs surface when users should not leave the app to understand what changed.
Add trust controls only when you need them
Layer in signing, analytics, and audit trail as the workflow gets more sensitive.
The same platform works across launches, embedded updates, and higher-trust communication.
Write one update, review it once, and ship it everywhere customers look.
Explore use case
Keep release notes inside the product with a widget, changelog, and docs surface.
Explore use case
Add signing, audit trail, and verification when customers or auditors need proof.
Explore use case
More than a static changelog page.
Turn synced work into reviewable drafts.
Use one update layer across product and automation.
Queue launches and recurring update workflows.
Ship updates where customers already are.
Support email, RSS, Atom, and JSON feeds.
Track engagement and keep a defensible audit trail.
Start with one customer-facing surface, then add automation and trust controls as the workflow grows.