Product Hunt vs Show HN for Bootstrapped Products

Product Hunt is usually the better fit for a polished, visually explained product aimed at makers and early adopters, because its submission format centres the product page, tagline, gallery and maker comment. Show HN is usually the better fit for something people can try immediately when its maker can discuss the work in depth. Those conclusions follow from the platforms' current Product Hunt posting instructions and Show HN rules, checked 18 Oct 2026.

TL;DR: Start with Show HN for a tryable technical product and an open maker-led discussion. Start with Product Hunt when a concise pitch and strong visual assets suit both the product and its likely users. If both fit, use separate dates and compare qualified actions rather than treating rank as the goal. Product Hunt describes its audience as makers, early adopters and other technology-minded people, while Show HN explicitly asks for personal work that users can try and discuss (Product Hunt overview and Show HN rules, checked 18 Oct 2026).

On 17 Oct 2026, Llmspeed appeared on Hacker News as a Show HN for trying the apparent speed of a local language model before buying hardware. The Hacker News archive for 17 Oct 2026 shows the named launch and its discussion on that date. It is a useful current example of the format: a specific, usable technical tool with a claim readers could question. It is one launch, not evidence of what another maker should expect.

This article compares platform rules and mechanics, not promised outcomes. ZeroRaised publishes it and is therefore not a neutral observer of launch sites. ZeroRaised is a launch and discovery site for bootstrapped indie makers whose products have no institutional VC or accelerator equity.

Product Hunt vs Show HN at a glance#

The shortest useful distinction is this: Product Hunt is a product listing and release page that may be selected for its main featured feed, while Show HN is a Hacker News submission and comment thread for work people can try. Product Hunt says unfeatured submissions remain available in its All feed, and Hacker News says every Show HN starts on shownew before a small points threshold can move it to the Show page (Product Hunt homepage explanation and Show HN rules, checked 18 Oct 2026).

The formats reward different launch stories#

Product Hunt asks a maker to package a product for quick scanning. Its posting instructions call for a direct product URL, product name, short tagline, relevant topics, thumbnail, pricing status, gallery, description, maker details and opening comment. Video and an interactive demonstration are supported options. The same instructions recommend self-posting because it gives the maker control of the launch (Product Hunt posting instructions, checked 18 Oct 2026).

That structure suits software whose value becomes clear through a short line and a small set of visual proofs. A design tool can show the canvas. A mobile app can show its main journey. A business product can show the input, the output and the workflow between them. This is editorial judgement based on the format, not a Product Hunt promise of traffic or sales.

Show HN starts elsewhere. Its official description is “something you've made that other people can play with”. It accepts software people can run and physical things people can hold. Hardware may be represented by a detailed article or video, and a book by a sample chapter. It asks the person who worked on the project to explain how and why, make access easy and stay for the conversation (Show HN rules, checked 18 Oct 2026).

Llmspeed illustrates that shape without establishing a formula for success. The title tells readers what they can test and why it matters. The Llmspeed Show HN thread then becomes a place for requests, technical objections and comparisons. A maker considering Show HN should copy the clarity of the proposition, not its subject or its public response.

Product Hunt's own overview names Loom, Lattice, Zoom and Figma as companies that used feedback received on launch day to improve their products (Product Hunt overview, checked 18 Oct 2026). Treat that as the platform's own set of named examples, not as independent evidence or a forecast for a bootstrapped launch. The useful lesson is narrower: Product Hunt presents feedback as an intended outcome alongside discovery.

Which products are eligible?#

For Show HN, tryability is the first gate. A reader must be able to use the work, run it, hold it or inspect the permitted substitute for hardware or a book. Blog posts, newsletters, lists, sign-up pages and other reading-only material are off topic for this post type. The rules also exclude landing pages and fundraising pages and tell makers to return when the work is ready to try (Show HN rules, checked 18 Oct 2026).

The work need not look polished. Hacker News explicitly says an early-stage project can qualify, but it should be non-trivial, personally meaningful work rather than a quickly generated one-off. Easy access is preferred, ideally without an email or registration barrier (Show HN rules, checked 18 Oct 2026).

