Every release you ship, turned into
an X thread.
DevRelay is an AI DevRel for dev-tool teams. It watches your GitHub, waits for the actual release, and drafts the posts, changelog and docs update in your voice. You approve; it publishes.
No credit card · Nothing posts without your approval
Reads your GitHub. Writes for every channel you announce on.
- GitHubwatches
- Xposts
- LinkedInposts
- Slackalerts
- Changelogmarkdown
- Docsmarkdown
Your team ships every week. Your changelog says otherwise.
The work gets merged, tagged and deployed. Then nobody writes the post, the changelog entry waits for someone with an afternoon free, and the docs page still describes last quarter's API.
- Features ship to silence while louder competitors look faster.
- Users open issues asking for things you already built.
- Generic AI writers invent APIs and call beta features GA, so nobody trusts them.
| Shipped | Post | Changelog | Docs |
|---|---|---|---|
Stream() for incremental query results go-sdk v2.8.0 | |||
insert_many() with batching python-sdk v1.14.2 | |||
Branch-aware connection strings api 2026.09 | |||
Retry policy for idempotent writes ts-sdk v3.2.0 |
Connect once. Review drafts when a release ships.
Onboarding is one short flow. After that DevRelay works from your GitHub activity, and the only step that needs you is the last one.
- 01
Connect
Install the GitHub App, pick the repos to watch and add your website. DevRelay reads your site, docs and blog to learn the product and how you talk about it.
- 02
Watch & decide
Every PR, release and issue is filtered and scored. Dependency bumps, typo fixes and test-only changes are dropped, and you can see why.
- 03
Draft & check
For changes worth announcing it gathers evidence from the diff, issues and docs, drafts each channel and runs hard checks before you see anything.
- 04You
You approve
Review in the inbox, edit if you like, approve. X and LinkedIn post now or on schedule; changelog and docs drafts export as Markdown.
Merged isn't released. DevRelay knows the difference.
Announce a pull request the moment it merges and sooner or later you announce something users can't install yet. DevRelay holds merged work until a GitHub release ships it.
Ship from a branch instead of tags? Put the repo in branch mode and a merge into your release branch counts as the release. A plain push never does.
- Tue 14:02Held: waiting for releasePR #1832 mergedgo-sdk: add Stream() for incremental query results
- Tue → ThuHoldingNothing drafted, nothing postedMerged code can still be reverted or changed before it ships.
- Thu 10:15ReleasedRelease v2.8.0 publishedThe release event is what unlocks public content.
- Thu 10:19Ready for reviewDrafts in your inboxX post, LinkedIn post, changelog entry, docs patch, tutorial, image brief.
Every claim traced to evidence. Checked before you read it.
Drafts are written from evidence gathered for that change: the diff, the release notes, linked issues and your docs. Then every draft runs through hard gates. If one fails, DevRelay repairs the draft or holds it back.
Claims with receipts
Each factual claim in a draft is listed with the evidence that supports it. Anything without support is flagged before it reaches you.
No invented APIs
Function names and versions that aren't in the evidence fail the technical gate. A beta SDK is never called GA, and unreleased work never reads as shipped.
No hype
“Revolutionary”, “game-changing” and unsupported “world's first” or funding claims fail review. Developers get facts and a code sample.
One release in. Every channel drafted.
These are the unedited drafts DevRelay wrote for one release in our demo workspace, FluxDB, a sample database company. Go SDK v2.8.0 added aStream()method.
Go SDK v2.8.0 adds Stream() for incremental query results.
Stream() returns *Rows backed by a server-side cursor.
Release notes → github.com/fluxdb/go-sdk/releases/tag/v2.8.0
Sounds like your team, and gets closer with every edit.
During setup DevRelay reads your website, docs and blog to build a brand profile: tone, phrases you use, phrases you avoid, your colours and logo. Add your own instructions per channel. When you edit a draft, it learns the pattern and applies it next time.
Approve in the inbox. It's already on the calendar.
Drafts for one change arrive together. Approve them one at a time or all at once, then publish now or pick a slot. Connected X and LinkedIn accounts post at that time on their own.
Drag to reschedule
Month and week views. Blog, changelog and docs entries sit on the same calendar as planned items for whoever ships them.
Approval binds to the exact version
Edit a draft after approving it and the old approval goes stale. What posts is what someone approved.
A Slack ping when drafts are ready
Pick a channel and DevRelay tells it when something needs review. Approving happens in the app.
Built so it can't embarrass you.
You can also run it in observe mode, where it decides and explains without drafting, or pause monitoring entirely and choose what happens to the backlog when you resume.
Waits for the release
Merged work is held until a release ships it. Pushes never count.
Security fixes stay quiet
Security-sensitive changes are blocked from public drafts. Only an admin can override, with a written reason that is logged.
Nothing posts unapproved
No approval, no post. Every approval matches one version and content hash.
Secrets redacted
Tokens and keys in PRs or docs are stripped before any model sees them or anything is stored.
Your repo can't steer it
PR text, READMEs and web pages are treated as data, never as instructions, so a crafted PR description can't hijack a draft.
Never double-posts
Each version publishes to a channel once, even if a job retries or a webhook arrives twice.
“Couldn't I just paste the PR into ChatGPT?”
You could. Someone still has to notice the release, find the PR, paste in the context, fix the invented method name, strip the hype, and do it again for every channel. That's why it doesn't happen.
DevRelay does the part nobody owns: noticing, deciding, grounding and checking. You keep the part that matters, the yes.
| DevRelay | ChatGPT | DevRel hire | |
|---|---|---|---|
| Notices what shipped without being asked | |||
| Waits until it's actually released | |||
| Checks each claim against the code | |||
| Knows your product, voice and past posts | If you paste it in | ||
| Drafts X, LinkedIn, changelog and docs together | One prompt at a time | When there's time | |
| Posts on schedule after approval | |||
| Cost | $999/mo | Your engineers' time | A full salary + ramp |
Try it on your repos for free.
Connect your repos and see what DevRelay would write about your recent releases before you pay anything.
Free
Watch, draft and review
- GitHub monitoring and change scoring
- Drafts for every channel
- Hard gates, claims and rubric on every draft
- Approval inbox and Slack alerts
- Up to 3 knowledge sources
- Publishing, Markdown export and scheduling
DevRelay
Full DevRelWatch, draft, approve and publish
- Everything in Free
- Unlimited knowledge sources
- Post to X and LinkedIn on approval
- Scheduling and the content calendar
- Markdown export for changelog, docs, blog and tutorials
- Export launch image briefs and video scripts
Billed monthly per organization. Change plans any time from Settings. Compare plans in detail
Questions teams ask before connecting their repos.
Something else? Sign up and look around: the free plan shows you exactly what DevRelay would draft before anything can go out.
01Does DevRelay post anything on its own?
No. Nothing is published without a human approving that exact version. After approval, X and LinkedIn posts go out immediately or at the time you scheduled. Changelog, docs, blog and tutorial drafts are exported as Markdown for you to commit or paste into your CMS.
02Will it announce something that isn't released yet?
No. Merged pull requests are held until a GitHub release ships them. If you release from a branch instead of tags, set the repo to branch mode and a merge into that branch counts as the release. A plain push never does.
03What happens with security fixes?
Security-sensitive changes are marked BLOCK and never drafted automatically. They show up on your Today page for a human to decide. An admin can still ask for a draft, with a written reason that is logged.
04How does it avoid making things up?
Drafts are written from evidence collected for that change: the diff, release notes, linked issues and your docs. Every draft then goes through hard gates. Claims without evidence, API names or versions that don't appear in the evidence, beta features called GA, and unsupported "first" or funding claims all fail, and the draft is repaired or held.
05Which AI models does it use, and what do they see?
DevRelay routes each task to a model by role: one decides what's worth announcing (it never writes prose), one extracts facts, one writes. Secrets are redacted before any model call, and content from your repos and websites is always treated as data, not instructions.
06What does it need access to?
You install the DevRelay GitHub App and choose which repositories it watches. You add your website, docs and blog as knowledge sources. X, LinkedIn and Slack are optional and connect with their own sign-in flows. You can disconnect any of them from Settings.
07Does it open pull requests on my docs repo, or make images and videos?
Not yet. Docs updates come as a Markdown diff you can apply, launch images come as a design brief built from your brand, and launch videos come as a script. We say so in the app too.
08How is this different from a changelog or release notes generator?
A generator turns commits into a list. DevRelay decides which changes deserve an announcement at all, waits for the release, writes for each channel in your voice, checks every claim against your code, and learns from your edits.
09Who is it for?
Dev-tool companies that ship often: APIs, SDKs, databases, infrastructure and open source. It fits best when you have no DevRel hire, or one person covering docs, community and social.
Your next release deserves more than a merge commit.
Connect GitHub and your website. The next time you ship, the post, the changelog entry and the docs update will be waiting for your yes.
No credit card · Nothing posts without your approval