Indie Hacker Community
An open community of solo builders: what you shipped this week, revenue posted openly, launches and failure notes.
- 5 categories
- 18 channels
- 7 roles
- Small
Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.
Server structure
Channels
THE ROOM
- house-rules
No course links in the revenue channels. A flat month is welcome.
- general
Everything else.
- intros
What you are building and how much time you have.
THE WEEK
- shipped-this-week
One post per builder per week. Small counts.
- stuck
The week nothing shipped, and why. Worth saying out loud.
- goals
What you intend to do next week.
NUMBERS
- revenue-milestones
First dollar, first hundred, first thousand.
- mrr-updates
A monthly number. No obligation to impress.
- failed-projects
What went nowhere, and what you learned. This keeps the rest honest.
LAUNCHES
- launch-day
Going public today. Say where.
- feedback-wanted
Pre-launch review. Ask one specific question.
- show-your-work
Demos and screenshots.
CRAFT
- marketing-and-distribution
Where solo builders are weakest. Ask here.
- pricing
What you charge and what happened when you changed it.
- tech-choices
Stack decisions, kept brief.
- tools
What is worth paying for.
- Build Session
- Weekly Call
Roles
- OwnerAdministrator
- ModeratorModerator
- Shipped
- Builder
- Launch Ping
- Muted
Overview
For people building small profitable things alone, usually alongside a job. The rhythm is weekly, not daily, because that is the pace a side project actually moves at. #shipped-this-week is the spine of the server: one post per builder per week saying what went out, and it works because shipping something small is far easier when a room is expecting it. #stuck is the counterpart, for the week where nothing shipped and the reason is worth saying out loud. Revenue is open here in a way it is not in most business communities: #revenue-milestones marks first dollar, first hundred, first thousand, and #mrr-updates takes a monthly number with no obligation to impress. #failed-projects is the channel that makes the rest honest — projects that went nowhere, with what was learned — because a community that only shows wins teaches nothing. Launches covers going public: #launch-day for the day itself, #feedback-wanted for pre-launch reviews with a required question, and #show-your-work for demos. Craft holds #marketing-and-distribution, which is where most solo builders are actually weakest, #pricing, #tech-choices and #tools. Voice has a Build Session for co-working and a Weekly Call. There is no hierarchy beyond moderators and a Shipped role earned by posting three weeks running.
When to use it
Solo builders lose to isolation rather than to competition: nothing forces a ship date, the marketing half never gets learned because there is nobody to ask, and every failure feels private and unusual. This layout sets a weekly shipping rhythm a room expects, keeps revenue and failure openly posted so the picture is honest, and gives distribution its own channel because that is where solo builders are weakest.
What makes it different
- A weekly shipping post, because a room expecting one is what gets small things finished.
- Revenue milestones and monthly numbers are posted openly, with no obligation to impress.
- A failed-projects channel, because a community that only shows wins teaches nothing.
- Marketing and distribution get their own channel, which is where solo builders are weakest.
Recommended Vetox setup
Streaks
Run Streaks on #shipped-this-week so a run of shipping weeks is visible, which is the whole mechanism here.
Leveling
Grant the Shipped role through Leveling so the people who consistently post are recognisable in every channel.
Reminders
Set a weekly Reminder in #shipped-this-week so the rhythm survives the weeks when everyone is busy.
Starboard
Point Starboard at #failed-projects so the most instructive write-ups are kept rather than scrolling away.
Questions
Why weekly rather than daily?
Because a daily standup is the wrong instrument for someone with two hours on a Tuesday evening. A daily channel produces either guilt or silence, and usually both. Weekly matches the real unit of progress for a side project, is achievable in a bad week, and makes the post worth reading, because a week's work is actually something.
Does open revenue posting not attract the wrong people?
It attracts two kinds and you have to moderate for the second. Builders posting real numbers, including small and flat ones, are the point. People posting inflated figures to sell a course are the failure mode, and the defence is a moderation rule against links to paid programmes in the revenue channels, plus a community norm that a flat month is as welcome as a good one.
Common mistakes
- Running a daily rhythm, which does not match how a side project actually moves and dies in a month.
- Allowing only success stories, after which every member privately believes they are the one failing.
- Filling the server with launch links, which turns a builder community into a promotion feed.
Consider instead
- Startup Founders Circle You want a small vetted room with confidential metrics rather than an open community.
- Freelancers Guild Members sell their time to clients rather than building products of their own.
More in Startups
View allEarly-Stage Startup Team
FeaturedA working server for a startup of three to eight people: async standups, a decision log, roadmap and customer signal.
Accelerator Cohort
A batch going through a programme together: a week-by-week schedule, mentor office hours, peer rooms and demo day.
Investor Updates Room
A private room for a company investors: monthly updates, a standing asks channel and questions answered once.
Product Launch War Room
A temporary server for one launch: a go or no-go checklist, per-surface channels and live incident handling.
0.0k
Servers
0+
Commands
0
Users
0
Languages