Product Hunt separates submission from homepage featuring. Its current featuring criteria focus on digital products and services that are available. The exclusion list includes waitlisted products without immediate access, directories, lists, templates, boilerplates, podcasts, courses, reports, events, books, services, commerce sites and deal sites. Hardware needs a prominent digital component. The team also evaluates usefulness, novelty, craft and creativity (Product Hunt featuring guidelines, checked 18 Oct 2026).

This distinction prevents a common misreading. Product Hunt's posting form can record a beta or unavailable status, but a submitted page is not the same as a featured homepage launch. The posting instructions describe the fields a maker can complete, while the featuring guidelines set a narrower standard for the featured feed (both checked 18 Oct 2026).

Apply those rules to the product you have now:

• A public API with working documentation and a usable key can fit both. Show HN becomes attractive when the implementation and trade-offs invite technical discussion. Product Hunt becomes attractive when the benefit can also be explained through a clean product page. This is editorial application of both platforms' rules.
• A private waitlist with no immediate access fits neither venue well. Show HN expressly excludes sign-up pages, while Product Hunt does not feature a waitlisted product without immediate access (Show HN rules and Product Hunt featuring guidelines, checked 18 Oct 2026).
• A technical book can qualify for Show HN if the post includes a sample chapter, but books appear on Product Hunt's current list of categories it does not feature (Show HN rules and Product Hunt featuring guidelines, checked 18 Oct 2026).
• A physical device can fit Show HN with something readers can inspect, while Product Hunt currently expects hardware to have a prominent digital component for featuring (Show HN rules and Product Hunt featuring guidelines, checked 18 Oct 2026).

If the product is still a waiting list, build demand through channels that accept that stage. The waitlist guide covers that job, and the broader SaaS launch guide compares venues by readiness.

Audience fit matters more than platform fame#

Product Hunt defines its community broadly: early adopters, makers, people in technology, entrepreneurs, investors and people who enjoy trying new products. It says anyone can use the platform and that makers can work alone, in a large team, in development, in marketing or elsewhere (Product Hunt overview, checked 18 Oct 2026).

Hacker News defines relevance through intellectual curiosity rather than a job-title list. Its guidelines say the site covers more than hacking and startups. They also warn against using Hacker News mainly for promotion: sharing your own work some of the time is acceptable, but curiosity should be the main reason for participating (Hacker News guidelines, checked 18 Oct 2026).

That produces a practical audience test. Ask whether the people most likely to understand the problem already spend time in that community. A database tool, programming library, local computing utility or piece of unusual hardware has an obvious technical question at its centre. A visual productivity app, creator tool or broad consumer utility may be easier to understand from a polished Product Hunt gallery. Neither conclusion guarantees a result, and an excellent product can fit both.

How to prepare a Product Hunt launch#

Begin with an individual account. Product Hunt does not allow a company account to post or comment, and a new account must finish onboarding before it can post. Its instructions recommend that makers submit their own product rather than depend on a third-party hunter (Product Hunt posting instructions, checked 18 Oct 2026).

Build the launch page as a compact explanation, not a collection of slogans. The required and supported fields tell you what evidence to prepare: a direct product link, plain product name, short tagline, closely related topics, pricing status, thumbnail, gallery, description, maker accounts and an opening maker comment. The instructions support video and interactive demonstrations too (Product Hunt posting instructions, checked 18 Oct 2026).

A useful asset sequence is editorial advice:

• Lead with the user's problem and the product's result, not a logo on an empty background.
• Show the product in use. Let each gallery image answer a different question about input, workflow, output or fit.
• Make the tagline concrete enough that a reader can decide whether the problem belongs to them.
• Use the opening comment for the build story, what changed for this release and the kind of feedback that would help.
• Test the direct product URL, sign-in path, pricing page and first useful action from a fresh browser before scheduling.

Product Hunt's current launch guide says a scheduled release goes out at 12:01 AM Pacific and advises choosing a date when someone can answer comments. It also recommends deciding what success means before the release (Product Hunt launch guide, checked 18 Oct 2026). Treat the clock as an operating constraint, not a reason to choose a date when users or support are unavailable. A launch time calculator converts that start to your own zone.

If you need production safeguards, use the traffic-spike guide before adding a public release date. If screenshots or a walkthrough are the weak point, use the product demo video guide. Those preparations matter on either platform even though Product Hunt exposes the media more prominently.

How to prepare a Show HN post#

