# DevRelay

> DevRelay watches your GitHub, waits for the release, and drafts posts, changelogs and docs updates in your voice, checked against your code. You approve.

DevRelay is an AI DevRel employee for SaaS and developer-tool teams. It watches a company's GitHub (pull requests, releases, issues) plus its website, docs and blog, decides which changes deserve content, and drafts X posts, LinkedIn posts, changelog entries, docs updates (as GitHub pull requests), launch images and launch video scripts. Drafts are grounded in the company's own code and docs, checked before review, and wait in an approval inbox: nothing is published without a person approving it.

Key facts:
- Release-aware: a merged pull request is held until it ships in a release (or merges into the release branch in branch mode).
- Every claim in a draft is checked against official evidence; drafts never name versions or link to GitHub.
- Between releases: a feature catalog built from the company's docs and website, ideas (how-tos, tips, use cases, FAQs) and an optional weekly plan that fills only the posting slots releases left free; ideas are never written as news.
- Hosted changelog page (DevRelay plan): approved changelog entries publish to a page at updates.devrelay.so/<company> or the company's own subdomain, with RSS and JSON feeds, a sitemap and a What's new widget. No roadmap, feedback board or subscriber email.
- Weekly and monthly recaps (a "What shipped" post, X thread, LinkedIn post and a newsletter a person copies into their email tool), and a look-back that drafts posts from the last 60 days on day one.
- Product Hunt launch kit: listing, maker's first comment, gallery, thumbnail, launch-day posts, blurbs and a runbook; a person posts everything.
- Clips: short educational videos of the company's AI avatar, made by DevRelay's team within 24 hours of approving a topic (10 a month on the DevRelay plan); the customer downloads and posts them.
- Listening on Hacker News, X and GitHub with reply drafts that a person posts (DevRelay never posts community replies itself).
- MCP server at https://api.devrelay.so/mcp (Streamable HTTP) for Claude.ai, Claude Desktop, ChatGPT (OAuth sign-in), Claude Code, Cursor and VS Code (personal tokens): read the workspace, draft and edit, and approve, publish or schedule only after the person confirms each time in their AI tool. Read tools on the free plan; everything, plus Ask (a chat page inside DevRelay over the same tools), on the DevRelay plan.
- Plans: Free (connect, watch, draft and check; 3 sources) and DevRelay at $999 per month per organization (publishing to X and LinkedIn, scheduling, docs pull requests, launch images, launch videos and clips, listening, the full MCP server and Ask).
- Sign up: https://app.devrelay.so/sign-up

## Product

