LaunchRepo.

Use case

Launch your developer tool on 346 directories with your own agent

You already run a coding agent all day. LaunchRepo gives it a second job: working through the tool directories, launch platforms and communities where developers actually find new tools.

Developer tools have an unusual distribution problem: the audience does not read ads, but it does browse alternatives sites, tool directories and a handful of communities. Listing there is worthwhile and tedious in equal measure. LaunchRepo is a repository, not a service, which is exactly why it fits a developer: your agent reads 346 Markdown playbooks, a JSON product file and a CSV tracker — files you can inspect, version and edit.

The specific pain: the tooling audience lives in directories you never fill in

A developer tool gets a README, a GitHub release and maybe a post. The directories where developers compare tools stay empty because the forms are boring:

Alternatives sites need a complete profile
Platforms, licence, pricing, screenshots, the tools you replace — half-filled profiles stay unpublished, and nobody on the team enjoys filling them.
Communities are not forms
Hacker News, subreddits and builder communities want a post in the right tone at the right time. Automating that badly is worse than skipping it.
Open-source and paid tiers confuse the fields
Is it free? Is there a paid plan? Every directory asks differently, and an honest answer needs a human decision the first time.

How the workflow fits a developer

  1. Everything is a file in a repo

    Playbooks in Markdown, product context in JSON, results in CSV, records written by a Python script. Diff it, grep it, version it — no dashboard you cannot inspect.

  2. Your existing agent and browser

    The agent you use for code reads the same files. BROWSER-SETUP.md connects it to a Chrome you are signed in to via Chrome DevTools MCP or a dedicated CDP profile.

  3. Communities are handed back to you

    For community platforms the playbook prepares the post and the tracker records prepared_needs_human. You decide what goes out under your name.

  4. A local dashboard, zero dependencies

    python3 scripts/dashboard.py serves a 127.0.0.1 web UI over the same files: products, states, follow-ups, catalog. Python standard library only.

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.

  • Software and tool directories

    85 playbooks

    Tool and alternatives directories where developers compare options. The largest source of long-lived profile pages for a developer tool.

  • Product launch platforms

    104 playbooks

    Launch platforms, including several aimed at developer products; useful for the release day and new-product feeds.

  • Communities

    7 playbooks

    Hacker News, Reddit, builder communities. The playbooks prepare; you post. Few platforms, high attention to tone.

Example platforms from the catalog

Platforms from the catalog that developer tools are usually expected on. Two have a public field guide on this site; the rest are described in the repository playbooks.

  • SourceForgeA long-standing software directory with a vendor request form and tight character limits that truncate silently.
  • AlternativeToAn alternatives directory where developers look for replacements; the profile lives on which tools you compare against.
  • SaaSHubAn alternatives and reviews directory; category fit and a complete profile matter more than timing.Field guide →
  • PeerlistA builder community whose Launchpad takes a project from your personal profile into a weekly slot.
  • Product HuntThe launch day most developer tools still plan around; the playbook covers scheduling.Field guide →

What LaunchRepo does not do

  • It does not post to Hacker News or Reddit for you. Community posts are prepared and handed back; you publish under your own name.
  • It does not guarantee stars, backlinks, traffic or a listing anywhere — each directory moderates on its own terms.
  • It does not manage your GitHub releases or package registry. It is about directories, not distribution of the code itself.
  • It does not run headless or unattended. CAPTCHAs, 2FA and paid routes stop the run and wait for you.

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

My tool is open source. Do the playbooks handle that?

Yes. product.json holds licence and pricing facts; the playbooks say how each directory asks about free and paid tiers. Nothing is invented — if a fact is unknown the platform is recorded as blocked with the missing fact.

Can I run it from the terminal only?

Yes. The dashboard is optional; record.py, submissions.csv and the Markdown files are the source of truth and work without it.

Which coding agent works best?

We make no benchmark claims. Any agent that reads files and drives a browser works: Claude Code, Codex, Cursor or a browser agent. The agent pages describe the setup for each.

Does it touch my repository or CI?

No. The workspace lives next to the delivery checkout, and the only thing that ever touches your website is a badge — and only if you grant that permission once per product.

What do I get on day one?

A private GitHub invitation with the 346 playbooks, the product template, AGENTS.md, the runbook, the browser setup guide, record.py and the local dashboard. The changelog lists every release.

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