Developer communities on Reddit are among the most hostile to marketing, and their rules say so. Most big programming subreddits ban product promotion and restrict project posts to a weekly thread or a flair, and more of them now ban AI-written content. The tools that get attention answer real problems with working fixes, disclose their affiliation, and have docs and a repo ready before anyone asks.
This guide covers what ten programming and infrastructure subreddits say about projects as of 3 November 2026. It compares Reddit with Show HN and shows how to answer a technical question with a real fix and how to write a launch post that survives. The last part covers how developers find tools through Reddit and AI answers, and how to measure results without vanity numbers.
Key takeaways
- r/programming bans "I made this" demos and wants technical write-ups. r/devops puts self-promotion in a weekly thread and wants affiliation disclosed at the top. r/kubernetes sends new tools to a weekly thread. Read each rules page before you draft anything.
- Many developer subs also ban AI-generated content. r/golang, r/cpp, r/java and r/webdev all say so in their rules, so write your own posts.
- Show HN and Reddit work differently. Show HN has one set of guidelines, for something people can try. Reddit has a different rule set in every subreddit.
- The reliable approach is to answer questions with a real fix: the cause, the commands, how to verify it, and its limits. Mention the tool last, if at all.
- Get the docs, a repo and an install path ready first. r/selfhosted wants promoted apps to be "production ready" with docs.
- Measure with docs and repo traffic, installs, a signup question and branded search. Stars and upvotes are weak signals.
How to promote developer tools on Reddit
If you want to know how to promote developer tools or devtools on Reddit, the answer is mostly a list of things not to do. The sections below go through each step.
- Read each programming subreddit's rules first. r/programming bans "I made this" demos and wants technical write-ups. r/devops puts self-promotion in a weekly thread and wants affiliation disclosed at the top. r/kubernetes sends new tools to a weekly thread.
- Write your own posts. r/golang, r/cpp, r/java and r/webdev all restrict AI-generated content.
- Get the docs, a repo and an install path ready before you post. r/selfhosted wants promoted apps to be "production ready" with docs.
- Answer questions with a real fix: the cause, the commands, how to verify it and its limits. Mention the tool last, if at all.
- Launch only where the subreddit allows it, using its own template, with disclosure in the first line.
- Measure with docs and repo traffic, installs, a signup question and branded search. Stars and upvotes are weak signals.
Do that and you can market developer tools on Reddit without the thread turning into a debate about your motives.
Why developers are hard to market to
Developers distrust vendor content and go to their peers instead. They have also seen the spam. An r/devops thread titled "[Mod Request] Do something about rampant blatant advertisements disguised as 'discussions'" reached 249 points in February 2026. The poster wrote that they now "immediately assume a post is a secret advertisement" (a r/devops poster, 23 February 2026). A commenter added: "The last thing I posted here was a legit question and before anyone commented on it, I got two DMs - one seemed like a bot, the other was a soft-sell for their competing product" (a r/devops commenter).
Readers judge your post against that. To get past it, do the opposite of what the poster describes: no pretend question, no bot replies, no DMs, and a real person answering who says who they work for.
Where developers talk, and what the rules say
We read these on 3 November 2026 from each subreddit's published rules and took member counts from Reddit the same day. Rules change, so check the live page before you post.
| Subreddit | What it is for | Stance on projects and promotion | Rules page |
|---|---|---|---|
| r/programming (6.9M) | General programming news and discussion | No product promotion or "I Made This" demos. Technical write-ups on what makes a project hard or interesting are allowed. "We don't care what you built, we care how you build it" | rules |
| r/webdev (3.3M) | Web development | Commercial promotion not allowed. Projects only on Showoff Saturday ("Think project, not product"). LLM-generated posts and comments are low effort | rules |
| r/devops (520k) | DevOps practice | Self-promotion goes in the weekly thread. Any affiliation must be disclosed at the top of a post or comment. Posts should not funnel traffic to external blogs | rules |
| r/kubernetes (215k) | Kubernetes | New tools only as a comment in the weekly "Show off your new tools and projects" thread. Commercial affiliation must be stated. No obvious AI articles | rules |
| r/selfhosted (865k) | Self-hosting | Promoted apps must be production ready and have docs. Projects under three months old only in the New Project Megathread | rules |
| r/docker (324k) | Docker and containers | Promotion needs prior mod approval. Shared projects must be over three months old and Docker-related | rules |
| r/Python (1.5M) | Python | No standalone showcase posts. Use the monthly showcase thread, with sections for what it does, target audience and comparison | rules |
| r/golang (382k) | Go | Open-source libraries and Go-targeted dev tools are on topic. Closed-source or paid software not aimed at Go developers is not. No AI-generated content. Projects have their own rules | rules |
| r/dotnet (247k) | .NET | Promotion only on weekends, with the Promotion flair, not AI-written, and limited to major or minor releases | rules |
| r/opensource (398k) | Open source news | Promotion allowed to a degree, flaired Promotional. Not a "link farm". Under 10% of your posts, with some leniency | rules |
Two more. r/sysadmin lets vendors discuss their product when it fits an existing discussion and requires them to disclose any affiliation, but it counts posting from your own blog as a product (rules). r/typescript requires a project to be open source with a link to the repo, in the same rule that bans general advertising (rules).
Between them, these rules ask three things of a project: it exists, people can try it, and it has docs. The post rule checker flags a draft against a sub's current rules: try the post rule checker. The 9:1 rule explains why most of your activity should not be about you.
AI-written posts are banned in many of these subs
If you plan to draft with a model, read the rules first. r/golang says "No GPT or other AI-generated content is allowed as posts, post targets, or comments". r/cpp says "DON'T use AI to 'polish' or translate your words". r/java calls itself an "AI free zone". r/webdev counts LLM-generated posts and comments as low effort. r/devops lists AI content and stealth marketing as low-quality. Our app drafts replies that you post yourself. In these subs, treat any draft as notes and write the final text in your own voice.
Show HN versus Reddit
Show HN's guidelines define a Show HN as something you have made that other people can try. Blog posts, sign-up pages and newsletters are listed as off topic, and landing pages and fundraisers shouldn't be posted at all. They ask you to make it easy to try, "ideally without barriers such as signups or emails". Updates like "Foo 1.3.1 is out" are generally not substantive enough. HN's general guidelines add: "Don't solicit upvotes, comments, or submissions", and "Please don't use HN primarily for promotion."
Reddit has no single page like that. Each sub sets its own rules, so the same project can be welcome in one and removed from the next. Reddit is harder to learn as a result, but there are also more places your project can fit. A project that isn't ready for a Show HN may suit r/selfhosted's New Project Megathread or Showoff Saturday in r/webdev. If you post to both, write a separate post for each audience, and never ask friends to upvote on either.
Technical credibility before any launch
Before you post, do the work that gets a skeptical reader to trust you.
- Ship docs and a repo that stand on their own: a README that explains the problem, a one-command install, a runnable example and the known limits. r/selfhosted wants docs. r/typescript wants the repo link.
- Show your method with any benchmark. If you quote a number, say what you measured, on what hardware, against what, and where you lose. People pick apart a number with no method behind it.
- Compare honestly. Say what already exists and when someone should use it instead.
- Keep the issue tracker clean, because people will check it. Answered issues and a recent commit help more than a polished landing page.
- Post as a person, not a brand. Use a maintainer or engineer account with a visible history in the community. Our guides on warming up a Reddit account safely and brand versus personal accounts cover the account side.
Answer with a real fix
The most reliable way to earn standing is to answer questions in your area with a fix that works.
A worked example
This is a hypothetical illustration, not a client result. A thread in r/devops asks why Prometheus memory keeps growing. The engineer works at an observability vendor, so they disclose that first, as r/devops requires.
Disclosure: I work on an observability product, so weigh this accordingly.
Growing memory in Prometheus is usually series count (cardinality), not scrape volume. In the UI, open Status > TSDB Status and look at the series counts by metric name and the label names with the most values. The usual culprit is a label like a user ID, a request path with IDs in it, or a pod UID.
To drop a label at scrape time:
metric_relabel_configs: - action: labeldrop regex: user_idTo verify, watch
prometheus_tsdb_head_seriesafter the reload. It should stop climbing, and memory settles once older blocks are cut.Limit: if dropping the label makes two series identical you'll get duplicate sample errors, so check that first. If you need that label for debugging, keep it on a short-lived metric instead.
The answer has no product mention, no link and no pitch. If someone asks a follow-up where the tool is relevant, you could add one line then, since you've already disclosed. Our thread finder can surface threads like this. You write the answer yourself.
Launch and changelog posts that survive
Where a sub allows launches, follow the template it already asks for. r/Python's showcase rules require sections on what the project does, who it is for, and how it compares. r/kubernetes asks that affiliated posts provide value independent of the product, share honest insights, and avoid "problem/solution" setups where the product is always the answer. r/dotnet only allows promotion for major or minor releases. Show HN says "Foo 1.3.1 is out" is generally not enough, so don't post every patch.
The posts that tend to survive read like the technical write-ups these subs say they want. One r/kubernetes post reached 120 points in April 2026 (r/kubernetes thread). It was laid out as background, what was done, results and caveats, and it ended with an offer to share the manifests. The replies asked about disk limits and failure handling. That's the exchange you want, so state the limits up front and let people test them.
A checklist for a launch:
- Disclosure in the first line.
- One sentence on what it does, and a second on who it is for and who it isn't for.
- A short comparison that names the alternatives and says where each one wins.
- Install steps and a runnable example, in the post or one click away.
- The benchmark method, with the numbers.
- A promise to answer questions, and then answering them for the first day.
- The weekly thread or flair the sub asks for. A launch post that gets removed teaches you nothing.
How developers find tools through Reddit and AI answers
A developer hits an error or has to make a choice, searches, and lands on a thread. If an answer there solves the problem, they trust it. Then they check your README and last commit, and try it. Reddit threads also feed AI answers. Ahrefs found ChatGPT retrieves Reddit constantly but rarely cites it by name. A tracker reported its Reddit citation share falling in August 2026, which we cover in does ChatGPT cite Reddit. In Ahrefs' study of 75,000 brands, branded web mentions correlated 0.664 with AI visibility, against 0.218 for backlinks. A useful answer that names your tool honestly counts as a mention.
Seeding posts for AI visibility is a separate bet, and we wrote it up in we posted on Reddit for GEO and nothing happened. Answer for the developer in the thread first.
Measuring the result
- Docs and repo traffic from reddit.com referrers.
- Installs and downloads over time, with the date of each post marked.
- A signup question, "How did you hear about us?", with Reddit as one of the options.
- Branded search in Search Console.
GitHub stars and upvotes are weak signals. They can be gamed, and you shouldn't game them. Don't buy accounts, stars or votes. See buying Reddit accounts and upvotes.
Pre-post checklist
- I read the sub's rules and wiki today, including any weekly thread, flair or megathread.
- I'm posting as a named person, and the first line discloses my affiliation.
- I wrote it myself, and the sub doesn't ban what I'm doing with AI.
- The reply would help someone even without my tool.
- Docs, repo, install and a runnable example are all live.
- Any numbers have a method behind them, and I say where the tool loses.
- I haven't asked anyone to upvote, star or comment, and nobody on my team will.
- I'll be around to answer questions for the next day.
Mistakes and what happens
| Mistake | What usually follows |
|---|---|
| A "what tool should I use" thread seeded to be answered by your own accounts | Exposure. The r/devops thread above describes exactly this pattern |
| A launch post in a sub that confines projects to a weekly thread | Removal, and the thread has your name on it |
| Posting every patch release | Ignored or removed. r/dotnet limits promotion to major or minor versions |
| An AI-written post in r/golang, r/cpp or r/java | Removal or a ban, since their rules prohibit it |
| Quoting benchmarks with no method | The thread becomes a debate about your method |
| Launching without docs | r/selfhosted expects docs. Readers leave |
A four to eight week plan for a developer tool
This puts the sections above in calendar order. It assumes a maintainer or engineer posts from an account with visible history in the community.
| Weeks | Do | Check |
|---|---|---|
| 1 to 2 | Read the rules of 6 to 10 subreddits. Get the README, one-command install, runnable example and known limits in order. Clean up the issue tracker | Can a stranger install and run it in one sitting? |
| 3 to 4 | Answer technical questions with a real fix from a maintainer account. No tool mention unless someone asks | Does each answer include the cause, the commands and how to verify? |
| 5 to 6 | Write one technical write-up (background, what was done, results and caveats, with the benchmark method) for a sub that wants it | Does it work if your product name is removed? |
| 7 | Post your launch in the thread or flair the sub asks for, using its template, with disclosure first. Stay for the first day of questions | Did you answer everyone, including the critical comments? |
| 8 | Review docs and repo referrals, installs after each post date, signup answers and branded search. Compare with any Show HN post. Drop subs that returned nothing | One page: what worked, what did not, what you will stop |
Reddit marketing agency for devtools and developer tools: what you get
Disclosure: we sell this service, so read this section as our own description and not as a neutral review.
Developer communities are the hardest place for an agency to work. The credible voice is an engineer who knows the product, so we build the work around your maintainers. An engagement starts with an audit of the subreddits where your developers talk, their rules, and where competitors and alternatives already show up. That becomes a written strategy: which subs, which thread types, and which of your engineers writes what. We find the threads and do the reporting. Where a subreddit expects a maintainer's own words, your engineer writes and posts them.
We are a done-for-you, white-hat agency, mostly for funded B2B SaaS, fintech and DTC brands. If you sell a developer tool, tell us what it does on the call and we will say whether Reddit fits. We don't buy upvotes, stars or accounts, and we don't farm karma. See how a campaign works, the Reddit marketing agency page and our case studies.
Reddit marketing services for devtools and developer tools: agency, in-house or app
| Option | Who does the work | Fits when | Watch out for |
|---|---|---|---|
| Agency (done for you) | An outside team plans, finds threads and reports, with your engineers writing where needed | You are funded and your engineers have no time to read threads | Subs that ban AI text and promotion mean the final words must be yours |
| In-house | A maintainer or developer advocate, from a personal account with history | Someone on the team can answer technical questions in public | Brand accounts are distrusted, and launching without docs loses readers |
| Self-serve app | You, with a tool that finds threads and drafts notes | You want the searching and rule-reading done faster | On Starter the tool never posts for you. In subs that ban AI text, treat any draft as notes |
We don't publish prices. Every engagement starts with a call. How Reddit marketing agency pricing works shows what other agencies publish, with dates and sources.
How the app helps
The Subreddit Marketing app finds threads where developers describe a problem and drafts rule-aware replies. It never sends DMs for you. On the Done for you plan we can also post replies through our warmed-up accounts and add upvotes to your posts and comments. In subreddits that ban AI-generated content, use the draft as notes and write the final text in your own voice. The thread finder shows the kind of threads it surfaces, and you can start the app when you are ready.
Where to go next
For a broader view, see Reddit marketing for SaaS and Reddit marketing for startups. All the verticals are on the use cases page.
The basics are in what Reddit marketing is and the Reddit marketing guide. To talk to us, book a call.
Frequently asked questions
Can I promote a developer tool on r/programming?
Not as a product or an "I made this" demo. r/programming allows technical write-ups about what makes a project technically challenging or educational, and the write-up has to be the focus of the post. If you can't write that without the product being the point, post somewhere else.
Where can I share a new open-source project?
It depends on the sub. Examples from the rules: Showoff Saturday in r/webdev, the monthly showcase thread in r/Python, the weekly tools thread in r/kubernetes, the New Project Megathread in r/selfhosted, and the Promotional flair in r/opensource. The rules change, so read the live version.
Should I disclose that I work on the product?
Yes, at the top. r/devops requires affiliation at the top of a post or comment, and r/kubernetes requires it from employees, founders, maintainers and investors. Developers trust a vendor who says so up front more than one whose affiliation turns up later.
Is Show HN better than Reddit for launching a tool?
They do different jobs. Show HN suits something people can try right now, and it runs under one set of guidelines. Reddit suits a specific community that has its own rules and a place for your project. Plenty of teams use both, with a separate post for each and no vote requests.
Can I use AI to write my posts and replies?
Check each sub first. r/golang, r/cpp, r/java and r/webdev explicitly restrict AI-generated content, and r/devops treats it as low quality. Write the post in your own words. If you use a model at all, use it for notes.
How do I know a Reddit post helped?
Look at docs and repo referrals, installs after the post date, answers to "how did you hear about us", and branded search. Stars and upvotes aren't proof, and inflating them is off the table.
How to market developer tools on Reddit?
Read each programming subreddit's rules, answer questions with a real fix, and disclose who you work for. Launch only in the thread or flair a sub provides, using its template. Have docs, a repo and an install path ready first, and write your own posts.
How to market devtools on Reddit without getting removed?
Don't post "I made this" demos in subs that ban them, and keep patch releases out of launch threads. Put your affiliation in the first line, share the benchmark method with any number, and say where your tool loses.
Is Reddit marketing for devtools worth it when subs ban promotion?
It can be. Many subs ban product promotion, but answering questions with a real fix, and writing technical write-ups where subs ask for them, still reaches developers. Measure with docs and repo traffic, installs, a signup question and branded search.
What does a Reddit marketing agency for developer tools do?
It audits the subreddits where your developers talk, writes a strategy, finds the right threads and reports on results. Developer subs expect an engineer's own voice, so a good agency works with your maintainers instead of posting for them.
Do you offer Reddit marketing services for developer tools?
Yes, for funded teams. We run a done-for-you Reddit marketing agency and a self-serve app for in-house teams. Every engagement starts with a call, and we don't publish prices. See the [agency page](/services/reddit-marketing-agency).