Ship the code.
We'll ship the news.
ShipNote turns your merged PRs into a developer changelog and a plain-English “what's new” — then publishes both to a branded page, an in-app widget, and email. Nobody has to remember to write it.
Private beta · GitHub-based
You shipped it. Your customers never heard.
Writing the update is the chore that always loses to shipping the next thing. So great work goes unannounced, and adoption quietly leaks — feature by feature nobody knew you built.
- feat: realtime presence indicators
- perf: 4× faster cold start
- fix: webhook retry backoff
announcement sent to customers
✗ nothing — again
One git history. Two audiences. Zero rewriting.
The same release, rendered for the people who build your product and the people who use it — generated together, every time you ship.
feat
- a4f1c2eapi: cursor-paginate GET /events (replaces offset)
- 9c0b7d1dashboard: saved filter views per workspace
perf
- 1e93aa0ingest: batch webhook fan-out, p95 1.8s → 340ms
fix
- 77de4b9auth: refresh token rotation race on parallel tabs
Filter your event feed and keep the views
Build a filtered view once and pin it — your saved filters are now there every time you open the dashboard.
Webhooks arrive almost instantly
Event delivery is roughly five times faster, so downstream automations fire without the lag.
No more random sign-outs across tabs
Working in several tabs at once no longer logs you out unexpectedly.
Three steps, then it runs without you.
- 01
Connect your repo
GitHub in two clicks. ShipNote reads your merged PRs and tags — no config files, no commit conventions required.
- 02
We translate every release
Two outputs, generated and grouped automatically: a technical changelog and a plain-English what's new. No template wrangling.
- 03
It publishes itself
Branded page, in-app widget, email and Slack digest — all on release. You never have to open an editor.
Generation is free. Being heard isn't.
Turning commits into text is a solved, commodity problem. The hard part — and the part your customers feel — is getting the news in front of them, everywhere they already are. Every channel is configured in-app, not in a config file.
Hosted branded page
A branded changelog page at your own ShipNote URL — your logo and colors, indexed by search, with an RSS feed built in. Always live, nothing to host.
In-app what's-new widget
A notification dot you drop into your product, where adoption actually happens. Customers see what's new in context — not in an inbox they ignore.
Email subscribers
Self-serve, double opt-in email. Zero-config — ShipNote sends from its own platform sender the moment you publish, so you just toggle it on. No domain or API key to wire up.
Slack
Every release lands in your team's Slack channel as native Block Kit. Paste an incoming-webhook URL once in-app — the secret is encrypted per workspace.
Multi-platform webhooks
Push to Discord, Microsoft Teams, or any custom JSON endpoint — formatted per platform. Drop in the target URL in-app and ShipNote shapes the payload.
Google Chat
Releases posted straight into your team's Google Chat space through a per-workspace incoming webhook you configure in-app.
Beamer, AnnounceKit and LaunchNotes charge $49–149/mo for the manual version of exactly this. ShipNote does it without the human.
You can finally let it run on its own.
Most tools still need someone to check each release, because some things shouldn't go out automatically. ShipNote quietly holds those back and surfaces only the few that need a quick look from you.
Undisclosed security fixes
Patches that read like a vulnerability are held until you confirm it's safe to disclose.
Held for your reviewInternal codenames
“Project Lighthouse” never ships to customers — it waits for the name they'll actually recognize.
Held for your reviewWork behind feature flags
Anything still gated stays unannounced until you actually roll it out.
Held for your reviewEverything safe ships on its own — so you stay in control of the moments that matter, and nothing else gets in your way.
The honest answers.
Your last release deserved an announcement.
So will your next one.
Already have an invite? Sign in with GitHub