LaunchRepoIndie hackers rarely lack ideas or shipping speed; they lack the boring week after launch. Every directory wants a slightly different tagline, its own screenshots, a maker account and a verification email. LaunchRepo is built for the third time you face that: describe the product once in product.json, hand your agent the start prompt, and let it work through the platforms that fit while you build the next thing.
The specific pain: distribution is the part you skip
Most side projects get one Product Hunt post and a tweet. The long tail of launch platforms, tool directories and communities stays untouched, not because it is worthless but because it is repetitive:
- The same copy, 346 times
- A 60-character tagline here, an 80-character one there, a “describe your product in one sentence” everywhere. Pasted by hand it drifts a little every time.
- Accounts and verification mails
- Each platform wants a maker account, a confirmation link and sometimes a badge on your site. After ten of them you stop opening the mails.
- No memory between products
- When the next project ships, nothing from the last round is reusable — the copy is in a dozen forms, the status is in your head.
How the workflow fits a solo builder
One product.json per project
Facts, copy variants, screenshots, pricing and the earliest launch date live in one file your agent reads for every submission. Fill it once in the local dashboard or let the agent interview you.
Your agent, your accounts, your browser
Claude Code, Codex, Cursor or a browser agent works in a Chrome you are signed in to. Nothing runs in the background; you see every tab it touches and every submit it clicks.
Small batches, honest states
The runbook picks a handful of fitting platforms per session and records each result as submitted, pending review, scheduled, needs-you or live. A thank-you screen is never counted as a listing.
Reuse for the next side project
The licence covers unlimited products you own. The second project starts with a working setup, a connected browser and an agent that already knows the playbooks.
Which directory categories matter
The catalog tags every one of the 346 platforms with one category. The counts below are computed from the catalog at build time; how many platforms actually fit your product is something your agent checks per directory before it submits anything.
Product launch platforms
104 playbooksThe largest group and the natural fit for a fresh side project: launch-day platforms and “new products” feeds where a maker account and a launch date are the main requirements.
Communities
7 playbooksFew in number but different in kind: forums and communities where a listing is a conversation, not a form. The playbooks tell your agent what to prepare and when to hand the post back to you.
Software and tool directories
85 playbooksGeneral tool directories that list anything with a URL and a category. Good second wave once the launch platforms are done.
Example platforms from the catalog
A few platforms from the catalog that indie hackers typically start with. Six of them have a public field guide on this site; the rest are described in the playbooks your agent reads.
- Product HuntThe launch day most side projects plan around; the playbook covers scheduling against your earliest launch date.Field guide →
- IndieHuntA launch platform for indie makers: a 200-word description, a free queue that can reach far into the future and a badge on your site.
- UneedA daily launch platform; the free plan allows one pending launch at a time, so a waiting product is not a failed one.Field guide →
- TinyLaunchA small launch platform with free dates and two upsell dialogs your agent clicks past with “continue with free”.Field guide →
- PeerlistA builder community whose Launchpad takes a project from your personal profile into a weekly slot.
What LaunchRepo does not do
- It does not submit for you. Your own agent does the work, in your session, with your accounts.
- It does not guarantee a listing, a backlink or traffic. Each directory moderates on its own terms and some only publish paid spots.
- It does not run unattended. CAPTCHAs, 2FA codes and paid upsells stop the run and are handed to you.
- It does not include agent usage. Your provider bills the tokens; the playbooks default to the free route on every platform.
Licence, in one sentence: pay once, then use it for an unlimited number of software products that you or your company own and operate, with as many agents as you like. Launching products for clients needs a separate licence.
Questions
I only have one side project right now. Is it still worth it?
That depends on whether there will be a second one. The licence is a one-time payment for unlimited own products, so the value grows with every launch. For a single product, a per-product service on our comparison pages may be the simpler choice.
Do I need to be a strong developer to use it?
You need to be comfortable running a coding agent such as Claude Code, Codex or Cursor and following a setup guide for connecting it to Chrome. No code has to be written; the local dashboard covers the forms.
How many directories will actually list my side project?
Nobody can promise a number. The catalog holds 346 playbooks, but each directory decides what it publishes and many review free submissions slowly. The tracker records what is really live so you never guess.
Can I launch under my personal name instead of a company?
Yes. identity.json holds the public name, contact address and nickname you want on listings; the agent uses exactly that and nothing else.
What does it cost beyond the licence?
Only your agent’s usage, billed by your provider. The playbooks never authorise a purchase; if a directory only offers a paid route, the agent records deferred_paid and moves on.
Ready when your next launch is
The launch price is €99.98, once. It rises 20 % after every 20 sales; the pricing page shows the live price, what is in the repository and the licence in short.
See pricing