Start with the product experience. The official rules prefer easy access without registration or email, and they tell makers to wait when users cannot yet try the work. The project must be something the poster worked on personally, and that person must be available to discuss it (Show HN rules, checked 18 Oct 2026).

Then prepare the post around a precise claim. Hacker News instructs posters to submit a story whose title begins with Show HN. General Hacker News rules also say not to use uppercase or exclamation marks to attract attention, and to use the original title unless it is misleading or promotional bait (Show HN rules and Hacker News guidelines, checked 18 Oct 2026).

The Llmspeed title works as an example because it identifies the action and decision: experience the likely speed of a local model before choosing hardware. A second recent example, GitGud's Show HN post, describes a free, open-source Git interface and names its undo capability. These examples show concrete title construction. They do not prove that a particular wording causes attention.

Use the first comment to give context that the product page cannot: why you built it, what the architecture or difficult trade-off was, what remains rough and what kind of critique you want. This is editorial advice consistent with Show HN's request to explain how and why. Do not manufacture a dramatic backstory. A short, specific account is more useful than a generic launch announcement.

Before posting, test the anonymous path, mobile layout if relevant, documentation, error states and a way to contact you. Remove any claim you cannot demonstrate. Prepare short answers about privacy, pricing, data handling, dependencies and limitations. Those are editorial checks, not Hacker News requirements.

Write the post and replies yourself. Hacker News currently prohibits generated text in posts and prohibits generated or machine-edited text in comments (Hacker News guidelines, checked 18 Oct 2026). The restriction is unusually explicit, so a polished template that would be acceptable elsewhere may breach the rules here.

Promotion and ranking without vote solicitation#

Both platforms permit awareness and forbid vote requests. Product Hunt allows a direct link to be shared with a community, friends or users, but says not to mass-message people asking for votes, offer rewards for votes or coordinate a voting push. It encourages organic social sharing, participation in relevant communities where the maker is already active and engagement with people who comment (Product Hunt sharing rules, checked 18 Oct 2026).

Hacker News is stricter about both votes and comments. Its FAQ says not to ask anyone to upvote or comment and warns that submissions, accounts and sites may be penalised or banned for vote solicitation. Its general guidelines repeat the prohibition on soliciting votes, comments or submissions (Hacker News FAQ and Hacker News guidelines, checked 18 Oct 2026).

The safe message is factual: “We released this, here is the post if you want to see it.” Do not add “please upvote”, substitute a euphemism such as “show support”, or offer a reward tied to action on the platform. On Product Hunt, ask for honest product feedback without prescribing a vote. On Hacker News, avoid asking people to enter the thread at all; tell genuinely interested people about the product through normal channels and let them decide what to do. This paragraph is conservative editorial guidance based on the cited rules.

Neither visible vote total is a reliable forecast of ranking. Product Hunt says its order uses upvotes, comments, time since submission and other undisclosed factors. Hacker News describes a time-decayed points calculation plus flags, abuse controls, weighting and moderator action, and says account karma does not boost a post's rank (Product Hunt launch-day guidance and Hacker News FAQ, checked 18 Oct 2026).

Do not buy a promotion package that promises votes. Product Hunt says paying anyone to hunt or send traffic for ranking purposes breaches its guidelines, while its own advertising is separate from the leaderboard. Hacker News says it penalises vote manipulation (Product Hunt overview and Hacker News FAQ, checked 18 Oct 2026).

Should you launch on both?#

Yes, if the product genuinely meets both sets of rules and both audiences contain plausible users. Neither platform's cited rules prohibits a separate launch on the other. The recommendation to separate the dates is ZeroRaised editorial advice, based on the work required to answer comments, support new users, diagnose failures and attribute outcomes.

Choose the order from the learning you need:

• Use Show HN first when technical scrutiny could expose incorrect assumptions, confusing documentation or missing controls before a broader presentation. Make the product easy to try and answer the uncomfortable questions directly.
• Use Product Hunt first when the main uncertainty is positioning for a broader maker and early-adopter audience. Use comments and observed user behaviour to sharpen the technical explanation before Show HN.
• Skip one venue when its audience or format is forced. A business service that cannot be tried is not rescued by a clever Show HN title. A strong command-line utility does not need a Product Hunt release merely because competitors have one.

