Can you actually market a developer tool on Reddit and Hacker News without getting banned?
Yes, but only by reversing the usual marketing instinct: you earn attention by being useful in the community first and mentioning your product second, rarely, and only when it's genuinely relevant. Both platforms have sophisticated, mostly volunteer moderation and a userbase that actively hunts for self-promotion — the tolerance for anything that reads as marketing is close to zero unless the value-to-promotion ratio is heavily skewed toward value.
This isn't a soft "be authentic" platitude, it's an operational rule with teeth. Reddit's automated spam filters and human moderators shadow-ban accounts that post links to the same domain repeatedly with low karma and no comment history. Hacker News has an unwritten but well-enforced norm against anything that smells like a "growth hack," and the community will flag and downvote a post into oblivion within minutes if it reads as promotional, regardless of how good the underlying product is. We've watched genuinely excellent developer tools get buried on HN because the submission read like a press release, and we've watched mediocre side projects hit the front page because the founder showed up, answered every technical question honestly, and didn't oversell.
The upside is real: a well-received Show HN or a genuinely helpful Reddit comment thread can drive more qualified developer signups in a day than months of paid acquisition, because the traffic arrives pre-qualified by peer endorsement rather than an ad impression. This guide covers the culture rules for each platform, how to post value-first, the specific mechanics of a Show HN launch, how to monitor these communities for organic opportunities, and how to convert that traffic without triggering the exact behavior that gets you banned.
What are the unwritten culture rules on Hacker News that most marketers get wrong?
Hacker News rewards technical substance, first-person founder voice, and intellectual honesty about tradeoffs and limitations, while punishing anything that reads as written by a marketing team, exaggerates results, or avoids answering hard questions in the comments. The community's collective radar for corporate-speak is extremely well calibrated, and triggering it once often means every future submission from your domain gets extra scrutiny.
The most common mistake is submitting a blog post or landing page instead of something with real technical content — a specific implementation detail, an honest post-mortem, an open-source tool with real code behind it. HN's front page skews heavily toward "I built this and here's exactly how, including the parts that didn't work" over "our platform helps you achieve X." If your submission could have been written by a copywriter who's never touched your codebase, it's already fighting an uphill battle regardless of the product underneath it.
The second most common mistake is disengaging after posting. HN comment threads are where submissions actually live or die, and the community expects the submitter to show up, answer technical questions directly, concede valid criticism, and avoid defensive marketing language in responses. A founder who responds to "this won't scale past 10k requests/sec" with genuine technical detail about where the bottleneck actually is earns more credibility than one who responds with "great question, we're always improving performance!" The second answer reads as evasive to a technical audience, and it usually gets called out explicitly in a reply.
The third mistake is timing and framing your post around a funding announcement, a rebrand, or any other event that centers your company rather than a technical or intellectual contribution. "We raised a Series A" gets a fraction of the engagement of "we hit this specific technical wall building our product and solved it this way," even when the underlying company and product are identical — because the second framing gives the community something to engage with intellectually.
What are the unwritten culture rules on Reddit for developer-focused subreddits?
Developer-focused subreddits like r/programming, r/webdev, and language- or framework-specific communities enforce strict self-promotion ratios, typically expecting genuine, non-promotional participation to vastly outweigh any mention of your own product, and most have explicit rules capping self-promotional posts to a small fraction of your total activity, sometimes enforced by automated tracking.
Unlike Hacker News, which is a single community with a fairly unified culture, Reddit is hundreds of separate subreddits each with their own moderation team, house rules, and tolerance level — what works in r/SideProject will get you permanently banned from r/programming. Before posting anything with even a tangential connection to your product, read each target subreddit's rules page and its "self-promotion" or "no-spam" policy specifically, because many explicitly state ratios like "no more than 1 in 10 posts should link to your own content" and actively enforce it with moderator bots that track posting history across the whole account.
The comment sections matter as much as, or more than, top-level posts. A large share of legitimate, sustainable Reddit-driven developer marketing happens in comments on other people's threads — someone asks "what's a good tool for X" in r/devops, and a genuinely helpful, specific answer that happens to mention your tool alongside two or three honest alternatives reads as community participation, not spam. The same mention as a standalone top-level post titled "Check out my new tool for X" reads as promotion, even though the underlying information might be identical. Context and framing matter more than content.
A related rule: disclose the affiliation. Redditors, and increasingly the platform's own norms, expect a simple "disclosure: I built this" when you mention your own product, even in a helpful comment. Omitting that disclosure and getting caught — which happens often, since Reddit users routinely check comment and post history — does far more reputational damage than the disclosure itself ever would, because it reframes every other genuinely helpful thing you've said as manipulative.
What does "value-first posting" actually look like in practice?
Value-first posting means your contribution would be worth reading or reacting to even if your product didn't exist at the end of it, meaning the post or comment leads with a real answer, insight, or resource, and only mentions your product as one option among several, positioned honestly relative to its limitations.
Take a concrete example: a developer posts in r/node asking how to handle rate limiting for a public API. A promotional response says "you should check out [Product], it handles rate limiting for you!" A value-first response explains the actual tradeoffs — token bucket versus sliding window, where to put the limiting logic in the request lifecycle, what happens at the edge versus the application layer — and then, only if genuinely relevant, mentions that a tool like yours handles a specific piece of that problem, while also naming one or two credible alternatives or the equivalent DIY approach. The second response gets upvoted, remembered, and clicked through on its own merits; the first gets removed or ignored.
This same principle scales to blog content you link externally. A post titled "5 Things We Learned Building Rate Limiting at Scale" that includes real numbers, real code, and an honest account of what didn't work will survive scrutiny on both platforms far better than a post that's structurally a product pitch with a technical veneer. The tell is usually in the conclusion — if the post's conclusion is "and that's why you should use [Product]," it's a pitch. If the conclusion is a genuine technical takeaway that happens to reference your product as the tool that got you there, it's value-first.
The practical process for most B2D teams: build a short list of specific, recurring questions your product's category answers (not just questions about your product), and prepare genuinely useful, non-promotional answers to those questions that you're willing to post repeatedly across relevant threads over months, mentioning your own tool only when it's actually the most honest answer to give.
What's the actual playbook for a successful Show HN launch?
A successful Show HN launch requires a working, immediately-usable product (not a waitlist or a demo video), a title that describes what it does in plain technical language without superlatives, a first comment from the founder explaining the specific problem and technical approach, and active, honest engagement in every subsequent comment for the following several hours.
Breaking that down into a checklist:
The product itself. "Show HN" submissions are explicitly meant to showcase something people can try right now. A waitlist, a "coming soon" page, or a product that requires a sales call before anyone can touch it will underperform regardless of how the post is written, because the entire format's implicit promise is hands-on evaluation.
The title. Effective Show HN titles are literal and specific: "Show HN: A CLI tool that diffs Terraform plans in plain English" outperforms "Show HN: Revolutionary new way to manage your infrastructure." HN's audience actively penalizes superlative language in titles — "revolutionary," "game-changing," "the best" — treating it as a signal that the substance won't match the claim.
The first comment. Immediately after submitting, the founder should post a comment (not edit the submission text, which HN limits) explaining the origin story briefly, the specific technical problem being solved, and an honest note on current limitations. This comment sets the tone for the entire thread and gives the community a genuine entry point for technical discussion rather than forcing them to guess your framing from the landing page.
The engagement window. The first two to four hours after posting determine almost everything, since HN's ranking algorithm weights early engagement velocity heavily. Submitting when you (and ideally a co-founder or engineer) can be actively present to answer comments in real time matters more than most other launch-day decisions. Many successful Show HN launches happen early in the US morning specifically because that's when the founder can commit to being present, not because of some magic algorithmic time slot.
Post-launch, regardless of outcome. If it goes well, follow up honestly on feature requests and bugs raised in the thread — HN has a long memory and will notice if you promised a fix and delivered it, or promised and didn't. If it flops or gets flagged, don't argue with moderators publicly; a quiet email to the mod team asking what went wrong is more productive and preserves your standing for a future submission.
How do you monitor Reddit and Hacker News for organic opportunities without spamming?
Effective monitoring means tracking specific keywords, subreddit names, and problem phrases related to your product category — not your brand name — so you catch genuine questions and pain points as they happen, rather than only reacting after someone already mentions you. Set up saved searches or alerts on the exact language developers use when they're stuck on the problem you solve, not the language you use to describe your solution.
Practically, this means building a running list of search terms based on how developers phrase the problem, not the product category name marketers would use. Someone struggling with your exact use case is far more likely to post "why does my webhook retry logic keep duplicating events" than "recommend a webhook management tool." Monitoring for the second phrase catches people already shopping; monitoring for the first phrase catches people at the moment of frustration, which is both a larger and earlier-stage audience, and a much better moment for a genuinely helpful, non-promotional response.
Tools like Reddit's own search, third-party alerting services, and simple RSS feeds on specific subreddits cover most of this without needing anything sophisticated. The harder part isn't the tooling, it's the discipline of responding as a knowledgeable community member rather than a brand account — using a personal account with a real comment history rather than a fresh account created the week of a launch, and resisting the urge to mention your product in every thread you find just because you found it.
This kind of always-on community monitoring is one of the pieces we build into ongoing developer marketing programs for DevTools clients, because the value compounds — the same monitoring setup that surfaces a helpful-comment opportunity today also surfaces competitive intelligence, feature request patterns, and genuine market research over time.
How do you convert Reddit and Hacker News traffic without triggering spam behavior?
Convert this traffic by sending it to content and product experiences that match the value-first tone of the post that drove the click, rather than a standard marketing landing page with pricing and a signup form above the fold. Traffic from these platforms is unusually skeptical and unusually likely to bounce immediately from anything that feels like a bait-and-switch from a helpful post to a hard sell.
The single most effective pattern we've seen: link to documentation, a specific technical page, or a genuinely useful resource (a comparison, a calculator, an open-source repo) rather than a homepage, and let the product's own merit do the converting once someone's already curious. Developer audiences from Reddit and HN convert well when they're allowed to self-serve evaluation — trying the product, reading the docs, checking the source — and convert poorly when they're funneled toward a "book a demo" call, which reads as a mismatch with the low-friction, self-directed research behavior that brought them there in the first place.
It's also worth explicitly measuring this traffic separately from other channels, because its behavior differs meaningfully: lower immediate conversion rates than paid search, but often higher long-term retention and a disproportionate tendency to become vocal advocates or contributors if the product actually delivers, since these are exactly the users who'll post their own honest opinion in a future thread when someone asks "has anyone used this." Treating a single Reddit or HN visit as a failed conversion because it didn't convert same-session misses where a meaningful share of the real value shows up weeks or months later. For teams scaling this beyond ad hoc posting, our content distribution approach treats these communities as one channel among several that need consistent, non-promotional presence over time rather than one-off launch pushes.
FAQ
How often can I post about my own product on Reddit before it looks like spam?
Most subreddits expect self-promotional content to be a small fraction of your total posting activity, often cited informally as roughly one in ten posts, and many enforce this with moderator bots that track your account's full history. A safer practical rule is to spend significantly more time genuinely helping in threads unrelated to your product than posting about it directly.
Should I use my personal account or a company account to post on Hacker News and Reddit?
Use a personal account with real comment history and, ideally, a name associated with your actual role at the company, since both communities strongly favor founder or engineer voice over brand accounts. A brand-new account with no history posting about a product on day one is one of the strongest spam signals on both platforms.
What happens if my Show HN post gets flagged or doesn't get traction?
Flags usually mean moderators or users perceived the post as promotional, off-topic, or duplicative of a recent submission; a polite email to hn@ycombinator.com asking for feedback is more productive than resubmitting immediately. A quiet launch is common even for good products, and it's generally safe to try again in a few months with a different angle or milestone.
Is it worth hiring an agency or growth hacker to manage Reddit and HN presence?
It can be worth it for monitoring, research, and content strategy, but the actual posting and comment engagement works far better coming from a real founder or engineer voice than an agency-run account, since both communities are unusually good at detecting outsourced, inauthentic participation. Treat any agency help as support infrastructure behind an authentic internal voice, not a replacement for it.
How do I measure whether Reddit and Hacker News marketing is actually working?
Track referral traffic from both domains alongside signup and activation rates specifically for that segment, but weight qualitative signals — mentions in unrelated threads, inbound messages referencing a specific post, GitHub stars or docs traffic spikes after a launch — more heavily than last-click conversion, since a meaningful share of the value from these channels shows up as delayed, word-of-mouth-influenced conversions rather than immediate signups.