Launching on Indie Hackers: what to post and where
Indie Hackers is a founder forum, not a launch site. Add your product page, earn posting access, then post numbers, lessons and failures.
LLaunchScaler·Published ·8 min read
Launching on Indie Hackers means adding your product to its Products database and then writing forum posts about how you built it, because Indie Hackers has no launch day, no launch ranking and no "submit your startup" button. The posts that get read share real numbers, a lesson learned or an honest failure, and new accounts must earn posting access by commenting first.
So treat Indie Hackers as the place you tell the story of the launch, not the place the launch happens. Everything below was checked on the live site in September 2026; the posting rules sit behind sign-in, so where the site does not publish something, this guide says so.
What is Indie Hackers?
Indie Hackers is a forum and case-study site for founders who make money directly from customers. Its own FAQ describes it as a place where founders of profitable businesses and side projects share their stories transparently, and as a community where members share experiences and give and receive feedback. It is not a directory and not a daily launch board.
A few facts from its About page shape how you should use it. Courtland Allen created it in August 2016. Stripe acquired it in April 2017, and it was spun back out as an independent business in March 2023, with Stripe as a seed investor. Its definition of an indie hacker is anyone who has set out to make money independently, "generating revenue directly from your customers."
That audience decides what works there. Readers are founders who came to learn, not shoppers looking for a new tool. They reward a post that teaches them something about building or selling, and they scroll past one that asks them to try your app.
Product page or post: which one is your launch?
Indie Hackers has three places your product can appear, and they do different jobs. The product page is a permanent profile. A post is a story in the forum that can reach the homepage. A product update is a short post attached to your product that competes on the daily Build Board. A launch uses all three, in that order.
Surface
Where it lives
What it is for
Questions, answered
What people ask about this
01
What is Indie Hackers?
Indie Hackers is a community where founders of profitable businesses and side projects share their stories and numbers, and where members give and get feedback. Courtland Allen started it in August 2016; Stripe acquired it in April 2017, and it was spun back out as an independent business in March 2023.
A permanent profile with your website and, if you share it, revenue
People browsing products by category or by revenue
Forum post
Homepage, Newest, Top Today, Top This Week
Your story: numbers, lessons, a failure, a question
The whole community, if members upvote and comment
Product update
Your product page and the Build Board
Short build-in-public progress notes
Build Board voters on the day you post
The Products database can be sorted by recently updated, recently added and revenue, from high to low or low to high, and filtered by category. A product page with a revenue figure can be found by readers who sort by revenue. The Build Board is marked as a beta and describes itself as a daily leaderboard of build-in-public posts, with voting that closes each day.
Can you post on Indie Hackers right away?
Usually not. A new account that tries to post gets the message "Sorry, you're not allowed to post this." Members in the thread about posting requirements quote the site's explanation that moderators look every day for people with a pattern of contributing authentically, and one reply from September 2026 notes there still does not seem to be a published threshold.
Plan for that wait before launch week, not during it. What members report working is plain participation: thoughtful comments on other founders' posts, answers to questions you know the answer to, and upvotes on posts you actually read. Nobody outside the moderators knows the number of comments or days required, so start two to four weeks early and treat the wait as unknown.
Two things are worth doing while you wait: add your product page, and draft your launch post so it is ready the day access arrives. If you have been sharing progress in public elsewhere, the build in public before launch guide covers how to turn those notes into a following you can bring with you.
What kind of posts do well on Indie Hackers?
Posts that share something readers can use do well: specific numbers, a lesson you paid for, a failure explained plainly, or a sharp question. Courtland Allen's posting advice says to start interesting discussions, ask useful questions, teach what you've learned and share relevant resources. Announcements of a product with nothing to learn from them do not.
The homepage shows the pattern. When checked in September 2026, many of the top posts led with a figure or an admission, such as a founder reporting $0 earned one week into a paid experiment, or a founder explaining what they fixed after a creator refused to endorse their product. Those titles promise a lesson, and the lesson is why people click.
Allen's title rules are specific:
Make the title descriptive, close to a full sentence. If you are asking a question, put the question in the title; if you are sharing advice, state the advice.
Make it useful to someone who is not you. His example of a good title is "How I figured out direct sales"; a bad one is "Progress report #2933".
Leave your company name out of the title. Unless the company is extremely popular and recognisable, he says it is almost never helpful.
He also says to put the important part in the first five sentences, because many readers will not go further, to use Markdown headings and lists to make long posts skimmable, and to put blank lines between paragraphs.
Here is how that turns a launch announcement into a post people read:
Weak launch post title
Stronger version
"Launching MyApp today!"
"What my first 50 signups taught me after 4 months building a scheduling tool"
"Feedback on my landing page?"
"My landing page converts at 1.2%. What would you change first?"
"MyApp v2 is live"
"I rebuilt my app after 3 customers churned for the same reason"
The numbers in those examples are placeholders; use your own. A post with invented or rounded-up figures gets picked apart in the comments by readers who build the same kind of product.
What are the self-promotion rules on Indie Hackers?
Indie Hackers does not publish a public rulebook on self-promotion. When checked in September 2026, the /guidelines URL returned a 404, and the posting rules shown to members sit behind sign-in. What is public is the founder's posting advice and the moderation gate on new accounts, and together they set the practical rule: teach first, mention your product second.
In practice that means:
Write the post so it is worth reading if the reader never clicks your link.
Mention the product where it is part of the story, once, with one link. The product page already carries your website.
Keep the company name out of the title.
Reply to every comment on launch day. Allen's advice notes the site rewards the posts that generate the most discussion, so the conversation is also what keeps the post visible.
Share the post elsewhere once. Allen explicitly says not to be shy about sharing posts on Twitter or with colleagues.
One piece of older advice no longer applies. The 2020 tips post recommends posting inside a relevant group so group members get it in their email digest, but the /groups page returned HTTP 410 (Gone) when checked in September 2026. Post to the main forum.
How do you launch on Indie Hackers, step by step?
A launch on Indie Hackers is a sequence spread over several weeks: earn posting access, add the product page, publish one story post on your launch day, answer every reply, then keep posting product updates. The steps below assume you are also launching elsewhere that week.
Two to four weeks before launch, join and start commenting on posts in your area. Posting access is granted by moderators on an unpublished schedule.
Add your product through Add Your Product in the Products database. Fill in the website and category, and a revenue figure if you are willing to share it.
Write the launch post before the day: a descriptive title, the key result or lesson in the first five sentences, Markdown headings, and one link to your product.
Publish on your launch day, early in your own day, and stay available to reply for the next several hours.
Post short product updates as you ship, which puts your product on the Build Board for that day.
A month later, write the follow-up: what the launch actually produced, in numbers, including what did not work.
How does Indie Hackers fit alongside launch platforms?
Indie Hackers is where you tell the story; launch platforms are where you get the dated listing, the ranking and the link. It has no launch-day ranking except the Build Board for product updates, so it works best as the long-form companion to a launch on Product Hunt, Show HN or LaunchScaler that same week.
The platforms differ in what they ask of you. Product Hunt says launching is 100% free, its day starts at 12:01 am Pacific Time, and you cannot ask people directly to upvote. Show HN is only for something people can try, and its guidelines say not to post landing pages or fundraisers. Indie Hackers asks for none of that, only a post worth reading. The full comparison of prices, waits and link terms is in the best product launch platforms, and the launch week plan shows how to space them so each gets its own day.
A sensible order for a small team: the dated launch on a platform first, the Indie Hackers post the same day or the day after with the early numbers in it, and a follow-up post a month later.
Pair the post with a launch you can date
Indie Hackers will not give you a launch date or a listing, so pair the post with a platform that does. On LaunchScaler, the free launch gives you "your listing from the day the queue reaches you", and every site gets a 156-check readiness scan before it is listed. The Premium launch is $29 one-time: it books any open day, today included, writes your listing for you from your own scan, and puts no badge on your site. In both cases, the one dofollow link to your site is earned by passing the readiness scan, not bought. If you want your Indie Hackers post and your launch listing live on the same day you choose, Get Premium and pick that day.
Can you launch a product on Indie Hackers?
Not in the Product Hunt sense. There is no launch day or launch ranking. You add your product to the Products database, then write forum posts about building it, and you can post product updates to the Build Board, a daily leaderboard of build-in-public posts.
03
Why can't I post on Indie Hackers?
New accounts get the message 'Sorry, you're not allowed to post this' until moderators grant posting access. Members quote the site's explanation that moderators look daily for people with a pattern of contributing authentically, and no published threshold exists.
04
Is self-promotion allowed on Indie Hackers?
Indie Hackers publishes no public rulebook on promotion. Its founder's posting advice is to share what readers want to learn, write descriptive titles, and leave your company name out of the title unless it is widely recognised. A post that teaches something can mention and link your product; a post that only advertises it gets ignored.
BetaList charges every submission and editors pick who is featured, refunding the rest. LaunchScaler lists free from a queue and ties its link to a scan.