# LaunchRepo

> The boilerplate for directory launches. 275 directory playbooks, product context and a submission tracker your AI agent runs for you. Pay once, launch every product you ever build.

One prompt, zero grind: LaunchRepo turns your AI coding agent into a distribution machine — step-by-step playbooks for every directory, your product context, and a tracker that records what actually went live.

## Key facts
- Product: a private GitHub repository (boilerplate) your own AI coding or browser agent runs to submit your SaaS to launch platforms and software directories.
- Price: €99.98 one-time launch price, no subscription. The price rises 20 % after every 20 sales. Current price: https://launchrepo.dev/#pricing
- License: Pay once, Unlimited products, Unlimited agents, Perpetual access. Repository access for one GitHub account.
- Works with: Claude Code, Codex, Cursor and browser agents that can read files and drive a logged-in Chrome.
- Not a done-for-you submission service. No guaranteed listings, backlinks or rankings; agent usage is billed by your AI provider.
- Proof: Built on our own launch: seomap.dev, submitted to 160+ directories — live or awaiting publication.
- Founder video (2:47, English, burned-in captions): https://launchrepo.dev/media/launchrepo-info.mp4
- Publisher: The CodeCave GmbH, Frechen, Germany. Founder: Aleksandar Vuk Jovanovic (@AleksDoesCode). Contact: info@thecodecave.de

## What is in the box
- 275 directory playbooks (`playbooks/`): Preparation, form fields, limits, blockers and the confirmation steps for each platform.
- Product context template (`product.json`): One product.json your agent reads for every submission: facts, copy variants, assets, pricing.
- Submission tracker (`submissions.csv`): draft → submitted → live. Your agent records evidence, you see what is actually published.
- Agent instructions (`AGENTS.md`): AGENTS.md and a runbook: how to qualify a directory, avoid duplicates, handle captchas and when to stop.
- Browser setup (`BROWSER-SETUP.md`): Connect the agent to your logged-in Chrome so OAuth, Gmail and captchas don’t block the run.
- One-command records (`record.py`): A script that updates CSV, status and playbook index. No hand-editing, no stale spreadsheets.

## How it works
1. Clone & describe: Fill product.json with your facts, copy and assets. Ten minutes, once per product.
2. Run your agent: Point Claude Code, Codex or Cursor at the repo. It reads the playbooks and works the list.
3. Ship the evidence: Approve what needs you, collect live URLs, reuse everything for your next launch.

## FAQ
### Is this a submission service?
No. It is a repository of playbooks, product context and tracking that your own AI coding or browser agent runs, with your accounts. You stay in control of every submission.

### Which agents work with it?
Any agent that can read files and drive a browser: Claude Code, Codex, Cursor, OpenAI Operator-style browser agents. The repo ships with a browser setup guide for your logged-in Chrome.

### Are listings guaranteed?
No. Every directory has its own rules, moderation and sometimes fees. Your agent records blocked, pending and live outcomes separately so you always know what is real.

### What else do I pay for?
Your agent’s usage, billed by your provider. Some directories charge for featured spots — the playbooks default to the free path and never authorize purchases.

### Can I use it for several products?
Yes. One payment, perpetual use for unlimited SaaS products you own and unlimited agents. Repository access is bound to one GitHub account.

### How do I get access?
Pay via Stripe, no account needed. Then verify your email and connect your GitHub account — you get invited to the private repo.

## Launch platforms covered (examples)
Product Hunt, SaaSHub, AlternativeTo, Uneed, Peerlist, SourceForge, Fazier, TinyLaunch, F6S, GoodFirms, IndieHunt, OMR Reviews, SaaSworthy, PitchWall, LaunchBoard, StartupBlink, Smol Launch, ToolPilot, PromoteProject, SideProjectors, Stork.AI, ToolDirs, SubmitHunt, Nick Launches, StartupTrusted, Startup Buffer, SaaS Browser, AppRater, ComingUp, Launching Next

## Directory submission field guides
- [Product Hunt submission guide](https://launchrepo.dev/directories/producthunt/): Prepare a maker-led launch with a clear product demonstration and a deliberate launch date. The observed workflow reached a scheduled launch; that confirms a date, not publication or homepage placement.
- [SaaSHub submission guide](https://launchrepo.dev/directories/saashub/): Prepare a software listing around accurate categories and real alternatives. The observed submission produced a publicly accessible page marked Pending approval. Public accessibility alone was not evidence of acceptance.
- [Uneed submission guide](https://launchrepo.dev/directories/uneed/): Check account capacity before preparing another launch. The observed free workflow allowed only one pending launch and blocked a new submission when the account already had waiting products. This is an account constraint, not a verdict on product fit.
- [Fazier submission guide](https://launchrepo.dev/directories/fazier/): Treat eligibility checks as a decision gate. The observed Basic submission flow required community comments, a visible badge and an Ahrefs Domain Rating above zero. A product that fails a requirement should stop before attesting compliance.
- [PitchWall submission guide](https://launchrepo.dev/directories/pitchwall/): Review imported copy before sending a startup for moderation. The observed URL import needed corrections to the product name and description. The completed submission remained Under Review, with an estimate exceeding 30 days.
- [TinyLaunch submission guide](https://launchrepo.dev/directories/tinylaunch/): Follow the complete scheduling flow, including the final upsell dismissal. The observed Standard launch path offered a future weekly slot, then required declining extras and a second upgrade dialog before showing success. Approval still remained outstanding.

## Launch planning guides
- [Track directory submissions without double counting](https://launchrepo.dev/guides/submission-status-tracking/): Separate preparation, review, queue, scheduling and publication so the next agent knows whether to resume or verify.
- [Plan directory work with a zero-spend budget](https://launchrepo.dev/guides/zero-spend-launch-planning/): Use eligibility and asset checks to decide where to spend agent time before attempting a submission.

## Languages
- [English](https://launchrepo.dev/)
- [Deutsch](https://launchrepo.dev/de/)
- [Español](https://launchrepo.dev/es/)
- [Português](https://launchrepo.dev/pt/)
- [Français](https://launchrepo.dev/fr/)
- [Italiano](https://launchrepo.dev/it/)
- [Nederlands](https://launchrepo.dev/nl/)
- [Polski](https://launchrepo.dev/pl/)
- [Türkçe](https://launchrepo.dev/tr/)
- [日本語](https://launchrepo.dev/ja/)
- [한국어](https://launchrepo.dev/ko/)
- [简体中文](https://launchrepo.dev/zh/)

## Optional
- [Full LLM context](https://launchrepo.dev/llms-full.txt): all guides in one file.
- [Sitemap](https://launchrepo.dev/sitemap.xml)
- [Legal notice](https://launchrepo.dev/legal/imprint/)
- [Privacy](https://launchrepo.dev/legal/privacy/)
- [Terms of Service](https://launchrepo.dev/legal/terms/)