Acme 3.0: realtime, everywhere
Live collaboration on every document, pages that load twice as fast, and Markdown in and out of the editor.
launchv3
Release notes · Pro & Team
Release notes that live next to your changelog
The changelog says what changed. Release notes tell the story — why it matters, how to use it, what comes next. Changelore publishes both from one place, on one domain, to one audience.
acme.com/notes
Acme
What’s new in Acme
ChangelogRelease notes
How we rebuilt search from scratch
A look inside the new index — and the three things you can now find in one query.
Stop running a blog next to your changelog
Most teams end up running two tools: a changelog for the small stuff and a blog — Ghost, WordPress, a Notion page — for the big launches. Two places to update, two audiences to grow, and two sets of links that never point at each other. The people who subscribed to your changelog never hear about the launch post, and the launch post never links back to the details.
One home for every update
Release notes get their own section on your public page, with a Changelog · Release notes switcher at the top. Same logo, same brand colour, same custom domain — at /notes.
Drafted from the changelog you already wrote
The draft_release_notes MCP prompt has your agent read your published entries and turn them into a long-form post. It never invents a feature that is not in the changelog, and it saves a draft — publishing waits for you.
A real long-form editor
Cover image, excerpt, headings, images, video embeds, tables and code blocks. Write in the editor, or send Markdown over the API and let the server convert it.
Delivered, not just posted
Subscribers get an email the moment a post goes live, a post.published webhook drops a card into Slack or Discord, and release notes have their own RSS feed, separate from the changelog’s.
Built to be found
Opt a project into indexing and every post is server-rendered at the edge for crawlers, with a clean permalink that is frozen once published and a canonical URL on your own domain.
Yours to take anywhere
Every published post is in the public read API as sanitized HTML or Markdown. Render your release notes inside your own site or docs with your own components.
Your agent writes the first draft
Release notes are the summary of a quarter’s changelog — so the agent starts from what you already published, not from a blank page.
Ask your agent for a launch post
> Use draft_release_notes for acme,
> covering everything since September 1.
Agent → list_changelogs (14 published entries)
→ create_post (draft)
# Acme 3.0: realtime, everywhere
excerpt: Live collaboration, faster pages,
and Markdown in and out.
Draft saved. Publish it when you're happy.Changelog vs release notes
They answer different questions for different readers. Most products need both — and they work best side by side.
| Aspect | Changelog | Release notes |
|---|---|---|
| Length | A few lines per entry | A full article with a cover image |
| Cadence | Every time you ship | Big launches, a few times a quarter |
| Answers | What changed? | Why does it matter, and how do I use it? |
| Read by | Your active users | Users, prospects and press |
| Lives at | /p/your-slug | /p/your-slug/notes |
Questions
- What is the difference between a changelog and release notes?
- A changelog is a dated list of what changed, kept short and published every time you ship. Release notes are long-form posts for the bigger moments — they explain why a change matters and how to use it. Changelore publishes both on the same public page, as two separate sections with two separate feeds.
- Do I still need a separate blog for product launches?
- Not for product news. Release notes give each launch a full article with a cover image and permalink, on the same domain and under the same brand as your changelog, and email it to the subscribers you already have.
- Can my AI agent write release notes?
- Yes. Over MCP your agent can list, create, update and publish posts, and the draft_release_notes prompt guides it from your published changelog entries to a draft. Publishing needs the publish scope, so you can let an agent draft and keep the final say yourself.
- Do subscribers get an email when I publish release notes?
- Yes. Your changelog subscribers are emailed when a post goes live, and any webhook subscribed to post.published fires at the same time — including ready-made Slack and Discord cards.
- Will search engines index my release notes?
- If you opt the project into indexing, yes — each post is server-rendered at the edge with its own title, permalink and canonical URL, and served on your custom domain when you have one. Private projects are never rendered or indexed.
- Can I schedule a post for launch day?
- Yes. Give a post a publish date over the API or MCP and the scheduler publishes it when the time comes, sending the emails and webhooks then rather than when you wrote it.
- Which plan includes release notes?
- Release notes are part of Pro and Team. If you ever downgrade, everything you already published stays online — only writing new posts is paused.
See who else Changelore is for in use cases, or how the MCP server writes the changelog itself.
Changelore is launching soon
The changelog written from your code. Join the waitlist for early access.
Join the waitlist