- [Launch posts](https://devrelay.so/launch-posts): X and LinkedIn posts for every release
- [Changelog](https://devrelay.so/changelog-generator): Grouped entries, written from the release
- [Docs updates](https://devrelay.so/docs-updates): A docs pull request when a release outgrows your docs
- [Product Hunt kit](https://devrelay.so/product-hunt-launch): Listing, gallery, posts and a launch-day runbook
- [Ideas and weekly plan](https://devrelay.so/content-ideas): Posts about features you already have, between releases
- [Recaps and newsletter](https://devrelay.so/product-updates): Weekly and monthly roundups, and a newsletter to send
- [Clips](https://devrelay.so/ai-avatar-videos): Short videos of your AI avatar teaching your niche
- [Engage](https://devrelay.so/engage): Threads about you on HN, X and GitHub, with reply drafts
- [Reddit and HN posts](https://devrelay.so/reddit-hn-posts): Posts that teach, for the communities you pick
- [MCP server and Ask](https://devrelay.so/mcp): Ask, draft and approve from Claude, ChatGPT or Cursor
- [Pricing](https://devrelay.so/pricing): Free and DevRelay plans compared
- [Security](https://devrelay.so/security): how repository access, data and approvals are handled
- [DevRelay vs LaunchNotes](https://devrelay.so/vs/launchnotes): how the two compare and when LaunchNotes is the better fit

## Free tools

- [PR to X post generator](https://devrelay.so/tools/pr-to-tweet): Paste a GitHub pull request and get a multi-line X post and a 3 to 5 post thread about the change, written for your users. Works for private repos. Free.
- [PR to LinkedIn post generator](https://devrelay.so/tools/pr-to-linkedin-post): Turn a GitHub pull request into a LinkedIn post for your users: a hook that fits above "see more", what changed and how to use it. Free, no sign-up.
- [Release notes generator](https://devrelay.so/tools/release-notes-generator): Generate release notes from pasted commit messages or PR titles, grouped into new, improved and fixed and written for your users. Works for private repos.
- [Commit message generator](https://devrelay.so/tools/commit-message-generator): Paste git diff --staged and get a Conventional Commits message: type, scope, subject and body. Secrets are redacted before the model sees it. Free.
- [Show HN title generator](https://devrelay.so/tools/show-hn-title-generator): Write a Show HN title that follows Hacker News conventions: under 80 characters, plain, specific, no hype. Generate six options or check your own. Free.
- [Open Graph checker](https://devrelay.so/tools/open-graph-checker): Check a page's Open Graph and Twitter card tags, preview the link on X, LinkedIn and Slack, and get fixes for image size, missing tags and lengths. Free.
- [Which release shipped this PR?](https://devrelay.so/tools/github-pr-release-finder): Paste git tag --contains output for a PR's merge commit and get the first release that shipped it, or learn it isn't released yet. Runs in your browser.
- [X character counter and thread splitter](https://devrelay.so/tools/tweet-character-counter): Count characters the way X does (links are 23, CJK and emoji count double) and split long text into a numbered thread. Free, runs in your browser.
- [LinkedIn text formatter](https://devrelay.so/tools/linkedin-text-formatter): Free LinkedIn text formatter: bold, italic, underline, strikethrough and bullet points that paste into posts, with a "see more" preview. No sign-up.
- [Conventional commit checker](https://devrelay.so/tools/conventional-commit-checker): Check commit messages against Conventional Commits 1.0: type, scope, breaking-change marker, subject rules and footers. Free, runs in your browser.
- [Semver calculator](https://devrelay.so/tools/semver-calculator): Work out the next semantic version from Conventional Commits or a bump type, with pre-releases, and test a version against an npm range. In your browser.
- [Keep a Changelog generator](https://devrelay.so/tools/keep-a-changelog-generator): Turn Conventional Commits into a Keep a Changelog section for CHANGELOG.md: Added, Changed, Deprecated, Removed, Fixed and Security. Runs in your browser.

## Guides

- [Semantic Versioning (SemVer): Rules, Ranges and Examples](https://devrelay.so/blog/semantic-versioning): Semantic Versioning (SemVer) numbers a release MAJOR.MINOR.PATCH. Bump major when a change breaks something people depend on, minor when you add something without breaking anything, and patch for a backward-compatible bug fix, resetting the numbers to the right to zero. Pre-releases like 1.0.0-beta.2 sort before the release they lead to.
- [Reddit Monitoring Tools Compared (Plus Hacker News)](https://devrelay.so/blog/reddit-monitoring-tools): Reddit monitoring tools alert you when a post or comment mentions your brand, a competitor or a problem you solve. F5Bot does it free by email for Reddit, Hacker News and Lobsters. KWatch.io and Syften add Slack and more sources from $19 to $50 a month, suites like Octolens and Brand24 cover many networks, and RedShip and SignalReply also draft replies.
- [App Release Notes: App Store and Google Play Templates](https://devrelay.so/blog/app-release-notes): App release notes are the "What's New" text a mobile app shows for each update. Lead with the change people will notice, group the rest as New, Improved and Fixed, describe fixes by the symptom, and leave out version numbers and internal work. Google Play allows 500 characters per language and the App Store 4,000, so write the 500-character version first and it works on both.
- [Product Update Email Template: 6 Examples to Copy](https://devrelay.so/blog/product-update-email-template): A product update email needs a subject line that names the change, preview text that says why it matters, the one headline change first, a single step to take, and one line for everything else with a link to the changelog. Pick the template by what you need the reader to do: try a feature, skim a monthly update, notice a fix, understand a price change, act before a breaking change, or consider an upgrade.
- [Tools That Turn GitHub PRs Into X and LinkedIn Posts](https://devrelay.so/blog/github-pr-to-social-post-tools): Yes. ShipPost writes X and LinkedIn posts from a merged PR you pick, free with your own API key. Merge & Tell and Shipstar draft a post for every merge and post it after you approve. DevRelay waits for the GitHub release, drafts posts only for changes users would notice, and posts the version you approve. xpost lets a coding agent publish the post through its MCP server.
- [LinkedIn Post Format: Specs, Layout and 6 Templates](https://devrelay.so/blog/linkedin-post-format): A LinkedIn post is plain text with line breaks, up to 3,000 characters, plus one kind of attachment: photos, a video, a document, a poll or a link preview. Put the news in the first line (about three lines show before "see more"), keep paragraphs to one to three sentences with blank lines between them, use Unicode bold for a few words at most, and use 1,080 px wide images between 3:1 and 4:5.
- [How to Change a Git Commit Message (Last, Old or Pushed)](https://devrelay.so/blog/git-change-commit-message): Run git commit --amend -m "new message" to change the last commit's message. For an older commit, run git rebase -i HEAD~3, change pick to reword on its line, and write the new message when Git opens the editor. If the commit was already pushed, finish with git push --force-with-lease.
- [What Is DevRel? Developer Relations Explained](https://devrelay.so/blog/what-is-devrel): DevRel, short for developer relations, is the work of building a two-way relationship between a company and the developers who use its product. Outbound, it helps developers succeed through docs, tutorials, sample code, posts and community; inbound, it brings their feedback, bugs and requests back to the product team.
- [Changelog Examples: 11 Real Changelogs and What to Copy](https://devrelay.so/blog/changelog-examples): The best changelogs pick a reader first, then a shape. Linear leads each update with one headline feature and keeps fixes as short lists labelled by area; Raycast opens with a summary of what users will notice; Vercel gives every change its own post; GitHub and Supabase label each entry by type; Stripe ties entries to API versions and flags breaking ones; Tailwind's CHANGELOG.md links every line to its pull request.
- [Best Changelog Tools in 2026: 17 Compared by Type](https://devrelay.so/blog/best-changelog-tools): Changelog tools come in three kinds. Hosted tools like Beamer, Headway and AnnounceKit give you a page and an in-app widget, but you write every entry. Git-based generators like release-please, git-cliff and semantic-release build CHANGELOG.md from your commits for free. AI tools like ReleasePad, Changesmith and DevRelay draft the entry from your pull requests for a person to approve.
- [Conventional Commits Cheat Sheet: Types, Examples, Rules](https://devrelay.so/blog/conventional-commits-cheat-sheet): A conventional commit starts with a type, an optional scope in parentheses, an optional ! for a breaking change, a colon and a short description, like feat(inbox): add send later. feat adds a feature (a minor version), fix fixes a bug (a patch), and a ! or a BREAKING CHANGE: footer makes it a major version. Other types such as docs, refactor, test, build, ci and chore don't change the version.
- [Release Notes Template: 8 Copy-Paste Formats with Examples](https://devrelay.so/blog/release-notes-template): A release notes template needs five parts: a title that names the change, a one-sentence summary, anything that needs action first, then New, Improved and Fixed with one line per change, and a link to more detail. Pick the template by where the notes will be read: a product update, an email, an SDK release, an app store, a GitHub release, an internal note, a hotfix or a Confluence page built on what Jira generates. All eight are downloadable Markdown files.
- [How to Write a Changelog: Format, Examples and Template](https://devrelay.so/blog/how-to-write-a-changelog): A changelog is a curated list of the notable changes in each release, newest first, written for the people who use the product. A good one groups changes by type with breaking changes at the top. Each line describes the effect on users, not the implementation, and links to docs or issues. Commit logs, refactors and dependency bumps don't belong in it.
- [How to Announce a Product Release on X: 10 Post Formats](https://devrelay.so/blog/how-to-announce-a-release-on-x): Match the post to the change. Use a launch format for a big release, "You can now" or before/after for a feature, symptom-first for a bug fix, old-to-new numbers for performance and a heads-up for breaking changes. Lead with what changed, show proof such as a snippet or a number, name the version and link to the release notes.
- [Release Notes vs. Changelog: What's the Difference?](https://devrelay.so/blog/release-notes-vs-changelog): A changelog is a complete, cumulative list of notable changes in every version, written for developers upgrading. Release notes describe one release to its users: what's new, why it matters and what to do. Libraries can often get by with a changelog; products with a growing user base need both.
- [How to Automate Your Changelog From GitHub (5 Tools)](https://devrelay.so/blog/automate-changelog-from-github): Give each change a machine-readable type with Conventional Commits, PR labels or change files, then let a release tool group them, pick the next SemVer version and write the changelog. Use release-please if you want to decide when to release, semantic-release to release on every merge, Changesets for JavaScript monorepos and git-cliff for custom formats in any language.
- [Docs Drift: How to Keep Documentation in Sync With Your Code](https://devrelay.so/blog/keep-docs-in-sync-with-code): Keep docs in the same repository and review flow as the code, run code examples as tests, generate reference docs from the spec or source, check links and terminology in CI, and review each release's changelog against the docs before you tag it.
- [DevRel for Startups: How to Do It Without a DevRel Hire](https://devrelay.so/blog/devrel-for-startups): At a startup, DevRel is making sure every release reaches the developers who'd care: announce it where they are, document it before they ask, and listen to what comes back. Give it an owner and a fixed weekly slot, skip events and ambassador programs early, and hire a developer advocate to scale a loop that already works.

## Company

- [About](https://devrelay.so/about)
- [Privacy](https://devrelay.so/privacy)
- [Terms](https://devrelay.so/terms)
- Contact: support@devrelay.so