How products get discovered.
Find something useful. Try it. Tell the founder what you think. These are the rules for taking part.
What works today
Product discovery rotates daily. You can browse by category, launch date or what a founder needs. Support votes come from signed-in accounts and do not determine homepage discovery.
The Community view orders products by support. Founder scores use positive support, adjusted for how long a listing has been live. Shipping numbers measure recorded activity, not product quality.
Bring a product people can use.
This directory is for solo founders and small teams building businesses. Link a live product website and a public post showing you building that product. Include your #buildinpublic post where available. A waitlist is fine; revenue is not required. Personal portfolios, freelance services, parked domains and repositories without a product website do not qualify.
New products deserve a chance.
The homepage discovery shelf rotates daily. It is a selection of listings, not a quality score or a popularity ranking. Newest and launch-date filters offer other ways to browse. A product with no votes has not been evaluated by the community.
Vote for products you find useful.
Vote because you would use a product or recommend it. Do not buy votes, trade votes, create extra identities or vote on your own product. Report misleading listings for review. A negative reaction alone is not grounds for removal.
Show what changed.
An update should describe a specific feature, release, experiment or customer lesson and link to its source. Repeating a post does not make it a new update. Repository activity is supporting evidence, not proof that a product is useful or commercially successful.
A feature is earned. An ad is labelled.
Editorial selections must explain why a product was chosen. Sponsored placements are separate and labelled. Payment never buys community votes, ownership verification or an editorial award. We do not promise customers, funding or traffic we cannot substantiate.
Founders control their own pages.
Publicly sourced listings are not endorsements by their founders. Claiming requires ownership verification and does not improve rank. Founders can correct their details or request removal. Unpublishing for eligibility should be reversible and include a recorded reason.
AI updates need founder permission.
Our planned API and MCP integration will let a founder authorise an assistant to draft or publish updates for a specific product. Automated posts must be attributed, linked to evidence and editable. Credentials must be scoped and revocable. An assistant cannot grant ownership, cast votes or manufacture traction.
How support works
One signed-in person can support a product once and can withdraw that support. Founders cannot support their own products. We keep homepage discovery separate, so a large existing audience cannot buy or mobilise its way into every discovery slot.
Support is a signal that someone wants a product to keep going. It is not a review, an endorsement, or proof of product quality.
What a feature should deliver
A defined homepage slot, a product story and a clear request from the founder. Email and social distribution will be included only when those channels are ready. Results should show actual visits and responses, not pretend that a click is a customer.
Corrections and removal
Send a correction with the product link and evidence, or request removal. A portfolio can be unpublished without banning its owner from submitting a genuine product later.
What counts as a ship
A ship is a public record of work, read from where it was published, with a link to the original: a commit or release on a public GitHub repository; an article on a feed you have listed; or a post on Mastodon or Bluesky that you tagged as build-in-public work (#buildinpublic, #indiedev, #indiehackers, #sideproject, #shipped, #launched, #devlog). Replies and reposts are not read, and an untagged post is not judged at all. Streaks count consecutive weeks with at least one ship; the number says how often you show your work in public, and nothing about how good the product is.
Your repository can stay private
A public GitHub repository is not an entry requirement. We need evidence connecting a founder to a product and their public updates. A hashtag alone is not proof of ownership or quality.