You get found on Hacker News by putting something genuinely interesting in front of a technical audience at the moment they are paying attention, and then engaging with the comments like a real person. Hacker News is not a collection of communities like Reddit. It is a single front page, one audience, and effectively one shot per launch. A post either gathers enough early upvotes to climb before time decay pulls it back down, or it sinks unseen. The mechanism rewards substance, honesty and technical depth, and it punishes anything that smells like marketing. Understanding how the ranking actually works is the difference between a launch that reaches thousands of the right people and one that disappears in twenty minutes.
- Hacker News is one front page and one audience, not many communities. You get roughly one good shot per launch, which makes it the opposite of a long-term presence channel.
- Ranking is driven by upvotes fought against a time-decay function, with flags and moderation able to override raw score. Early velocity from real readers is what matters.
- Most launches sink because the title oversells, the timing is wrong, or the thing is not interesting to a technical audience on its own merits. The audience is unforgiving of hype.
- A small, genuinely technical product wins by being honest, specific and present in the comments. The Show HN format exists precisely for this.
How the front page ranking works
Hacker News ranks stories with a published formula that balances how many points a story has against how old it is. A story gains points from upvotes, and that score is divided by a function of its age raised to a power, so a post decays steadily as the hours pass. The practical effect is that points alone do not win. Points relative to age win. A post that gathers upvotes quickly in its first hour climbs the ranking faster than the same number of upvotes spread over a day, because the time-decay denominator is still small while the votes are arriving. This is why early velocity is the thing that decides almost everything.
The new page is where launches live or die
Every submission starts on the /new page, which is a fast-moving stream of everything posted, read by a smaller pool of dedicated users who specifically hunt for good early stories. To reach the front page, your post needs to gather enough upvotes from those readers, quickly, while it is still near the top of /new. If it does not, it slides off /new and out of view, and almost no one will ever see it again. This is the bottleneck. The front page is the reward; /new is the gate, and most posts never get through it because nothing about them compels an early reader to upvote in the first few minutes.
Flags, the flamewar penalty and moderation
Upvotes are not the only force acting on your rank. Users can flag a post, and enough flags will bury it regardless of its score, which is how the community removes things it considers spam, dishonest or off-topic. There is also a software penalty that can down-weight threads showing the signature of a flamewar, many comments arriving fast relative to upvotes, on the theory that a heated argument is not the same as genuine interest. And moderators intervene by hand: they can re-rank, penalise misleading titles, or give a quietly good post a second chance. The takeaway is that the ranking is not a pure popularity contest. It actively tries to filter for genuine, good-faith interest, and it works against anything engineered.
The Show HN and Launch HN formats
Hacker News has a purpose-built format for showing the community something you made: Show HN. You prefix your title with "Show HN:" and link to something people can actually look at or try, not a sign-up wall or a marketing page. The format comes with expectations. The audience wants to see the thing, understand what it does, and ideally poke at it, so a Show HN that hides behind a waitlist or a video tends to disappoint. There are also rules: Show HN is for your own work, it should be genuinely new to the audience, and the title should describe the thing plainly without hype.
Launch HN is a separate, moderator-coordinated format reserved for funded startups, typically arranged with the site rather than self-posted. For most solo and bootstrapped founders, Show HN is the relevant door. The good news is that Show HN is the format most aligned with what a small technical product can offer: a real thing, built by the person posting, that an engineer can evaluate on its merits. That alignment is exactly why it gives a small product a fair chance against much larger ones.
| Aspect | Show HN | Launch HN |
|---|---|---|
| Who it is for | Anyone showing their own work | Funded startups, coordinated with moderators |
| How you post | Self-posted with a "Show HN:" title prefix | Arranged with the site, not self-served |
| What to link | Something people can actually see or try | A launch post plus the product |
| Best fit | Solo and bootstrapped technical products | Venture-backed companies with a milestone |
Why most launches sink
The common assumption is that launches sink because of bad luck or a saturated front page. More often they sink for reasons the founder controlled. The title oversold and the audience punished the hype. The thing was not actually interesting to engineers on its own terms, so no early reader felt compelled to upvote. The timing put the post into /new during the quietest part of the day. Or the founder tried to manufacture early votes, which the system is specifically built to detect and penalise. Each of these is avoidable, and each is more common than genuinely losing to better posts.
- Hyped or vague titles. Hacker News readers react against marketing language and reward plain, specific description. A title that promises more than the thing delivers gets flagged or ignored.
- Nothing to actually look at. A Show HN behind a waitlist, a login, or a video frustrates an audience that came to evaluate the real thing.
- Not interesting to engineers. If the product solves a real problem but in a way that holds no technical interest, the front page is the wrong audience and the post will not catch.
- Manufactured early votes. Asking friends to upvote, or coordinating a voting ring, is detectable, against the rules, and a reliable way to get a post penalised rather than promoted.
- Wrong moment. Posting when /new is quiet or the audience is asleep starves the post of the early velocity it needs while time decay is still working against it.
What gives a small product a real chance
A small, genuinely technical product has a structural advantage on Hacker News that it has almost nowhere else: the audience evaluates the work, not the marketing budget. To use that advantage, lead with the substance. Write a title that describes plainly what the thing is and what is interesting about it, with no hype to react against. Link to something people can immediately see or try. And give the audience the technical detail it wants, either in the post itself or in your first comment: how it works, why you built it this way, what the hard part was, and what the honest limitations are.
How to behave in the comments
The comments are not an afterthought to a Hacker News launch. They are the launch. The audience expects the person who built the thing to be present, answering questions directly and engaging in good faith, and that presence is often what carries a post from a modest start to the front page. Be specific, admit limitations openly, and answer the technical questions properly rather than deflecting. Crucially, do not get defensive when the criticism is sharp, because Hacker News criticism is frequently both blunt and correct, and how you handle it is itself part of what the audience is judging. A founder who responds to hard questions with candour and depth earns more goodwill than a flawless pitch ever could.
There is one more thing the small product can offer that the large one cannot fake: a real story. The honest account of why you built this, what you learned, and what is still rough is exactly the kind of substance this audience rewards. You are not trying to win a marketing contest. You are trying to be interesting and honest enough that a technical reader thinks the rest of the front page should see this too. That is a contest a small product can win.
How Hacker News fits the rest of your discoverability
Hacker News is a single, high-intensity moment, and that is its defining feature. You get one front page, one audience, and roughly one good shot per launch, with a long quiet gap before the next thing you have is worth posting. This makes it the opposite of a channel like Reddit, where the work is being a useful regular across several niche communities over months. Reddit is patient, distributed presence. Hacker News is concentrated, occasional intensity. Both reward genuine substance and punish promotion, but they ask for completely different rhythms of effort, so it pays to know which one a given piece of work suits before you spend the energy.
The sibling guide: getting found on Reddit without getting banned →A strong Hacker News appearance also outlives the day it happens. The thread, the discussion, and the links it generates become part of the durable record of your product, the kind of credible, technical mention that both human readers and AI assistants weigh later when they decide whether your product is worth naming. A good launch is not only a traffic spike. It is evidence that compounds.
How credible mentions feed AI visibility →When is the best time to post on Hacker News?
The honest answer is that timing helps but does not save a weak post. You want your submission landing on /new when enough dedicated early readers are active to give it the velocity it needs, which generally means a weekday during waking hours for the largely North American and European audience rather than the middle of the night. Avoid the quietest stretches. But treat timing as a small edge on top of a genuinely interesting post, not a substitute for one.
Can I ask friends to upvote my Show HN?
No. Coordinated voting, asking people to upvote, or any voting ring is against the site rules and the system is specifically built to detect it. The likely outcome is not a boost but a penalty, and a damaged reputation if it is noticed. The votes that matter are from real readers who found your post on /new and genuinely thought it was worth seeing. Engineer the post to deserve those, not the count to fake them.
What makes a good Show HN title?
Plain, specific, and honest. Start with the "Show HN:" prefix, then describe what the thing is and what is interesting about it in the fewest words that are still accurate. Avoid superlatives, marketing language, and anything the product does not actually deliver, because this audience reacts against hype and rewards precision. A title that lets a technical reader immediately understand what you built and decide it is worth a look is doing its whole job.
My launch sank with no comments. What went wrong?
Usually one of a few things: the post never gathered enough early upvotes on /new to climb, the title oversold and readers passed, there was nothing concrete to look at, the thing was not interesting to a technical audience on its own merits, or the timing was poor. A sunk post is rarely bad luck alone. Re-read your title and first comment honestly, make sure there is something real to try, and a future post can do far better.
Is one Hacker News launch enough, or should I keep posting?
Reposting the same thing repeatedly is discouraged and tends to get penalised, so do not treat it as a channel you post to weekly. Hacker News rewards genuinely new things, so the right cadence is to return when you have something the audience has not seen and would find interesting: a significant new capability, a real technical write-up, a result worth sharing. Quality and novelty, spaced out, beat frequency every time on this platform.
Getting found on Hacker News comes down to having something genuinely interesting to a technical audience and being honest and present when you show it. There is no mechanism to game and no shortcut around being substantive, which is exactly why a small, real product can hold its own against much larger ones. AfterLaunch treats launch and community surfaces as dimensions where your product is either present or absent, watches for the moments worth a post, and drafts the write-up in your own voice for you to review and publish on your timeline. It cannot manufacture interest, and it will not try to. What it can do is help you recognise when you have something worth the front page, and show up to it as the honest builder this audience respects.