Do not copy the same text between platforms. Product Hunt's fields reward a concise benefit, useful media and an opening maker story. Show HN needs a precise title, immediate access and a thread capable of carrying technical scrutiny. The facts can remain consistent while the presentation answers each community's actual questions.

For a deeper platform-specific runbook, use the Product Hunt launch guide and the Show HN writing guide. The bootstrapped launch checklist covers work outside either listing, including onboarding, support and measurement.

How to measure which launch worked#

Define one primary product action before posting. It might be completing onboarding, installing the tool, creating a project, requesting a relevant sales conversation or paying. This is editorial advice. It makes the comparison about product progress rather than applause.

Record each source separately, then review:

• visits that reached the product rather than only the platform page;
• users who completed the first meaningful product action;
• qualified conversations with people who match the intended audience;
• repeated objections, broken steps and feature requests;
• paid conversions or sales opportunities, where those match the product model;
• support load, failures and fixes required by the release.

Do not merge all referral traffic into one success figure. A Show HN thread may be valuable because it reveals a technical flaw. A Product Hunt page may be valuable because a clear visual explanation converts the right visitor. Neither outcome is captured by rank alone. The first users guide explains how to turn initial attention into direct learning without treating one launch as a growth system.

Write a short review after each release: what you expected, what happened, what users did, what broke and what you will change. Keep individual comments as qualitative evidence rather than converting one person's opinion into a market conclusion. No platform source can tell you in advance what your product will convert.

Relaunch rules and the next release#

Product Hunt's specific relaunch policy asks for at least six months between posts for the same product or company, including products that share a root domain. It also requires a significant change, such as a new mobile app or a complete redesign with new functionality. A new interface or price change alone does not qualify. Earlier attempts require a request and receive more scrutiny (Product Hunt relaunch policy, checked 18 Oct 2026).

The broader Product Hunt launch guide encourages makers to return for major releases. Read that encouragement together with the specific timing and significance rules, not as permission to post every small change (Product Hunt launch guide and relaunch policy, checked 18 Oct 2026).

Show HN says new features and upgrades are generally not substantive enough for another Show HN, though a major overhaul may be. The general Hacker News FAQ permits a small number of reposts when a story has received no significant attention for roughly a year, but also says not to delete and repost the same story (Show HN rules and Hacker News FAQ, checked 18 Oct 2026).

In either case, write down the actual change before planning a return. “We changed the pricing” is not a fresh product story. “A new group can now complete a job that was previously impossible” may be, provided it is accurate and meets the platform's current rules.

A practical choice for a bootstrapped maker#

Choose Show HN when the product is ready to try, the technical substance is part of its appeal and the builder can stay in the discussion. Choose Product Hunt when its stated community overlaps with likely users and the product becomes understandable through a short pitch, images and a maker comment. Choose both, on separate dates, when each has a distinct job.

Choose neither yet when access is only a waiting list, onboarding breaks for a new user or the team cannot support the resulting conversations. Fixing readiness is more valuable than occupying a release date. The guide to validating a SaaS idea can help before launch, while the Product Hunt alternatives guide covers other venues.

ZeroRaised can sit alongside either plan. Browse the current launch board, check the member perks, and submit a product if it meets the current requirements. ZeroRaised is specifically for bootstrapped indie products with no institutional VC or accelerator equity. That makes funding eligibility part of its remit, whereas Product Hunt and Show HN should be chosen here for their format, rules and audience fit.

Sources#

• Hacker News Show HN rules, checked 18 Oct 2026
• Hacker News guidelines, checked 18 Oct 2026
• Hacker News FAQ, checked 18 Oct 2026
• Hacker News archive for the hook, Llmspeed thread and GitGud thread, checked 18 Oct 2026
• Product Hunt platform overview, checked 18 Oct 2026
• Product Hunt launch guide, checked 18 Oct 2026
• Product Hunt posting instructions, checked 18 Oct 2026
• Product Hunt featuring guidelines, checked 18 Oct 2026
• Product Hunt homepage explanation, checked 18 Oct 2026
• Product Hunt sharing rules, checked 18 Oct 2026
• Product Hunt launch-day guidance, checked 18 Oct 2026
• Product Hunt relaunch policy, checked 18 Oct 2026