# LaunchRepo > Use your AI agent to prepare directory submissions with platform instructions, a reusable product brief and a local tracker. Pay once for your own products. Get paying customers for your SaaS. Use your AI agent to prepare and submit your product to relevant software directories—sites where people browse and compare tools. LaunchRepo gives it the platform instructions, your product brief and a record of each submission’s status. A downloadable toolkit you run with your own agent. You handle logins and verification, and decide what it may publish. ## Start here - [Product and current price](https://launchrepo.dev/pricing/): purchase details, licence, requirements and additional costs. - [Machine-readable pricing](https://launchrepo.dev/pricing.md): the same price source as the public pricing page. - [Workflow and setup check](https://launchrepo.dev/how-it-works/#setup-check): what the agent does and when the owner must step in. - [Founder and publisher](https://launchrepo.dev/about/aleks/): who built LaunchRepo. - [Original directory research](https://launchrepo.dev/blog/directory-status-index/): dated aggregate counts and counting method; the full catalog and playbooks are delivered after purchase. ## Key facts - Product: a downloadable toolkit (private GitHub repository) you run with your own AI agent to prepare, submit and track your SaaS on software directories and launch platforms. - Price: €49.00 one-time incl. 19 % VAT at the regular checkout (regular price €69.00 minus an automatic €20 discount). The price does not rise; live price: https://launchrepo.dev/pricing/ - Licence: unlimited products you or your company own; repository access for one GitHub account; client work needs a separate licence. - Requirements: Git, Python 3.10+ on Windows, macOS or Linux, Chrome, Node.js LTS with npm, and an agent with local-file and Chrome DevTools MCP access (e.g. Claude Code, Codex, Cursor with a browser integration). Toolkit documentation and playbooks are English. - Not a hosted or managed submission service. No guaranteed listings, traffic, backlinks or rankings; agent usage is billed by your AI provider; platforms decide whether to publish. - Catalog evidence as of 2026-10-07: 299 active guides; 84 verified free routes; 156 conditional-free routes with explicit prerequisites; 5 research-only routes; 53 currently unavailable routes. 50 known mandatory-paid routes are excluded from active recommendations. Unknown is not free. - Proof: SeoMap, our own pilot, has public listings such as https://findly.tools/seomap (a listing, not a traffic or revenue result). - Videos (English audio; transcripts and subtitles in 12 languages): LaunchRepo live demo: an AI agent submits a new app to directories (5:54) https://launchrepo.dev/videos/demo/; LaunchRepo explained in under 3 minutes (2:47) https://launchrepo.dev/videos/explained/ - Publisher: The CodeCave GmbH, Frechen, Germany. Founder: Aleksandar Vuk Jovanovic (@AleksDoesCode), profile: https://launchrepo.dev/about/aleks/. Contact: info@thecodecave.de ## Where could people discover your product? - AlternativeTo: Finding alternatives to familiar software. Your product solves a similar job in a different way. - G2: Researching business software and reviews. Your product fits a category buyers already research. - Dev Tools Dir: Discovering tools for developers. Developers are the people your product serves. - Product Hunt: Exploring new tech products. You have a new product to introduce to a launch community. The default queue uses only current, evidenced zero-cost routes. Unknown and mandatory-paid routes stay out. ## What is included - Platform playbooks: Readable Markdown instructions covering preparation, submission steps, known hurdles and confirmation. - A reusable product brief: Your facts, approved claims, copy and assets in one place. - Selection guidance: Judge fit, audience evidence and effort before submitting. - A local dashboard and tracker: A page on your computer showing products, saved statuses, public links and next actions. Your agent checks platforms and updates the records when you run it. - Setup guides and prompts: Create your private workspace, connect your browser and resume later. 299 active guides as of October 7, 2026: 84 verified free, 156 conditional free, 5 research-only and 53 currently unavailable. Your launch uses only the suitable subset. ## How it works 1. Describe your product once. Gather the facts, approved claims and images with your agent. Set its registration and publication permissions. 2. Plan a run of 10 submissions. Start with a target of 10 relevant free submissions and one browser worker. If fewer suitable routes exist, the planner keeps the smaller truthful target instead of adding unknown or paid routes. 3. Prepare, submit and follow up. Copy the run prompt and use /goal if your agent supports it. Your agent records confirmations and continues toward the saved target. You handle logins and human challenges; later sessions resume the remaining work. - You: Decide which platforms and claims to use; Log in, verify accounts, solve CAPTCHA and 2FA; Grant or withhold submission permission. - Your agent: Reads the platform guide and your brief; Prepares copy within the form limits and submits; Records the confirmed state and next action. - The platform: Reviews the submission on its own terms; Publishes, schedules, queues or declines; Sets its own fees and timing. You run your agent with your accounts. LaunchRepo supplies the instructions and tracking; platforms decide whether to publish. - [Launch every product you own, again and again](https://launchrepo.dev/features/repeatable-saas-launches/): Set up your directory launch once and repeat it for every SaaS you own: shared catalog and agent setup, one dashboard, one license for unlimited own products. Licence terms quoted from the Terms of Service; dashboard screenshot from the kit's demo mode with fictional products. - [Only the directories that fit your product](https://launchrepo.dev/features/platform-selection/): How LaunchRepo picks the right directories for your SaaS: dated route status, product fit, existing listings and permission, then a small run of up to 10. Try it. Includes a browser-only demo of the selection lanes on ten example route types (no directory names) and real dashboard screenshots from the kit's demo mode. - [Know where every submission stands](https://launchrepo.dev/features/submission-tracking/): Track every directory submission with LaunchRepo: 11 evidence-based states, honest run counts, saved CAPTCHA handoffs and a resume that never submits twice. Try the demo. Includes a browser-only tracker demo on six example route types (no directory names) and real dashboard screenshots from the kit's demo mode. ## Sample guide Public Product Hunt sample with preparation, steps, pitfalls and confirmation: https://launchrepo.dev/directories/producthunt/. Capability check before buying: https://launchrepo.dev/how-it-works/#setup-check ## FAQ ### Will it bring traffic or customers? It creates more relevant places where your product may be discovered and gives you a clean record of what was submitted, approved and published. We have not measured attributable traffic, rankings or customer growth, and no platform, backlink or outcome is guaranteed. ### Do I need to understand SEO? No specialist SEO knowledge is required to run the workflow. Your agent checks fit and current rules, while the tracker separates attempts from public listings. Whether a published page links, ranks or sends visitors must be measured after it goes live. ### Why pay when I could just tell Claude to do it? Because the value isn’t the list of directories — anyone can find a list. It’s the hand-written playbook behind every directory: which route to take, what each field expects, where the traps are and what to do when something goes wrong. Without it, your agent guesses and burns tokens on trial and error. With it, it follows a tested path, submits properly and records every result, so nothing gets lost or submitted twice. ### Can I review the copy before anything is submitted? Yes: ask your agent to prepare drafts and withhold submission permission until you review them. You can also grant permission for final submissions in advance. These permissions are instructions for your agent, rather than a software-enforced approval gate. ### How is it automated — and does it break when a site changes its UI? Your agent drives a real Chrome browser and reads every page the way a person does, instead of clicking hard-coded selectors that snap with the next redesign. That’s our secret sauce: each playbook describes what the directory needs and what a finished submission looks like, not which pixel to click. A moved button or a reworked form doesn’t stop it. When a directory changes more than that, we re-test the route and publish the updated playbook for every buyer. ### How long does setup take, and what will my agent cost? Setup is a one-time first session that establishes your workspace, browser connection and run target; later sessions reuse it. After that, plan roughly 3–5 minutes per directory. What your agent costs depends on your provider and plan, so check its billing before buying. ### Can my team use it? Yes, for products you or your company own, with repository access bound to one GitHub account. Client work requires a separate license. Redistribution is not included. ### What exactly do I get — what do I clone? Access to a private GitHub repository. You clone it and use everything locally with your own agent: the directory catalog, a playbook for every directory, your product brief, the submission tracker and a local dashboard. No SaaS, no extra login, nothing uploaded to us. ### Won’t Google flag me for getting so many backlinks at once? Unlikely, and that’s built into how free directories work. Free listings wait in a review queue, so they go live anywhere from one day to about twelve weeks after you submit. The links arrive one by one over a long period, not as a sudden spike. How Google weighs any single link is up to Google. ### Are submissions automated or do I have to do them by hand? Largely automated. Your agent creates the account, confirms the verification email, fills in the forms and submits the listing on its own. It hands you CAPTCHAs, two-factor codes and logins it can’t complete (see below) and stops before anything that would cost money. ### What about CAPTCHAs? Some directories show a CAPTCHA. Your agent pauses there, you solve it once in your own browser, and it carries on. Most directories have none at all. Don’t want to deal with any? Tell your agent at the start and it filters those directories out automatically. ### How long does each directory take? Plan on roughly 3–5 minutes per directory. It depends on whether you already have an account there, whether you sign in with Google or with email and password (which adds a confirmation email), and how many forms the directory has. With enough hardware, you can run up to two agent sessions in parallel. ### How many of my products can I submit? As many as you like — there’s no limit. Buy once and use it for all of your own products, as often as you want, for good. Client work needs a separate license. ### Do I get lifetime access to updates? Yes. One payment, no subscription: every update we publish, including new directories and playbooks, lands in your repository at no extra cost. The changelog shows everything that has shipped so far. ## Launch platforms covered (examples) Product Hunt, TinyLaunch, Uneed, Hacker News, G2, Indie Hackers, PitchWall, Peerlist, SourceForge, Crunchbase. 289 more platforms, with their requirements and step-by-step playbooks, ship in the private repository after purchase. ## Pricing - [LaunchRepo pricing — One-time toolkit purchase](https://launchrepo.dev/pricing/): See what’s included, the setup requirements and the costs your AI provider bills separately. Buy once at €49.00 and reuse LaunchRepo for your own products. - [LaunchRepo affiliate program: 30 % on every sale](https://launchrepo.dev/affiliates/): Recommend LaunchRepo and earn 30 % of the net price on every sale. Your audience saves €20; commissions are paid monthly by SEPA transfer. ## Comparisons and alternatives Policy: competitor facts (price, model, features) are taken from each vendor's public pages and dated with the day they were checked; they are not updated automatically, so re-check the vendor before relying on them. Each page also names what the competitor does better. No ratings, reviews or rankings are claimed. - [LaunchRepo compared with launch tools and services](https://launchrepo.dev/vs/): LaunchRepo side by side with directory submission services and SEO tools: pricing model, who does the work, what you own. Every fact dated and sourced. - [LaunchRepo vs Outrank: content SEO or distribution](https://launchrepo.dev/vs/outrank/): Outrank publishes AI SEO articles from $99 a month. LaunchRepo is a pay-once repo with 299 directory playbooks your own agent uses to submit your product. Checked on 2026-09-30; price from: $99 per month (Organic Growth Plan), or $999 per year. - [ListingBott vs LaunchRepo: costs, work and account ownership](https://launchrepo.dev/vs/listingbott/): Compare ListingBott’s directory submission service with LaunchRepo’s reusable toolkit: who does the work, who owns the accounts and what each purchase covers. Checked on 2026-09-30; price from: Historical snapshot 2026-09-30: $499 one-time per website (Standard, 100 listings); $999 Premium; $99 per month for 20 listings. - [LaunchRepo vs StartupSubmit: buy a launch or own it](https://launchrepo.dev/vs/startupsubmit/): StartupSubmit submits your startup manually from $99 per product. LaunchRepo: one licence, and your agent works 299 directories for each of your products. Checked on 2026-09-30; price from: $99 one-time (Starter, 60+ directories); Growth $199 (150+); Authority $199 (200+). - [LaunchRepo vs Submit Juice: DA guarantees or a toolkit](https://launchrepo.dev/vs/submitjuice/): Submit Juice submits your startup by hand from $197 per site with DA guarantees. LaunchRepo: pay once; your agent works 299 directories for every product. Checked on 2026-09-30; price from: $197 one-time (Classic, 20 directories); Premium $297 (50); Premium Plus $983 (until DA 40+); free DIY list of 152+. - [LaunchRepo vs LaunchDirectories: one launch or all](https://launchrepo.dev/vs/launchdirectories/): LaunchDirectories submits your startup manually from $99 per product. With LaunchRepo you pay once; your own agent works 299 directories for every product. Checked on 2026-09-30; price from: $99 one-time (Starter List, 30+ directories); Pro List $149 (60+); Premium List $199 (100+). - [LaunchRepo vs SubmitSaaS: 48-hour service or toolkit](https://launchrepo.dev/vs/submitsaas/): SubmitSaaS submits your SaaS to 60–140+ free directories in 48 hours from $60 per product. You pay for LaunchRepo once; your agent works 299 playbooks. Checked on 2026-09-30; price from: $60 one-time (Basic, 60+ submissions); Standard $100 (100+); Premium $140 (140+). - [LaunchRepo vs GetMoreBacklinks: packages or a toolkit](https://launchrepo.dev/vs/getmorebacklinks/): GetMoreBacklinks sells backlink packages from $379 per website and had paused new orders. LaunchRepo is a one-time licence; your agent works 299 playbooks. Checked on 2026-09-30; price from: $379 one-time per website (Advanced, 100 submissions); Business $579 (200); Pro $779 (200 + 5 blogs). - [LaunchRepo vs AutoSaaSLaunch: extension or agent](https://launchrepo.dev/vs/autosaaslaunch/): AutoSaaSLaunch is a $29 lifetime Chrome extension that auto-fills directory forms. LaunchRepo is paid once; your own agent works 299 playbooks. Checked on 2026-09-30; price from: $29 one-time, lifetime (Founding Member, crossed-out $50); beta. - [LaunchRepo vs SubmitMap: own repo or MCP subscription](https://launchrepo.dev/vs/submitmap/): SubmitMap maps 826 launch platforms for free and sells an MCP dashboard from $9 a month. LaunchRepo is paid once: 299 playbooks your agent runs. Checked on 2026-10-01; price from: Free to read; paid from $9 per month (Indie), $15 (Studio), $29 per month or $190 per year (Unlimited), or $250 once (Lifetime). - [LaunchRepo vs Submitator: $29 automation or your agent](https://launchrepo.dev/vs/submitator/): Submitator submits your startup to 30–160 directories for you, from $29 per product. LaunchRepo is paid once, and your agent works 299 playbooks. Checked on 2026-10-01; price from: $29 one-time per product (Starter, 30 directories); Growth $49 (60); Scale $79 (100); All Directories $149. - [LaunchRepo vs SubmitMatic: $60 service or your own agent](https://launchrepo.dev/vs/submitmatic/): SubmitMatic submits one product to 60–140+ directories for $60 to $140, done for you. LaunchRepo is paid once, and your own agent works 299 playbooks. Checked on 2026-10-01; price from: $60 one-time per product (Basic, 60+ directories); Standard $100 (100+); Premium $140 (140+). - [LaunchRepo vs Blastra: launch kit or review-site upkeep](https://launchrepo.dev/vs/blastra/): Blastra keeps B2B review-site listings current, from $99 setup plus $59 a month. LaunchRepo is paid once so your own agent can launch with 299 playbooks. Checked on 2026-10-01; price from: $99 setup + $59/month (Pulse, 3 listings, first month included); $299 + $99/month (Minimum Viable Presence, 12 listings). - [LaunchRepo vs backlink-pilot: free script or curated kit](https://launchrepo.dev/vs/backlink-pilot/): backlink-pilot is free MIT code that auto-fills directory forms; we counted 180 auto targets, not 226. LaunchRepo: 299 curated playbooks, paid once. Checked on 2026-10-01; price from: free (MIT licence). - [Directory submission on Fiverr vs LaunchRepo: fees, risks](https://launchrepo.dev/vs/fiverr-directory-submission/): Fiverr lists 681 directory submission gigs, most for local citations, plus a 5.5% fee. LaunchRepo: 299 playbooks your own agent runs, paid once. Checked on 2026-10-01; price from: set by each seller per package; plus Fiverr’s 5.5% service fee and $3 under $100. - [LaunchRepo vs manual submission: hours or a toolkit](https://launchrepo.dev/vs/manual-submission/): Submitting by hand costs no software, only your time. Set your own minutes per form, directories and products in the calculator. LaunchRepo: pay once. (Modelled comparison, not a vendor.) - [Directory submission tools and services compared](https://launchrepo.dev/alternatives/): Every directory submission service and launch tool we checked, side by side: pricing model, price from, who it is for, date checked. Three models explained. - [Outrank alternative: pay once, launch every product](https://launchrepo.dev/alternatives/outrank/): Looking for an Outrank alternative for directory submissions? LaunchRepo is paid once, not $99 a month per website: your agent works 299 directories. Checked on 2026-09-30. - [ListingBott alternative: your agent, your accounts](https://launchrepo.dev/alternatives/listingbott/): Looking for a ListingBott alternative? Compare running your own agent with a managed service, including account ownership, setup and repeat product launches. Checked on 2026-09-30. - [StartupSubmit alternative: one licence, every launch](https://launchrepo.dev/alternatives/startupsubmit/): Looking for a StartupSubmit alternative? StartupSubmit is from $99 per product. LaunchRepo: pay once for every product; your agent works 299 directories. Checked on 2026-09-30. - [Submit Juice alternative: a toolkit you keep](https://launchrepo.dev/alternatives/submitjuice/): Looking for a Submit Juice alternative? Submit Juice is from $197 per site. LaunchRepo is one licence for every product; your own agent works 299 directories. Checked on 2026-09-30. - [LaunchDirectories alternative: listings in your accounts](https://launchrepo.dev/alternatives/launchdirectories/): Looking for a LaunchDirectories alternative? It is $99–$199 per product in accounts they create. With LaunchRepo you pay once: your agent, your own accounts. Checked on 2026-09-30. - [SubmitSaaS alternative: know what went live](https://launchrepo.dev/alternatives/submitsaas/): Looking for a SubmitSaaS alternative? SubmitSaaS is from $60 per product in 48 hours. With LaunchRepo you pay once and your agent works 299 directories. Checked on 2026-09-30. - [GetMoreBacklinks alternative: available, pay once](https://launchrepo.dev/alternatives/getmorebacklinks/): Looking for a GetMoreBacklinks alternative? Orders were paused when we checked. LaunchRepo: one licence for all your products; your agent works 299 directories. Checked on 2026-09-30. - [AutoSaaSLaunch alternative: 299 playbooks, your agent](https://launchrepo.dev/alternatives/autosaaslaunch/): Looking for an AutoSaaSLaunch alternative? It is a $29 autofill extension in beta. LaunchRepo: pay once, and your own agent works through 299 playbooks. Checked on 2026-09-30. - [Playwright MCP vs Chrome DevTools MCP](https://launchrepo.dev/compare/playwright-mcp-vs-chrome-devtools-mcp/): Playwright MCP and Chrome DevTools MCP on one local test form: fields, file upload, iframes, handoff to a person and restarts. Five runs each, plus agent-browser. Test page: https://launchrepo.dev/compare/playwright-mcp-vs-chrome-devtools-mcp/browser-mcp-test.mjs - [Claude in Chrome vs Chrome DevTools MCP](https://launchrepo.dev/compare/claude-in-chrome-vs-chrome-devtools-mcp/): Claude in Chrome, Anthropic’s browser extension, next to Chrome DevTools MCP, the open-source MCP server: requirements, logins, safety, uploads and handoff. - [Product Hunt vs Hacker News](https://launchrepo.dev/compare/product-hunt-vs-hacker-news/): Product Hunt vs Hacker News for a developer launch: audience, format, rules and what success means on each, with data from 44,624 Show HN posts. - [BetaList vs Product Hunt](https://launchrepo.dev/compare/betalist-vs-product-hunt/): BetaList vs Product Hunt: which fits your stage. Official rules for waitlists and live products, BetaList’s paid submission and a three-question picker. - [Uneed vs Product Hunt](https://launchrepo.dev/compare/uneed-vs-product-hunt/): Uneed assigns free launch dates from a waiting line; Product Hunt lets you pick your day for free. Current Uneed rules, dated, plus a date planner and picker. - [Product Hunt vs AppSumo](https://launchrepo.dev/compare/product-hunt-vs-appsumo/): Product Hunt is a free launch day; AppSumo sells your product as a deal and you support those buyers for years. Partner terms, dates and a picker. - [G2 vs Capterra](https://launchrepo.dev/compare/g2-vs-capterra/): G2 and Capterra side by side from the vendor side: listing rules, review thresholds, review rules and paid options, from their own pages, plus a picker. - [DEV vs Hashnode vs Medium](https://launchrepo.dev/compare/dev-to-vs-hashnode-vs-medium/): Where to republish a launch write-up: canonical links, ownership and community rules on DEV, Hashnode and Medium, from their docs, plus a cross-post kit. ## Use cases - [Who LaunchRepo is for: launch use cases by audience](https://launchrepo.dev/for/): Five use cases: indie hackers, SaaS founders, AI tools, developer tools and agent builders. Which directory categories matter and how your agent works the list. - [Indie hacker marketing: get your side project listed](https://launchrepo.dev/for/indie-hackers/): For indie hackers: launch a side project on 102 launch platforms and 7 communities with your own AI agent. Pay once, reuse it for every product you ship. - [SaaS distribution strategy: get listed with your agent](https://launchrepo.dev/for/saas-founders/): For SaaS founders: launch on 102 launch platforms, 76 tool directories and 27 B2B review sites with your own agent. One licence, every product. - [How to market an AI tool: get listed where people look](https://launchrepo.dev/for/ai-tools/): For AI tools: launch on 70 AI tool directories and 102 launch platforms with your own AI agent. Playbooks, product context and a tracker — pay once. - [How to market a developer tool: list it where devs look](https://launchrepo.dev/for/developer-tools/): For developer tools: launch a CLI, SDK, API or open-source project on 76 tool directories and 102 launch platforms with your own coding agent. - [How to market an AI agent: let your own agent list it](https://launchrepo.dev/for/agent-builders/): For agent builders: launch an AI agent or agentic product on 70 AI directories and 102 launch platforms — with your own agent doing the submissions. - [How to market vibe coded apps: an honest plan](https://launchrepo.dev/for/vibe-coders/): How to market vibe coded apps built with Lovable, Bolt, Cursor or Claude Code: seven steps, real directory numbers and launch rules checked September 28, 2026. Facts checked on 2026-09-28 at the source; own numbers. Available in 12 languages. - [Micro SaaS marketing: a zero-budget strategy](https://launchrepo.dev/for/micro-saas/): Micro SaaS marketing for $5–50/month plans: small-ticket math, payment fees checked September 28, 2026, zero-budget moves and why paid ads rarely pay back. Facts checked on 2026-09-28 at the source; own numbers. Available in 12 languages. - [Distribution for open source maintainers](https://launchrepo.dev/for/open-source-maintainers/): Promote your open source project where developers look: README, GitHub topics, awesome lists, Show HN and your ecosystem. Rules quoted, plus a free plan builder. Rules quoted from GitHub Docs, the awesome list template and Show HN, checked on 2026-10-01; includes a browser-only plan builder. - [Distribution for Chrome extension developers](https://launchrepo.dev/for/chrome-extension-developers/): Promote a Chrome extension with a strong Web Store listing, a planned release and the right channels. Official rules quoted, plus a free release checker. Chrome Web Store, Edge and Firefox rules quoted, checked on 2026-10-01; includes a browser-only release checker. LaunchRepo does not publish to browser stores. - [API distribution: from a public example to the marketplaces](https://launchrepo.dev/for/api-developers/): How to market and sell an API: a public example that reaches a first 200 OK, Postman, RapidAPI and public-apis rules, and a free OpenAPI listing check. RapidAPI, Postman, public-apis and APIs.guru rules quoted, checked on 2026-10-01. LaunchRepo does not submit APIs to these marketplaces. - [Works with Claude Code, Codex, Cursor and browser agents](https://launchrepo.dev/with/): LaunchRepo runs with the agent you already use. One page each for Claude Code, Codex, Cursor, browser agents and more: setup, the start prompt, handoffs. - [Launch your SaaS on directories with Claude Code](https://launchrepo.dev/with/claude-code/): Run LaunchRepo with Claude Code: it reads the 299 playbooks and product.json, drives your logged-in Chrome via MCP and records every outcome. - [Launch your SaaS on directories with Codex](https://launchrepo.dev/with/codex/): Run LaunchRepo with Codex: it reads the 299 directory playbooks and product.json, drives your logged-in Chrome via an MCP browser server and records outcomes. - [Launch your SaaS on directories with Cursor](https://launchrepo.dev/with/cursor/): Run LaunchRepo with Cursor’s agent: it reads the 299 playbooks and product.json, drives your logged-in Chrome via MCP and records every outcome. - [Launch your SaaS on directories with a browser agent](https://launchrepo.dev/with/browser-agents/): Run LaunchRepo with a browser agent: what it must be able to read, how the 299 playbooks and product.json feed it, and which steps stay with you. - [OpenClaw marketing: launch your SaaS with your agent](https://launchrepo.dev/with/openclaw/): Can OpenClaw handle marketing and the launch of your SaaS? Skills, browser profiles, automations, and where logins, CAPTCHA and 2FA still need you. Facts about OpenClaw checked on 2026-09-28 against its public docs. Available in 12 languages. - [ChatGPT agent marketing: launch after agent mode](https://launchrepo.dev/with/chatgpt-agent/): ChatGPT agent mode is gone. What ChatGPT Work and its cloud browser can do for a SaaS launch, where sign-ins and blocks stop it, and how Codex fits in. Facts about ChatGPT agent checked on 2026-09-28 against its public docs. Available in 12 languages. - [Gemini CLI marketing: launch your SaaS from the terminal](https://launchrepo.dev/with/gemini-cli/): Can Gemini CLI handle the marketing launch of your SaaS? GEMINI.md, MCP, the browser agent, and where logins, CAPTCHA and 2FA still need you. Facts about Gemini CLI checked on 2026-09-29 against its public docs. Available in 12 languages. - [GitHub Copilot marketing: launch a SaaS with agent mode](https://launchrepo.dev/with/github-copilot/): Can GitHub Copilot launch your SaaS? Agent mode, Copilot CLI and MCP in your own Chrome, why the cloud agent can’t submit, and where logins still need you. Facts about GitHub Copilot checked on 2026-09-29 against its public docs. Available in 12 languages. - [Windsurf AI marketing: launch your SaaS from your IDE](https://launchrepo.dev/with/windsurf/): Windsurf is now Devin Desktop. What its agent can do to list your SaaS on directories, how MCP drives your Chrome, and where logins, CAPTCHA and 2FA need you. Facts about Windsurf checked on 2026-09-29 against its public docs. Available in 12 languages. - [LaunchRepo with Cline: browser setup that works](https://launchrepo.dev/with/cline/): Add Chrome DevTools MCP to Cline in one command. Tested on Cline CLI 3.0.67: the config file that loads, silent mistakes, the 8,000-character cut, resume. Tested with Cline CLI 3.0.67 and Chrome DevTools MCP 1.10.1; not a certification. - [LaunchRepo with OpenCode: browser MCP setup, tested](https://launchrepo.dev/with/opencode/): Add Chrome DevTools MCP to opencode.json in one block. Tested on OpenCode 1.18.34: which config files load, permissions, and resuming a session after a CAPTCHA. Tested with OpenCode 1.18.34 and Chrome DevTools MCP 1.10.1; not a certification. - [LaunchRepo with Kiro: where the browser config goes](https://launchrepo.dev/with/kiro/): Build the Kiro mcp.json for Chrome DevTools MCP: workspace, user or agent scope, who approves browser actions, and how to resume after a CAPTCHA or 2FA handoff. Config builder plus checks of Kiro CLI 2.26.1 without an account; not a certification. ## Blog - [Launch directory status index](https://launchrepo.dev/blog/directory-status-index/) (2026-10-01): Dated statistics on 349 launch directories we checked: how many have a free route, how many are paid-only or offline, and exactly how we counted. - [Does llms.txt help? What it does and what is proven](https://launchrepo.dev/blog/does-llms-txt-help/) (2026-10-01): What llms.txt is, what Google said on 15 June 2026, what a 300,000-domain study can and cannot prove, and who really reads the file. Checked 1 October 2026. - [Earning GitHub stars through real usefulness](https://launchrepo.dev/blog/earn-github-stars/) (2026-10-01): What a GitHub star means, what research found about 6 million suspected fake stars, and what our own Show HN measurement shows about how real stars arrive. - [Your first SaaS users: how to choose the right channels](https://launchrepo.dev/blog/first-100-saas-users/) (2026-09-30): Where the first users of a SaaS come from: a channel matrix with cost and time to a first signal, dated public examples, and a four-week test to pick your two. - [Best startup directories to launch a SaaS in 2026](https://launchrepo.dev/blog/best-startup-directories-2026/) (2026-09-17): How to choose startup directories for a SaaS launch: six categories, a five-minute route check, a worked example and a shortlist that fits your product. - [Coding agent vs browser agent vs done-for-you service](https://launchrepo.dev/blog/coding-agent-vs-browser-agent-vs-done-for-you/) (2026-09-17): Coding agent, browser agent or done-for-you service for directory submissions: what each needs, costs and leaves you owning, plus a five-question decision path. - [Directory backlinks: what we can prove, and what we cannot](https://launchrepo.dev/blog/directory-backlinks-what-we-can-prove/) (2026-09-17): Are directory backlinks worth it? What Google says about directory links, three checks that take five minutes, and what you may honestly claim afterwards. - [Directory submission services compared: 3 pricing models](https://launchrepo.dev/blog/directory-submission-services-compared/) (2026-09-17): Directory submission service pricing explained: per product, subscription or pay once, with prices published on 30 September 2026 and the cost for 1–3 products. - [Launch-date floor: when should directory listings go live?](https://launchrepo.dev/blog/launch-date-floor-when-should-listings-go-live/) (2026-09-17): When to submit to directories before a launch: why free listings go live weeks later, a four-week timeline, and a date floor that stops early scheduling. - [Launch a SaaS on directories with Claude Code: walkthrough](https://launchrepo.dev/blog/launch-saas-on-directories-with-claude-code/) (2026-09-17): A Claude Code walkthrough of one directory launch run: the exact start prompt, onboarding, Chrome setup, real tool output and all 11 tracker states. - [Product Hunt launch checklist for solo developers](https://launchrepo.dev/blog/product-hunt-launch-checklist-solo-developers/) (2026-09-17): A Product Hunt launch checklist for solo makers: account age, 60/500-character copy, 240×240 and 1270×760 images, first comment, date and launch day. - [Submitted, pending, scheduled, live: why states matter](https://launchrepo.dev/blog/submission-states-submitted-pending-scheduled-live/) (2026-09-17): Pending vs live, scheduled vs submitted: what each directory submission status means, what proves it and how to count them without a false total. - [Why we charge once: a founder's view on pay-once pricing](https://launchrepo.dev/blog/why-we-charge-once/) (2026-09-17): Pay once vs subscription for a developer tool: when each model is cheaper, a break-even example, our flat price and what we do not promise. - [Zero-budget directory launch: what a free run looks like](https://launchrepo.dev/blog/zero-budget-directory-launch/) (2026-09-17): A zero-budget SaaS launch on directories: the free route of six platforms, the upsells to decline, review times of weeks, and what a free run really costs. ## Best-of lists Five editorial shortlists of at most 10 platforms from the kit catalog (299 platforms), ranked by published rules: fit, dated field guide, evidence level, fewest free-route conditions. Available in 12 languages. - [Best AI tool directories: 10 picks with criteria](https://launchrepo.dev/best/ai-tool-directories/): The 10 AI tool directories to start with, picked from 70 in the catalog by published rules: AI fit, evidence level and fewest free-route conditions. - [Best SaaS directories: 10 picks with criteria](https://launchrepo.dev/best/saas-directories/): The 10 SaaS directories and B2B review sites to start with, picked from 102 in the catalog by published rules: fit, evidence and fewest conditions. - [Best startup directories and launch boards: 10 picks](https://launchrepo.dev/best/startup-launch-platforms/): The 10 launch boards to start with, picked from 101 in the catalog by published rules: fit, field guide, evidence level and fewest free-route conditions. - [Developer tools directory: best places to list a dev tool](https://launchrepo.dev/best/developer-tool-directories/): The 10 places to list a developer tool first: specialist directories, then general sites where developers compare tools. 15 dev directories in the catalog. - [Best indie hacker launch platforms and communities](https://launchrepo.dev/best/indie-hacker-launch-platforms/): The 10 places an indie launch should start: maker communities first, then launch boards, picked from 108 in the catalog by published rules. - [Free startup directories: 240 routes, dated data](https://launchrepo.dev/best/free-startup-directories/): Free startup directories, counted: 84 free and 156 conditionally free routes out of 299, 50 removed for fees. 9 re-checked on September 28, 2026. Counts computed from the catalog snapshot of 2026-10-07; 9 platforms named, re-checked on 2026-09-28. Available in 12 languages. - [AI agent directory list: 10 free places for your agent](https://launchrepo.dev/best/ai-agent-directories/): Where to submit an AI agent for free: ten AI agent directories checked on September 28, 2026, with the badge, review and wait behind each free route. 10 platforms, free route checked on 2026-09-28. Available in 12 languages. - [Vibe coded apps directory list: 9 places to list your app](https://launchrepo.dev/best/vibe-coding-directories/): Where to list an app built with Lovable, Bolt, Cursor or Claude Code: nine vibe coding directories checked on September 28, 2026, with what the free route asks. 9 platforms, free route checked on 2026-09-28. Available in 12 languages. - [Product Hunt alternatives: 10 free routes](https://launchrepo.dev/best/product-hunt-alternatives/): Ten Product Hunt alternatives with a free route checked on September 28, 2026: cost, queue, audience and what “live” means, compared with Product Hunt itself. 10 catalog platforms, free route checked on 2026-09-28. Available in 12 languages. - [BetaList alternatives: 10 free places for your beta](https://launchrepo.dev/best/betalist-alternatives/): Ten free BetaList alternatives for makers in beta, checked on September 28, 2026: cost, wait, audience and refund rules compared with paid-only BetaList. 10 catalog platforms, free route checked on 2026-09-28. Available in 12 languages. - [Best Claude Code marketing skills on GitHub](https://launchrepo.dev/best/claude-code-marketing-skills/): Nine open-source Claude Code marketing skills and plugins from GitHub: what each does, license, stars with date, and the distribution gap none of them close. Third-party GitHub repositories, not catalog platforms; licenses and stars checked on 2026-09-28. Available in 12 languages. - [MCP server directories and registries: where to list](https://launchrepo.dev/best/mcp-server-directories/): Where to list an MCP server: the official MCP Registry and nine directories compared by publish route, ownership check and cost. Plus a free server.json builder. Ten MCP registries and directories, checked on 2026-10-01; includes a browser-only server.json builder. - [Startup databases in Europe and Germany: where to list](https://launchrepo.dev/best/european-startup-directories/): European and German startup databases compared: who gets in by country, region and company age, what it costs and how to add your company. Ten places. Ten startup databases, Germany first, checked on 2026-10-01; includes a browser-only eligibility filter. ## Glossary - [AI coding agent](https://launchrepo.dev/glossary/ai-coding-agent/): A model-driven assistant that reads and edits files, runs commands and calls tools in a project — Claude Code, Codex and Cursor are examples. - [Backlink](https://launchrepo.dev/glossary/backlink/): A link from another website to yours. On a directory, the product link on your listing page — if it is a crawlable anchor. - [Boilerplate](https://launchrepo.dev/glossary/boilerplate/): A reusable starting point you own and adapt — code, files and conventions — instead of a service you rent. - [Browser agent](https://launchrepo.dev/glossary/browser-agent/): An agent that operates a web browser — navigating, reading pages, filling forms and clicking — either as a product of its own or a coding agent with a browser tool. - [Chrome DevTools Protocol](https://launchrepo.dev/glossary/chrome-devtools-protocol/): The remote-control interface of Chromium browsers: over a local debugging port a program can inspect and drive tabs. - [Directory badge](https://launchrepo.dev/glossary/directory-badge/): A small linked image the directory asks you to place on your website, often as a condition for a free listing or a dofollow link. - [Directory submission](https://launchrepo.dev/glossary/directory-submission/): The act of entering a product into one directory: account, form, assets, confirmation — and the recorded outcome. - [Dofollow vs. nofollow](https://launchrepo.dev/glossary/dofollow-vs-nofollow/): “Nofollow” is a rel attribute telling search engines not to endorse a link; “dofollow” is marketing shorthand for its absence. - [Domain authority](https://launchrepo.dev/glossary/domain-authority/): A third-party estimate of how strongly a domain might rank. Not a Google metric; useful only as a rough, vendor-specific comparison. - [Done-for-you submission service](https://launchrepo.dev/glossary/done-for-you-submission-service/): A vendor that submits your product to a list of directories on your behalf for a fee, usually per launch or per month. - [Draft vs. submitted](https://launchrepo.dev/glossary/draft-vs-submitted/): Draft means work is saved on your side; submitted means the platform explicitly acknowledged receipt and moderation is open. - [Featured listing / paid placement](https://launchrepo.dev/glossary/featured-listing-paid-placement/): A paid option on a directory — featured spot, sponsored slot, skip-the-queue review — offered next to or instead of the free route. - [IndexNow](https://launchrepo.dev/glossary/indexnow/): An open protocol to notify participating search engines that a URL was added or changed, instead of waiting for a crawl. - [Launch directory](https://launchrepo.dev/glossary/launch-directory/): A website that lists new products around a launch day and keeps the listing as a permanent page. - [Launch-date floor](https://launchrepo.dev/glossary/launch-date-floor/): The earliest date on which any listing for a product may go live — a field the owner sets and the tracker enforces. - [Listing status](https://launchrepo.dev/glossary/listing-status/): The recorded state of one product on one directory — from draft through pending, scheduled and live to blocked or not a fit. - [Live listing](https://launchrepo.dev/glossary/live-listing/): A listing whose public page loads for a logged-out visitor and carries no pending label — verified, with the URL recorded. - [Maker profile](https://launchrepo.dev/glossary/maker-profile/): Your personal account on a launch platform — name, avatar, bio, links — that submissions and comments are attributed to. - [MCP server](https://launchrepo.dev/glossary/mcp-server/): A process that exposes tools to an AI agent through the Model Context Protocol — for LaunchRepo, the one that hands the agent a Chrome tab. - [Product context file](https://launchrepo.dev/glossary/product-context-file/): One structured file with the facts and copy about your product — product.json in LaunchRepo — that the agent reads for every submission. - [Product launch platform](https://launchrepo.dev/glossary/product-launch-platform/): A site built around launch events: a product goes live on a chosen day, collects votes or comments and is ranked against others launching that day. - [Scheduled listing](https://launchrepo.dev/glossary/scheduled-listing/): A listing for which the platform confirmed a future launch date; approval may still be outstanding and the page is not yet public. - [Software directory](https://launchrepo.dev/glossary/software-directory/): A catalog of software organized by category, with a profile page per tool, alternatives and often user reviews. - [Startup directory](https://launchrepo.dev/glossary/startup-directory/): A directory of companies rather than products: profiles with founders, funding stage, location and a website link. ## 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 account allowed one scheduled launch at a time and blocked a new submission while another product held a launch date; unscheduled drafts did not count. 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. ## Directory categories - [Product launch platforms in the catalog](https://launchrepo.dev/directories/category/product-launch/): how this platform type works (requirements, review, what counts as live), route status counts and public profiles; 101 platforms in the catalog. Available in 12 languages. - [AI tool directories in the catalog](https://launchrepo.dev/directories/category/ai-tools/): how this platform type works (requirements, review, what counts as live), route status counts and public profiles; 70 platforms in the catalog. Available in 12 languages. - [Software and tool directories in the catalog](https://launchrepo.dev/directories/category/software-tools/): how this platform type works (requirements, review, what counts as live), route status counts and public profiles; 75 platforms in the catalog. Available in 12 languages. - [B2B software review sites in the catalog](https://launchrepo.dev/directories/category/b2b-software/): how this platform type works (requirements, review, what counts as live), route status counts and public profiles; 27 platforms in the catalog. Available in 12 languages. - [Company and startup profile platforms](https://launchrepo.dev/directories/category/company-profile/): how this platform type works (requirements, review, what counts as live), route status counts and public profiles; 17 platforms in the catalog. Available in 12 languages. - [Community platforms in the catalog](https://launchrepo.dev/directories/category/community/): how this platform type works (requirements, review, what counts as live), route status counts and public profiles; 7 platforms in the catalog. Available in 12 languages. ## Directory profiles - [AlternativeTo: adding your app as an alternative](https://launchrepo.dev/directories/alternativeto/): AlternativeTo is a crowd-sourced catalog of software alternatives across Windows, Mac, Linux, iOS, Android and the web. The homepage counts more than 150,000 apps ranked by more than two million user opinions. - [SourceForge: request a business software listing](https://launchrepo.dev/directories/sourceforge/): SourceForge has two tracks: open-source project hosting with downloads, and a business software directory that its About page puts at over 124,400 titles, with ratings, comparisons and category rankings. SourceForge cites more than 20 million visitors a month; commercial products use the vendor route. - [Show HN: what it is, rules and how to submit](https://launchrepo.dev/directories/hackernews/): Show HN means sharing something you personally built so Hacker News readers can try it and give feedback. A working app, tool or demo can qualify; a landing page, waitlist, newsletter or blog post cannot. Make it easy to try, ideally without signup, and be available to explain how and why you built it. - [Capterra: getting listed through G2 Digital Markets](https://launchrepo.dev/directories/capterra/): Capterra is a software discovery site with verified user reviews and comparisons that advertises more than 25 years of software advice. Its vendor page is now branded “powered by G2 Digital Markets”: the Get Your Product Listed button leads to G2’s add-product form at g2.com/products/new, and vendor accounts log in at app.g2digitalmarkets.com. Public field guides and profiles cover 10 of 299 catalog platforms; the others ship in the private repository after purchase. ## Launch planning guides - [Start LaunchRepo in three steps](https://launchrepo.dev/guides/start-in-three-steps/): Clone the repository, paste one prompt into your coding agent, open the dashboard link. What each step does, what you need installed, and how to do it by hand. - [Connect your coding agent to your Chrome](https://launchrepo.dev/guides/connect-your-agent-to-chrome/): Two ways to give your agent a browser you can watch: Chrome DevTools MCP with auto-connect, or a dedicated CDP profile on port 9222 — and the smoke check. - [Your first session: onboarding led by the agent](https://launchrepo.dev/guides/first-session-onboarding/): The seven phases of the kit’s agent-led onboarding, from product brief to first real submission: what the agent asks and which files it fills so work resumes. - [The local dashboard: your workspace, as the agent sees it](https://launchrepo.dev/guides/local-dashboard/): What the kit’s local dashboard shows — products, onboarding, states, handoffs, follow-ups — how to start it, what it writes and the boundaries it never crosses. - [Confirm how you are represented before listings go public](https://launchrepo.dev/guides/confirm-public-representation/): The kit’s representation briefing: three concrete examples of how the agent will describe you — bio, launch intro, why-I-built-this — approved before a listing. - [Set a launch-date floor before anything is scheduled](https://launchrepo.dev/guides/launch-date-floor/): How earliest_launch_date in product.json works: what the tracker refuses, what it cannot influence, why free directories publish late, and how to pick the date. - [Recording outcomes: states, evidence and record.py](https://launchrepo.dev/guides/recording-outcomes/): How the kit’s tracker records what actually happened on a directory: the eleven states, the observation each requires, the record.py flags and the note rules. - [A launch run from start to finish](https://launchrepo.dev/guides/launch-run-from-start-to-finish/): One directory batch with the kit, end to end: brief, batch selection, one platform at a time, evidence-based states, resume rules, and a realistic first result. - [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. ## Product Hunt rules, checked against the official pages - [Product Hunt featuring and relaunch rules explained](https://launchrepo.dev/guides/product-hunt-launch-rules/): Will Product Hunt feature your product, and when can you launch again? The official featuring and relaunch rules, quoted and dated, with a quick rule check. - [Product Hunt launch services: what to pay for and what to skip](https://launchrepo.dev/guides/product-hunt-launch-services/): Should you pay a Product Hunt launch service or hunter? What the official rules allow and forbid, a risk table by service type, and a quick offer check. ## Launch timing and Reddit rules, checked against the official pages - [Plan your launch day and hour across time zones](https://launchrepo.dev/guides/best-time-to-launch/): Product Hunt’s day starts at 12:01 am Pacific. See that moment in your own time zone, what Product Hunt says about weekdays and what 44,624 Show HN posts show. - [Promote your SaaS on Reddit without breaking the rules](https://launchrepo.dev/guides/reddit-saas-promotion/): Reddit self-promotion rules for 10 SaaS and startup subreddits, checked and dated, plus Reddit’s spam policy, a draft check and a sample post. ## Pre-launch waitlist and demo video, with a form/email generator and a scene planner - [Build a pre-launch waitlist that turns into first users](https://launchrepo.dev/guides/pre-launch-waitlist/): Build a pre-launch waitlist people actually open: page anatomy, a generator for the signup form and four emails, consent rules and how to convert it at launch. - [Plan your SaaS demo video with a real example](https://launchrepo.dev/guides/saas-demo-video/): Plan a SaaS demo video with a real example: our 5:54 demo broken down scene by scene, a scene planner with script export and the video limits of 8 platforms. ## CAPTCHA and 2FA in agent workflows - [CAPTCHA and 2FA in agent workflows: the controlled handoff](https://launchrepo.dev/guides/ai-agent-captcha-2fa-handoffs/): Your agent prepares the form, pauses at the CAPTCHA or 2FA prompt, you finish it in the same tab, the agent resumes. Flow diagram, live demo form, handoff note. ## Visibility in AI search, from the vendors' own documentation - [Product visibility in AI search: index, retrieval, recommendation](https://launchrepo.dev/guides/product-visibility-in-ai-search/): How AI search finds, fetches and names products: index, retrieval and recommendation explained with official Google, OpenAI, Anthropic and Perplexity sources. Includes a browser-only robots.txt checker for the documented AI crawler tokens and a prompt log template; no model panel, no guaranteed mentions. ## Indexing a new website, from Google's own documentation - [Your new website is not on Google yet? Check it step by step](https://launchrepo.dev/guides/new-website-indexing/): What Google says about indexing times for a new site, a first-week checklist, a decoder for every Search Console status and a page-source check. Free, no login. Includes a first-week checklist (Markdown export), a decoder for Search Console statuses and a browser-only page-source check; no own Search Console timeline claimed. ## Hubs - [Free launch tools](https://launchrepo.dev/tools/): Free launch tools: a launch checklist, image and tagline checkers, a UTM builder, cost calculators and an agent setup check. No sign-up, nothing uploaded. - [Launch templates to copy](https://launchrepo.dev/templates/): Copy-ready launch templates: the LaunchRepo start prompt, Chrome DevTools MCP configs for nine coding agents, a Product Hunt checklist and an outcome record. - [What LaunchRepo does](https://launchrepo.dev/features/): LaunchRepo features one by one: agent-led workflow, nine supported agents, your own Chrome, local dashboard, tracked outcomes, approvals and date floor. - [Launch comparisons](https://launchrepo.dev/compare/): Launch comparisons in one place: coding agent vs browser agent vs service, submission service pricing, pay once vs subscription and LaunchRepo vs others. ## Free launch tools and templates - [SaaS launch checklist](https://launchrepo.dev/tools/saas-launch-checklist/): Free interactive SaaS launch checklist: 30 tasks in six phases from T−30 to T+30, each with the reason and an official source. Progress saved, Markdown export. - [Launch plan template](https://launchrepo.dev/templates/launch-plan/): Free product launch plan template: 22 tasks on real dates from T−30 to T+30, three roles with hours per person, export to CSV or Markdown, printable. - [Launch announcement email templates](https://launchrepo.dev/templates/launch-announcement-emails/): Five plain-text launch emails to copy: waitlist opening, existing users, launch day, relaunch, changelog. Fill in once, copy, and see why each line is there. - [Check your launch images against platform size specs](https://launchrepo.dev/tools/launch-image-sizes/): Check an image against launch specs: OG and LinkedIn previews, Product Hunt, Chrome Web Store, Google Play, GitHub, YouTube. Runs in your browser, no upload. - [Launch tracker template to download](https://launchrepo.dev/templates/launch-tracker/): Free launch tracker template: one row per platform, nine statuses that never double count and three numbers worth reporting. Fill it in here or get the CSV. - [UTM builder for your launch links](https://launchrepo.dev/tools/launch-utm-builder/): Build UTM links for every launch platform at once: existing query and #anchor kept, values encoded, only http(s) accepted. Nothing leaves your browser. - [What directory submissions really cost you](https://launchrepo.dev/tools/directory-submission-cost-calculator/): Calculate what directory submissions cost you: products, attempts, minutes, your hourly rate and agent plan, compared with doing it by hand and with LaunchRepo’s current price. Browser-only; every input is the reader's assumption, amounts in EUR, no outcome or ROI claims. - [Check your tagline against every platform’s character limit](https://launchrepo.dev/tools/tagline-checker/): Count your tagline the way Product Hunt, the App Store, Google Play, X and five more fields do, with emoji and accents counted right. Runs in your browser. - [A lean product brief template for you and your AI agent](https://launchrepo.dev/templates/product-brief/): A one-page product brief with ten fields: problem, audience, solution, scope and success. Fill it in your browser and download Markdown or JSON for your agent. Blank files: https://launchrepo.dev/templates/product-brief/product-brief.en.md, https://launchrepo.dev/templates/product-brief/product-brief.en.json ## Original research - [Launch directory status index](https://launchrepo.dev/blog/directory-status-index/): Edition 1, catalog snapshot of 2026-09-24: shares of free, conditional, paid-only and unavailable launch directories with the full counting method; counts only, no directory names. Aggregates (CSV): https://launchrepo.dev/media/directory-status-index/directory-status-index-2026-09-24.csv - [How to launch on Show HN](https://launchrepo.dev/guides/show-hn-launch/): Show HN rules in the official wording, a quick eligibility check, and what 44,624 Show HN posts from 12 months show about points, timing and titles. Dataset (CSV, derived fields only): https://launchrepo.dev/guides/show-hn-launch/show-hn-sample.csv ## Languages Same slug in every language, with a locale prefix (e.g. https://launchrepo.dev/de/pricing/); each page lists its language versions in its hreflang tags. 182 of 182 public pages exist in all 12 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/) ## Full directory guides ### Product Hunt Source: https://launchrepo.dev/directories/producthunt/ · Observed: 2026-09-13 · Official entry: https://www.producthunt.com/launch 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. **Preparation:** Prepare a personal maker profile, product URL, logo and gallery. The observed form allowed a 60-character tagline and 500-character description. Recheck limits before writing final copy. **Workflow:** Search My Products and the public site first. Add the product URL, select an accurate category, upload real product images and identify the maker. Represent paid products with trial access honestly, then choose and confirm the launch date. **Watch for:** Native selects may require direct interaction. Verify the selected value after scrolling. Do not solicit upvotes or invent testimonials, and do not count a saved draft as a scheduled launch. **What counts as confirmation:** Record scheduled only after the account confirms the date and time zone. On launch day, inspect the public product page before recording live. ### SaaSHub Source: https://launchrepo.dev/directories/saashub/ · Observed: 2026-09-13 · Official entry: https://www.saashub.com/services/submit 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. **Preparation:** Have a live English website on your own domain, a product tagline, contact details and a short list of genuine competitors. Domain ownership verification may be separate from account login. **Workflow:** Start with the product URL and check for an existing listing. Choose two or three precise software categories. Select a real alternative already present in the selector, complete contact fields and inspect the available submission plan. **Watch for:** Do not invent an alternative when a competitor is missing from the selector. A software product should not be presented as an agency. Recheck the plan before submitting; the observed free option is not a permanent pricing promise. **What counts as confirmation:** Keep submitted_pending_review while the page says Pending approval. Verify domain requests separately and check for acceptance before changing to live. ### Uneed Source: https://launchrepo.dev/directories/uneed/ · Observed: 2026-09-13 · Official entry: https://www.uneed.best/submit-a-tool Check account capacity before preparing another launch. The observed free account allowed one scheduled launch at a time and blocked a new submission while another product held a launch date; unscheduled drafts did not count. This is an account constraint, not a verdict on product fit. **Preparation:** Sign in with the intended Google or email account and inspect its unpublished products. Prepare the product URL and launch assets only after understanding which scheduled launch occupies the slot. **Workflow:** Open Submit a tool. If a one-launch limit appears, inspect Manage my products and the waiting list. Reconcile those entries with your own tracker before creating anything else. **Watch for:** Do not delete another product or create extra accounts to evade the limit. A read-only integration cannot submit a product. Stop and ask the owner to decide how to handle existing launches. **What counts as confirmation:** Record blocked with the next action, not submitted. Resume after capacity is legitimately available and confirm the resulting queue or schedule in the account. ### Fazier Source: https://launchrepo.dev/directories/fazier/ · Observed: 2026-09-13 · Official entry: https://fazier.com/submit 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. **Preparation:** Prepare an English website and inspect the current eligibility checklist while signed in. Verify the actual domain in the named rating checker; do not substitute a different authority metric. **Workflow:** Open Submit and inspect the Basic route. Check whether the community requirement is already satisfied. Verify the domain rating and obtain the official badge markup only if you can meet the conditions. **Watch for:** Do not manufacture comments, assert a rating you have not verified or buy an upgrade under a zero-spend mandate. Publishing a badge is a website change that requires the site owner’s authorization. **What counts as confirmation:** Record blocked when the rating or badge condition is unmet. A completed checklist is only preparation: obtain the final submission confirmation before recording pending review. ### PitchWall Source: https://launchrepo.dev/directories/pitchwall/ · Observed: 2026-09-13 · Official entry: https://pitchwall.co/submit 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. **Preparation:** Prepare a complete personal profile, product URL, logo and screenshot. Review login consent and newsletter requirements before proceeding; stop if mandatory consent exceeds your authorization. **Workflow:** Save the profile, inspect the available plan and import the product URL. Replace invented or inaccurate generated text, choose relevant tags and upload real assets. Reopen edited fields to confirm they persisted before Submit for Review. **Watch for:** Some profile fields appeared edited but did not save until native input was used. A long review estimate is not a deadline or guarantee. Check existing records before treating an older directory brand as a new opportunity. **What counts as confirmation:** Record submitted_pending_review only after Under Review is confirmed. Retain the next review date privately and check the existing submission rather than sending a duplicate. ### TinyLaunch Source: https://launchrepo.dev/directories/tinylaunch/ · Observed: 2026-09-13 · Official entry: https://www.tinylaunch.com 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. **Preparation:** Prepare a logo, up to three product images, product URL, category and description. Observed limits were 30 characters for the name and 60 for the tagline. Read the terms and any community pledge before accepting. **Workflow:** Use the homepage Submit Product button; the guessed /submit route failed in the observed run. Create the product, choose an available date and inspect Standard. Set optional services to None, schedule, then use Continue with free launch in the final upgrade dialog. **Watch for:** A cookie overlay can block buttons. Rich-text fields may create empty paragraphs from double line breaks. Recheck all totals and available slots; do not assume the old date, price or availability still applies. **What counts as confirmation:** Confirm the success page and dashboard date. Record scheduled with approval still pending when the dashboard says Waiting for approval. A date on a calendar is not proof that the product is publicly live. ## OpenClaw facts (dated) Source page: https://launchrepo.dev/with/openclaw/ - What it is: An open-source, MIT-licensed personal agent. It runs as a Gateway on your own machine, takes requests from chat apps such as WhatsApp, Telegram, Slack, Discord or Signal, and works with the model you pick. (Source: https://github.com/openclaw/openclaw; checked 2026-09-28) - Release pace: The latest GitHub release when we checked was v2026.9.6, published on September 23, 2026. Behavior can change between releases. (Source: https://github.com/openclaw/openclaw/releases; checked 2026-09-28) - Skills: A skill is a folder with a SKILL.md file: YAML frontmatter plus instructions for when and how to use tools. Skills load from your workspace, your home folder or the bundled set, and install from ClawHub or Git with openclaw skills install. (Source: https://docs.openclaw.ai/tools/skills; checked 2026-09-28) - Browser: Three kinds of browser profile: an isolated, managed “openclaw” profile; the built-in “user” profile, which attaches to your signed-in Chrome through Chrome DevTools MCP; and remote CDP endpoints. (Source: https://docs.openclaw.ai/tools/browser; checked 2026-09-28) - Attaching to your Chrome: The “user” profile needs a Chromium browser version 144 or newer, remote debugging switched on in chrome://inspect, and your approval of the attach prompt. The docs say to use it only when you are at the computer. (Source: https://docs.openclaw.ai/tools/browser/existing-session; checked 2026-09-28) - Logins: The docs tell you to sign in manually, because automated logins often trigger anti-bot defenses and can lock the account. Credentials should stay out of chat. (Source: https://docs.openclaw.ai/tools/browser-login; checked 2026-09-28) - Automations: A built-in scheduler (openclaw automations, alias openclaw cron) wakes the agent at set times and can send the result to a chat channel or a webhook. (Source: https://docs.openclaw.ai/automation/cron-jobs; checked 2026-09-28) - Shell: The exec tool runs shell commands in the workspace, so OpenClaw can run local scripts, such as Python. (Source: https://docs.openclaw.ai/tools/exec; checked 2026-09-28) - Skill security: In February 2026, researchers reported 341 malicious skills among 2,857 audited on ClawHub. ClawHub added malware scanning afterwards. The docs still say to treat third-party skills as untrusted code. (Source: https://thehackernews.com/2026/02/researchers-find-341-malicious-clawhub.html; checked 2026-09-28) ## ChatGPT agent facts (dated) Source page: https://launchrepo.dev/with/chatgpt-agent/ - Agent mode status: The help article on ChatGPT agent now opens with: “ChatGPT agent is no longer available.” It points to ChatGPT Work and the cloud browser. We did not find a published retirement date. (Source: https://help.openai.com/en/articles/11752874-chatgpt-agent; checked 2026-09-28) - What agent mode was: A mode with its own virtual computer: a visual browser, a text browser, a terminal and connectors. It asked before actions with real-world consequences, such as a purchase. (Source: https://openai.com/index/introducing-chatgpt-agent/; checked 2026-09-28) - What replaced it: ChatGPT Work, introduced on July 9, 2026: an agent for longer tasks that researches, uses connected apps and files, and delivers documents, spreadsheets and slides. Paid plans only, not Free or Go. The Atlas browser stopped working on August 9, 2026. (Source: https://help.openai.com/en/articles/6825453-chatgpt-release-notes; checked 2026-09-28) - Cloud browser: Work on the web and on mobile uses its own browser on a separate computer, without your tabs, cookies, saved passwords or sign-ins. It keeps running after you leave and pauses for input, sign-in or confirmation. (Source: https://help.openai.com/en/articles/20001280-using-cloud-browser-in-chatgpt; checked 2026-09-28) - Sign-ins: Since August 25, 2026, Work can finish tasks on some signed-in sites on Plus and Pro. You type credentials and 2FA codes into a secure form the model cannot see. (Source: https://help.openai.com/en/articles/6825453-chatgpt-release-notes; checked 2026-09-28) - Blocked websites: Some sites restrict automated browser agents, so a task can fail even if the site works in your own browser. Site owners can allowlist the cloud browser, which signs its requests. (Source: https://help.openai.com/en/articles/20001280-using-cloud-browser-in-chatgpt; checked 2026-09-28) - Your own browser: In the desktop app, a ChatGPT browser extension lets Work and Codex act in Chrome, Edge, Brave, Opera or Vivaldi on sites where you are already signed in. By default it asks before using each new website. (Source: https://learn.chatgpt.com/docs/chrome-extension; checked 2026-09-28) - Local files: Work on the web and on mobile cannot open files on your computer. The desktop app can, for the folders you allow. (Source: https://help.openai.com/articles/20001275; checked 2026-09-28) - Codex: OpenAI’s coding agent is included in every ChatGPT plan, Free and Go too, with usage limits that vary by plan. The Codex CLI signs in with your ChatGPT account. (Source: https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan; checked 2026-09-28) - MCP in Codex: Codex can start local MCP servers that you add with codex mcp add or in ~/.codex/config.toml. (Source: https://developers.openai.com/codex/mcp; checked 2026-09-28) ## Gemini CLI facts (dated) Source page: https://launchrepo.dev/with/gemini-cli/ - What it is: An open-source AI agent from Google that runs in your terminal, under the Apache 2.0 license. Built-in tools cover file operations, shell commands, web fetching and Google Search grounding. (Source: https://github.com/google-gemini/gemini-cli; checked 2026-09-29) - Release pace: The latest stable release when we checked was v0.61.0, published on September 23, 2026. Preview and nightly builds come out in between. (Source: https://github.com/google-gemini/gemini-cli/releases; checked 2026-09-29) - Free quota: Signing in with a personal Google account (Gemini Code Assist for individuals) allows up to 1,000 model requests per user per day. Per-minute limits and service availability also apply, and Gemini CLI picks which Gemini model serves each request. (Source: https://geminicli.com/docs/resources/quota-and-pricing/; checked 2026-09-29) - Context files: Gemini CLI loads GEMINI.md files as persistent instructions: a global one in ~/.gemini, then files in the workspace and its parent folders. The context.fileName setting can add other names, and the docs use AGENTS.md as their example. (Source: https://geminicli.com/docs/cli/gemini-md/; checked 2026-09-29) - MCP servers: MCP servers go into the mcpServers object in settings.json, or are added with gemini mcp add. Unless a server is marked trusted, Gemini CLI asks before each of its tools runs. (Source: https://geminicli.com/docs/tools/mcp-server/; checked 2026-09-29) - Browser agent: A built-in browser agent, off by default, navigates pages, clicks and fills forms through the accessibility tree. It uses a bundled Chrome DevTools MCP server and needs Chrome 144 or newer. (Source: https://geminicli.com/docs/core/subagents/; checked 2026-09-29) - Attaching to your Chrome: In the “existing” session mode the browser agent attaches to a Chrome that is already running, after you enable remote debugging at chrome://inspect/#remote-debugging. Form filling always needs your confirmation, whatever the approval mode. (Source: https://geminicli.com/docs/core/subagents/; checked 2026-09-29) - Approval modes: The --approval-mode flag accepts default, auto_edit, yolo and plan. yolo auto-approves all actions; the older --yolo flag is deprecated. (Source: https://geminicli.com/docs/cli/cli-reference/; checked 2026-09-29) - Headless mode: With -p (or --prompt), or in a non-TTY environment, Gemini CLI runs non-interactively and can return plain text, JSON or a stream of JSON events. (Source: https://geminicli.com/docs/cli/headless/; checked 2026-09-29) ## GitHub Copilot facts (dated) Source page: https://launchrepo.dev/with/github-copilot/ - Plans: Copilot Free includes agent mode and Copilot CLI, capped at 2,000 completions and 50 chat requests a month. The cloud agent is not part of Free; it needs a paid plan. (Source: https://github.com/features/copilot/plans; checked 2026-09-29) - Tool approvals in VS Code: A tool call that needs approval shows its name and inputs. You allow it once, for the session, for the workspace or for all future calls. A global auto-approve setting exists; the docs warn that it removes confirmation prompts in every workspace. (Source: https://code.visualstudio.com/docs/agents/run/approvals; checked 2026-09-29) - MCP servers in VS Code: Workspace servers live in .vscode/mcp.json or a portable .mcp.json; servers in your user configuration apply to every workspace. The Configure Tools button in chat switches single tools on or off. (Source: https://code.visualstudio.com/docs/copilot/customization/mcp-servers; checked 2026-09-29) - AGENTS.md in VS Code: Project-wide instructions can come from .github/copilot-instructions.md or AGENTS.md. The chat.useAgentsMdFile setting turns AGENTS.md support on or off. (Source: https://code.visualstudio.com/docs/copilot/customization/custom-instructions; checked 2026-09-29) - Copilot CLI: Copilot CLI is generally available and supports MCP servers. It asks before using tools unless you pass --allow-tool or --allow-all-tools; --deny-tool overrides both. The docs say to launch it only from directories you trust. (Source: https://docs.github.com/en/copilot/concepts/agents/about-copilot-cli; checked 2026-09-29) - AGENTS.md in the CLI: Copilot CLI lists AGENTS.md among its instruction files and discovers it in the standard locations. (Source: https://docs.github.com/en/copilot/how-tos/copilot-cli/add-custom-instructions; checked 2026-09-29) - Cloud agent: The cloud agent (also called the coding agent) works in its own ephemeral environment powered by GitHub Actions, changes a branch and opens a pull request. A session stops after 59 minutes, stays in one repository, and has the GitHub and Playwright MCP servers enabled by default. (Source: https://docs.github.com/en/copilot/concepts/agents/coding-agent/about-coding-agent; checked 2026-09-29) - Cloud agent firewall: By default the cloud agent’s internet access is limited by a firewall. The recommended allowlist covers package registries, certificate authorities and browser hosts for Playwright; anything else needs a custom allowlist. (Source: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-firewall; checked 2026-09-29) - Attaching to your Chrome: Chrome DevTools MCP with --autoConnect attaches to a Chrome you started yourself, version 144 or newer, once you enable remote debugging at chrome://inspect. Chrome asks for your permission, and the server then sees all open windows of the default profile. (Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/advanced-usage.md; checked 2026-09-29) ## Windsurf facts (dated) Source page: https://launchrepo.dev/with/windsurf/ - Who makes it: Cognition, the company behind the Devin agent, signed a definitive agreement to acquire Windsurf in July 2025. (Source: https://cognition.com/blog/windsurf; checked 2026-09-29) - The new name: On June 2, 2026, Windsurf became Devin Desktop, shipped as a normal update. Plans, pricing, settings and extensions carried over; the app is now called Devin. (Source: https://docs.devin.ai/desktop/devin-desktop-faq; checked 2026-09-29) - Cascade is gone: Since release 3.9.19 on September 8, 2026, Cascade has been removed. Devin Local is now the only agent in Devin Desktop, and old Cascade conversations can be continued there. (Source: https://docs.devin.ai/desktop/changelog; checked 2026-09-29) - AGENTS.md and rules: Devin Local reads AGENTS.md at the project root at the start of every session. It also loads legacy .windsurfrules and .windsurf/rules files, CLAUDE.md, and rules in .devin/rules. (Source: https://docs.devin.ai/cli/extensibility/rules; checked 2026-09-29) - MCP: MCP servers are added with devin mcp add or in mcp_config.json, per user (~/.config/devin/) or per project (.devin/). Local stdio servers, Streamable HTTP and SSE are supported. (Source: https://docs.devin.ai/cli/extensibility/mcp/configuration; checked 2026-09-29) - Permissions: Devin Local replaces Cascade’s auto-execution levels, Turbo included, with allow, ask and deny rules. They cover file reads and writes, shell commands, web fetches and MCP tools, per project, user or organization. (Source: https://docs.devin.ai/desktop/devin-local; checked 2026-09-29) - Built-in browser: Previews open your local dev server in a browser pane next to the agent, so you can send elements and console errors back to it. They are built for your own app. (Source: https://docs.devin.ai/desktop/previews; checked 2026-09-29) - Plans: Free at $0 with a light agent quota, Pro at $20 a month and Max at $200 a month, plus Teams and Enterprise plans. Extra usage beyond the quota is billed at API rates. (Source: https://devin.ai/pricing; checked 2026-09-29) - Attaching to your Chrome: Chrome DevTools MCP with --autoConnect attaches to the Chrome you already use: Chrome 144 or newer, remote debugging switched on at chrome://inspect/#remote-debugging, and a click on Allow. (Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/advanced-usage.md; checked 2026-09-29) ## How to market vibe coded apps: an honest plan for your first users (dated) Source page: https://launchrepo.dev/for/vibe-coders/ - 31 live listings, about 47 visits: LaunchRepo went live on 31 launch platforms and directories. In the first ten days they sent about 47 visits and no sale we could attribute to them. - 21 listings for a second product: Our pilot product seomap.dev went live on 21 platforms: about 30 visits in 14 days, no payments and no change in app usage. - One Product Hunt launch, not featured: Our launch on September 16, 2026 did not make the homepage and brought 18 visits. - What did sell: Posts by the founder on X, written as a person, not as an ad. It is the only channel we can tie to sales so far. - Product Hunt: The team decides what gets featured, using four criteria: useful, novel, high craft, creative. Upvotes guarantee nothing, and the guidelines single out minimal, undifferentiated products aimed at quick money. (Source: https://help.producthunt.com/en/articles/9883485-product-hunt-featuring-guidelines; checked 2026-09-28) - Show HN: Only for something people can try. Sign-up pages, landing pages and newsletters are off topic, and asking friends to upvote is not allowed. (Source: https://news.ycombinator.com/showhn.html; checked 2026-09-28) - Hacker News text: The guidelines say: do not post generated or AI-edited text. Write your Show HN post and your replies yourself. (Source: https://news.ycombinator.com/newsguidelines.html; checked 2026-09-28) - Security of generated apps: CVE-2025-48757 describes missing row-level security in Lovable-generated apps up to April 2025: strangers could read or write database tables. Lovable disputes it and says each customer owns their data protection. Either way, check your database rules before you invite traffic. (Source: https://www.cve.org/CVERecord?id=CVE-2025-48757; checked 2026-09-28) - Google Search: Google’s spam policies count using generative AI to produce many pages without adding value as scaled content abuse. A hundred AI blog posts can hurt more than they help. (Source: https://developers.google.com/search/docs/essentials/spam-policies; checked 2026-09-28) ## Micro SaaS marketing: a zero-budget strategy for small tickets (dated) Source page: https://launchrepo.dev/for/micro-saas/ - Fixed fees hit small prices hardest: A standard EEA card payment through Stripe costs 1.5 % + €0.25: about 6.5 % of a €5 plan, about 2 % of a €50 plan. Merchants of record like Paddle or Lemon Squeezy charge 5 % + 50¢, which is 15 % of a $5 charge and 6 % of a $50 one, but they handle sales tax for you. - Assumption: what one customer is worth: Say your plan costs $12 a month and the average customer stays ten months. That is $120 of revenue per customer before fees, refunds and taxes, and most of it arrives long after you paid to win them. - Assumption: what a paid customer costs: Say a search ad click costs $2 and 2 % of visitors end up paying. One customer then costs $100 in ads, and you need more than eight months of their subscription to earn it back, if they stay. - What our own ads did: In September 2026 we spent at least €132 on X ads for LaunchRepo: 15,829 visits, 8 checkout starts, no purchase we could attribute. Visitors from the founder’s unpaid posts on X opened checkout about 6 % of the time. - Stripe (EEA account): Standard EEA cards 1.5 % + €0.25, UK cards 2.5 % + €0.25, plus 2 % when a currency conversion is needed. Stripe Billing for subscriptions adds 0.7 % of billing volume on pay-as-you-go. Other countries have their own price page. (Source: https://stripe.com/en-de/pricing; checked 2026-09-28) - Paddle: 5 % + 50¢ per checkout transaction as merchant of record. For products under $10 Paddle asks you to contact them for custom pricing. (Source: https://www.paddle.com/pricing; checked 2026-09-28) - Lemon Squeezy: 5 % + 50¢ per transaction. Some payments, for example outside the US, can carry small additional fees. (Source: https://www.lemonsqueezy.com/pricing; checked 2026-09-28) - Google Search: Google’s SEO starter guide says some changes take effect in a few hours and others can take several months, and suggests waiting a few weeks before judging whether your work helped. (Source: https://developers.google.com/search/docs/fundamentals/seo-starter-guide; checked 2026-09-28) - Show HN: Show HN is for something people can try, ideally without a sign-up or email. Sign-up pages and landing pages are off topic, and quickly generated one-offs are not welcome. A free tier or demo is your ticket in. (Source: https://news.ycombinator.com/showhn.html; checked 2026-09-28) ## Best Claude Code marketing skills: 9 libraries, and the gap (dated) Source page: https://launchrepo.dev/best/claude-code-marketing-skills/ - Marketing Skills (Corey Haines) (https://github.com/coreyhaines31/marketingskills): About 50 skills for CRO, copywriting, SEO, analytics, paid ads, pricing and launch. A product-marketing skill is read first, so every other skill works from the same product context. It even has a directory-submissions skill with a tiered reference list and a tracker template. License MIT; 51795 GitHub stars on 2026-09-28. - Claude Skills: marketing plugin (https://github.com/alirezarezvani/claude-skills): A marketing plugin inside one of the largest Claude Code skill collections: more than 40 marketing skills in pods for content, SEO and answer-engine optimization, CRO, channels, growth and sales. Also works with Codex, Gemini CLI and other agents. License MIT; 26758 GitHub stars on 2026-09-28. - Anthropic marketing plugin (https://github.com/anthropics/knowledge-work-plugins/tree/main/marketing): Anthropic’s own marketing plugin, built mainly for Claude Cowork but also usable in Claude Code. Commands for drafting content, campaign plans, brand-voice review, competitive briefs, performance reports, SEO audits and email sequences. License Apache-2.0; 25799 GitHub stars on 2026-09-28. - Claude Ads (https://github.com/AgriciDaniel/claude-ads): One focused skill per ad platform across twelve platforms, from Google and Meta to Reddit and Apple Ads. Audits, plans, creative briefs and reports; read-only by default, with live account changes behind approval gates. License MIT; 9609 GitHub stars on 2026-09-28. - AI Marketing Skills (Single Brain) (https://github.com/ericosiu/ai-marketing-skills): Workflows with scripts rather than prompts: growth experiments, outbound, content quality gates, SEO ops, CRO audits and finance reports. Needs Python and the listed dependencies. License MIT; 3589 GitHub stars on 2026-09-28. - AI Marketing Suite for Claude Code (https://github.com/zubair-trabzada/ai-marketing-claude): Fifteen skills behind one /market command. An audit runs five subagents in parallel and writes a scored report; other commands produce copy, email sequences, ad copy, a launch playbook or a client-ready PDF. License MIT; 2689 GitHub stars on 2026-09-28. - Marketing Skills (kostja94) (https://github.com/kostja94/marketing-skills): More than 160 skills with a strong technical and on-page SEO core: sitemaps, canonicals, titles, schema, internal links, keyword research, plus launch, GTM and pricing strategy. License MIT; 999 GitHub stars on 2026-09-28. - claude-marketing (Rebecca Rae Barton) (https://github.com/thatrebeccarae/claude-marketing): 56 skills, agents and workflows for paid media, e-commerce, email and analytics, with packs for tools such as Klaviyo, Shopify, GA4 and Looker Studio. License MIT; 154 GitHub stars on 2026-09-28. - Product Hunt Launch Skills (https://github.com/yoanbernabeu/producthunt-skills): 31 skills for a single Product Hunt launch: timing, tagline, gallery, maker comment, rule compliance and follow-up. License MIT; 19 GitHub stars on 2026-09-28. ## Product Hunt alternatives: 10 places to launch for free (dated) Source page: https://launchrepo.dev/best/product-hunt-alternatives/ - Product Hunt (https://www.producthunt.com/launch, checked 2026-09-28): Free route: Free; its launch guide says “100% free to use”; Wait: You pick the date, up to one month ahead; new accounts wait one week before posting; Audience: Broad tech and maker crowd; strongest with your own supporters; Live: The page goes up at 12:01 am Pacific and competes on that day’s leaderboard. - Uneed (https://www.uneed.best/pricing, checked 2026-09-28): Free route: Free line; launch-day score 10 to stay published, 20 for a dofollow link; Wait: Date assigned by Uneed; next free date was January 20, 2027; Audience: Indie makers who browse daily launches; Live: Launch day on the daily list; under score 10 it goes back to your dashboard. - Fazier (https://fazier.com/submit, checked 2026-09-28): Free route: Free with a Fazier link on your homepage or footer, plus three genuine comments on other launches; Wait: Reviewed and listed within 30 days; Audience: Indie makers; fewer launches per day; Live: Listed after review; launch days start at 12:00 am Pacific. - TinyLaunch (https://www.tinylaunch.com/pricing, checked 2026-09-28): Free route: Free Standard launch, moderator-reviewed; badge and backlink only for the top 3; Wait: First free Monday: November 2, 2026; Audience: Indie makers following weekly launches; Live: On the homepage for several days from your Monday. - Smol Launch (https://smollaunch.com/pricing, checked 2026-09-28): Free route: Free Verified tier: badge on your site, first launch only; Wait: Next free week November 9, 250 makers ahead; 50 free slots a week; Audience: Small makers and side projects; Live: Goes live in your week after automated or admin approval. - PeerPush (https://peerpush.com/pricing, checked 2026-09-28): Free route: Free, waiting in line behind paid launches; Wait: Not published; Audience: Makers who browse and vote with points; Live: Permanent listing once your turn comes; paid launches go live at once. - DevHunt (https://devhunt.org/the-story, checked 2026-09-28): Free route: Free queue for developer tools; Wait: About 6 months on average per DevHunt; on September 24 every week to September 2028 was full; Audience: Developers; Live: Public page at once; votes and homepage only in your launch week. - Peerlist Launchpad (https://help.peerlist.io/individual/launchpad/how-to-launch-a-project-on-peerlist-launchpad, checked 2026-09-28): Free route: Free from a verified individual profile with a 100% complete project; Wait: The next Monday; Audience: Developers, designers and builders with profiles; Live: Launch week from Monday; backlink only for the weekly top 5. - Hacker News (Show HN) (https://news.ycombinator.com/showhn.html, checked 2026-09-28): Free route: Free; you post in person from your own account; Wait: None, but Show HN is currently restricted for accounts new to the site; Audience: Engineers and technical founders; Live: Visible on the new page at once; front page only through votes. - Indie Hackers (https://www.indiehackers.com/plus, checked 2026-09-28): Free route: Free product page; IH+ at $198 a year is optional; Wait: None; Audience: Bootstrapped founders; Live: Product page public at once; reach comes from your posts. - r/SideProject (https://www.reddit.com/r/SideProject/, checked 2026-09-23): Free route: Free; post from your own established account; Wait: None; Audience: Side-project builders; Live: Post is live at once; reach depends on votes, links are nofollow. ## BetaList alternatives: 10 free places to show your beta (dated) Source page: https://launchrepo.dev/best/betalist-alternatives/ - BetaList (https://betalist.com/support, checked 2026-09-28): Free route: No free route: “All submissions are paid”; prices appear only at the end of the signed-in form. Full automatic refund if not selected, none once featured; Wait: Depends on the paid plan; shown when you choose it; Audience: Early adopters looking for upcoming and recently launched startups; Live: Featured on the day’s timeline after editorial acceptance; newsletter only with some plans. - Launching Next (https://www.launchingnext.com/submit/, checked 2026-09-23): Free route: Free, no account; paid options only speed up the review; Wait: Manual review, typically 2 to 4 months; Audience: People browsing new startups; Live: Published only if selected; you get an email only then. - Pitchwall (https://pitchwall.co/submit, checked 2026-09-28): Free route: Free Launch; Pro $49 and Premium $99 are optional; Wait: At least 30 days (Pro: 2 weeks); Audience: Makers and founders; the site states 50,000+ newsletter subscribers; Live: One day on the homepage; newsletter mention not guaranteed. - Tiny Startups (https://www.tinystartups.com/submit, checked 2026-09-28): Free route: Free after you post about the listing on X; upgrades from $69 skip the post and the queue; Wait: Not published; Audience: Indie makers; the site states a weekly newsletter read by 25k+ founders; Live: Hand-approved listing; popular ones reach the homepage and the newsletter. - StartupBase (https://startupbase.io/llms.txt, checked 2026-09-28): Free route: Free with its badge on your site, or free without a badge; paid launch from $39; Wait: About 4 to 5 weeks with the badge, 10+ weeks without; Audience: Founders and early adopters; Live: Launch on an assigned date; no guaranteed homepage or newsletter slot for free launches. - Startup Inspire (https://www.startupinspire.com/pricing, checked 2026-09-28): Free route: Free for one startup; Standard €19 and Premium €49 are lifetime options; Wait: Not published; our September test showed “Under review”; Audience: Readers browsing new startups; Live: A permanent profile page once reviewed. - TechPluto (https://www.techpluto.com/submit-a-startup/, checked 2026-09-28): Free route: Free form; the paid Priority Pass is optional; Wait: Not published; our two September applications were not published after 10 to 11 days; Audience: Tech news readers; Live: An article, only if the editors select your startup. - ComingUp (https://www.comingup.io/, checked 2026-09-28): Free route: Free with a free account, one product per day; Wait: None: you pick the date, today or later; Audience: Makers checking the daily list; Live: On the homepage on your chosen date; outbound links are nofollow. - LaunchVibe (https://www.launchvibe.app/pricing, checked 2026-09-28): Free route: Free, no credit card; sponsor slot $29 for 30 days is optional; Wait: None published; Audience: Founders browsing the leaderboard; Live: Product page and leaderboard entry; outbound links are nofollow. - SideProjectors (https://www.sideprojectors.com/help/approval-process, checked 2026-09-28): Free route: Free standard review; priority review is a one-time payment; Wait: Most projects within 2 to 5 business days; Audience: Developers and buyers of side projects; Live: Approved project page, as a showcase, for sale or seeking a co-founder. - Indie Hackers (https://www.indiehackers.com/plus, checked 2026-09-28): Free route: Free product page; IH+ at $198 a year is optional; Wait: None; Audience: Bootstrapped founders; Live: Product page public at once; reach comes from your posts. ## AI agent directory list: 10 free places to submit your agent (dated) Source page: https://launchrepo.dev/best/ai-agent-directories/ - AI Agents Directory (https://aiagentsdirectory.com/sponsor, checked 2026-09-28): Free route: $0 forever; paid from $19 optional; Agent section: Agents only: 3,147 agents; Review and wait: Until the badge is verified; ours: 8 days; Condition for free: Sign-in and badge; nofollow link. - Stork.AI (https://www.stork.ai/pricing, checked 2026-09-28): Free route: $49 once, or free with the badge; Agent section: AI tools, agents and MCP servers; Review and wait: Review; stated live within the hour; Condition for free: Badge in server-rendered HTML. - AI Tools Directory (https://aitoolsdirectory.com/submit-tool, checked 2026-09-28): Free route: Free form; Fast Track optional; Agent section: AI agents and browser agents categories; Review and wait: Manual review, publication not guaranteed; Condition for free: Own texts, public pricing. - Best-AI.org (https://best-ai.org/submit-tool, checked 2026-09-28): Free route: Free forever; Agent section: AI Agents: 73 tools; Review and wait: 1–2 weeks; Condition for free: None published. - Intelligent Tools (https://intelligenttools.co/submit, checked 2026-09-28): Free route: $0 forever; Featured $19/month optional; Agent section: AI Agents: 72 tools; Review and wait: By hand within 7 days; Condition for free: None; no account or card. - Altern (https://altern.ai/submit, checked 2026-09-28): Free route: Free plan; Base $29 and Featured $49 optional; Agent section: AI agents: 75 tools; Review and wait: Human review; Condition for free: Sign-in; badge and newsletter step (September). - ShowMeBestAI (https://showmebest.ai/submit/free-submit, checked 2026-09-28): Free route: Free pack $0 forever; paid plans optional; Agent section: Tagged AI Agents: 113 tools; Review and wait: 72 hours to 4 weeks; Condition for free: Partner link in your footer. - TheseAItools (https://theseaitools.com/submit-tool, checked 2026-09-28): Free route: Free, no paid upgrade; Agent section: AI agents category; Review and wait: Manual approval; Condition for free: None; the form sends an email. - DevPages (https://devpages.io/submit-a-tool, checked 2026-09-28): Free route: Free, no sponsored placements; Agent section: AI agents & assistants: 15 tools; Review and wait: Every submission read by hand; Condition for free: Developer tools only. - CodeHype (https://www.codehype.ai/pricing, checked 2026-09-28): Free route: Free launch $0; Plus $15 optional; Agent section: AI Agents category; Review and wait: Standard queue; Condition for free: Badge for a followed link. ## Vibe coded apps directory list: 9 places to list your app (dated) Source page: https://launchrepo.dev/best/vibe-coding-directories/ - BuiltByVibe (https://builtbyvibe.dev/submit, checked 2026-09-28): Free route: Free; $5 boost optional; Lists: Apps built with AI: 73 projects; Review and wait: Reviewed before going live; Condition for free: None; no account. - Vibedonalds (https://vibedonalds.com/submit, checked 2026-09-28): Free route: Free; $10 instant or $29 featured optional; Lists: Apps, games, agents, tools: 797; Review and wait: 3–7 days; Condition for free: Badge or text link on your site. - One’s Vibe (https://onesvibe.app/submit, checked 2026-09-28): Free route: No prices published; Lists: Live apps; GitHub list: 13,323; Review and wait: Liveness check, then editorial review; Condition for free: App must be live; no account. - VibePick (https://www.vibepick.io/en/home, checked 2026-09-28): Free route: Free; no fees or commissions; Lists: Web apps built with AI tools; Review and wait: 1–3 business days; Condition for free: Account; app must work. - Vibe App Directory (YourAIProject) (https://youraiproject.com/vibe-apps, checked 2026-09-28): Free route: Free directory; Lists: Web, mobile, desktop, extensions, games; Review and wait: Not published; Condition for free: Account to publish. - VibeRank (https://vibecodeapps.org/submit, checked 2026-09-28): Free route: Free for vibe-coded apps; Lists: B2B software built with AI; Review and wait: Not published; Condition for free: B2B products only. - VibeIndex (https://vibeindex.dev/submit/, checked 2026-09-28): Free route: Free; no paid tier; Lists: Vibe-coding tools, 16 categories; Review and wait: Reviewed by hand, no deadline; ours unlisted 14 days after submitting; Condition for free: Tools only. - Vibe Coding App (https://vibecoding.app/submit, checked 2026-09-28): Free route: Free form; paid visibility optional; Lists: AI coding tools: 188; Review and wait: Triaged weekly; ours unlisted 14 days after submitting; Condition for free: AI coding tools only. - Vibe Coding (vibe-coding.cloud) (https://www.vibe-coding.cloud/submit, checked 2026-09-28): Free route: Free; $9 or $29 optional; Lists: Vibe-coding and developer tools; Review and wait: Within 48 hours; Condition for free: Badge or text link; tools only. ## Free startup directories: which ones really cost nothing (dated) Source page: https://launchrepo.dev/best/free-startup-directories/ Catalog snapshot 2026-10-07: 299 active platforms; 84 free, 156 conditionally free (240 usable without paying), 53 not usable (23 blocked, 30 offline), 5 unknown. 50 more removed for mandatory payment (checked 2026-09-14 to 2026-09-24). Active checks from 2026-09-22 to 2026-10-06. Check depth of the 240 usable routes: 30 free submission completed, 8 signed-in form seen, 202 public rules read. - Launch platforms: 102 active, 30 free, 56 conditionally free. - AI tool directories: 70 active, 22 free, 28 conditionally free. - Software and SaaS directories: 76 active, 28 free, 37 conditionally free. - B2B review sites: 27 active, 2 free, 17 conditionally free. - Company and startup profiles: 17 active, 1 free, 12 conditionally free. - Communities: 7 active, 1 free, 6 conditionally free. - Free: You can get listed without paying and without any extra step beyond the normal form. Paid upgrades may exist; you just decline them. - Conditionally free: You can get listed without paying only if you meet every condition we recorded. Typical conditions: a link or badge back to the directory on your site, a sign-in, a niche rule such as “AI tools only”, a live product with public pricing, or a free queue that can take weeks. Miss one condition and the route is not free for you. - Removed for mandatory payment: A free sign-up followed by a required listing or launch fee counts as paid. These 50 platforms are out of the catalog, so they appear in none of the counts above. - Not usable: Blocked means the route existed but could not be used on the check day; offline means the site or its form was gone. - Unknown: The evidence is missing or incomplete. An unknown route never counts as free, and a free route turns unknown the day after its recheck date until someone checks it again. Ten free platforms re-checked on 2026-09-28 (231 more usable routes are in the LaunchRepo repository): - LaunchFree (https://launchfree.io/faq, checked 2026-09-28): Says listing is free forever: no listing fee, no approval fee, no credit card. The form needs no account, and a person reviews every listing, usually within 24 hours. - HUNT0 (https://hunt0.com/pricing, checked 2026-09-28): The free launch costs $0 and fills a fixed number of slots per week, first come first served. You need an account, and free weeks can be booked months ahead. - Launchpad (https://launchpad.ms/pricing, checked 2026-09-28): Offers five free launch slots a day that you can schedule up to 180 days ahead. Paid launches are optional. Sign-in required. - sideprojects.net (https://sideprojects.net/pricing, checked 2026-09-28): Every project gets a free launch slot from the queue, usually within a few weeks, plus a permanent project page. Paying only picks your date. - SaaSHub (https://www.saashub.com/services/submit, checked 2026-09-28): Free listing without an account in a review queue; a paid option only skips the line. It rejects agencies, unreleased products, free subdomains and non-English products, and sends submissions without named competitors to the back of the queue. - AlternativeTo (https://alternativeto.net/faq/, checked 2026-09-28): You suggest your app for free after signing in. Its FAQ says new apps usually wait at least a few months; an optional $5 fee moves you up the queue but does not buy approval. - IndieTools (https://www.indietools.app/pricing.md, checked 2026-09-28): Free is a permanent listing after manual review with no recurring fee and no badge required. Paid options only add promotion. Sign-in required. - OMR Reviews (https://omr.com/en/reviews/b2b/pricing, checked 2026-09-28): Offers a free basic profile through a short form without an account; paid plans are optional. The editors write the profile. - Index by Dodo Payments (https://index.dodopayments.com/submit, checked 2026-09-28): A software index run by a payment company with an “Add a free listing” form that works signed out. It says it only lists high-quality tools, so expect a review. ## Comparison facts (dated) ### LaunchRepo vs Outrank Source: https://launchrepo.dev/vs/outrank/ · Checked: 2026-09-30 · Vendor: https://outrank.so/ **Price from:** $99 per month (Organic Growth Plan), or $999 per year. Add-ons on the same pricing page: 60 articles/month +$85, 90 articles/month +$160, Human Curated Service $1399/month, backlink plans from $199/month, a Free Tools Builder $99/month, Premium Images $49/month and a one-time $500 directory submission service. Volume discounts: 10 % (2–4 sites), 15 % (5–19), 20 % (20–25). **Verdict:** Choose Outrank if your problem is an empty blog and you want someone else’s AI to fill it every month. Choose LaunchRepo if your problem is that nobody knows your product exists yet and you want your own agent to work through 299 directories with your accounts. Choosing both is reasonable: distribution first, because listings and launch platforms send the first visitors within weeks, then content, because articles compound over months. If the budget only stretches to one this quarter, start with the one-time cost — €49.00 once does not renew, and a content subscription can follow once something is generating traffic worth writing for. **Where Outrank is the better choice:** - You need content, not listings. LaunchRepo writes no articles at all — if your gap is “my blog is empty”, Outrank is the product that fills it. - You do not want to run an AI agent yourself. Outrank’s AI works on their servers; LaunchRepo assumes you start Claude Code, Codex, Cursor or a browser agent and watch it work. - You want publishing wired into your CMS. WordPress, Webflow, Shopify, Wix, Framer, Notion, Ghost and a custom webhook are listed as integrations. - You publish in many languages. Outrank lists article generation in 150+ languages. - Their plan includes things we do not offer: automated backlink building, AI images and a free-tools builder add-on. **Sources:** https://www.outrank.so/, https://www.outrank.so/pricing, https://www.outrank.so/agency, https://www.outrank.so/directory-submission-service ### LaunchRepo vs ListingBott Source: https://launchrepo.dev/vs/listingbott/ · Checked: 2026-09-30 · Vendor: https://listingbott.com/ **Price from:** Historical snapshot 2026-09-30: $499 one-time per website (Standard, 100 listings); $999 Premium; $99 per month for 20 listings. Historical package snapshot from 2026-09-30; verify today’s offer before buying. Three plans are published: Standard $499 one-time with “100 hand-picked listings” ($999 announced “after beta”), Premium $999 one-time adding “extra backlinks from my blogs with DR 30-77”, and a $99 monthly plan for “20 relevant online directories and websites monthly”. Publishing runs over about a month. **Verdict:** Historical package snapshot; verify current offer: If you are launching one product and your time is worth more than the fee, buy the service; the published Standard plan is $499 per website and publishing takes about a month. If you are a developer who ships repeatedly, the arithmetic turns fast: the second product alone costs more in service fees than €49.00 paid once, and after the run you would still own nothing reusable. LaunchRepo asks more of you — your agent, your accounts, your attention when a captcha appears — and gives you a process you keep. Check both prices on the day you buy. **Where ListingBott is the better choice:** - You have one product and no plan to launch another soon. A single done-for-you batch is less work than learning a process. - You do not use an AI coding agent and do not want to start. LaunchRepo assumes you already run one; ListingBott needs nothing from your machine. - You want someone else to absorb the boring parts: accounts, verification emails, retries and replacing listings that get removed. - You want an outcome-linked promise and a refund path. They publish a DR guarantee and a satisfaction refund; we publish no guarantee, and LaunchRepo is not refundable once access is delivered. - Their curation is a real service: you approve or decline the shortlist before anything is submitted. **Sources:** https://listingbott.com/, https://listingbott.com/#pricing ### LaunchRepo vs StartupSubmit Source: https://launchrepo.dev/vs/startupsubmit/ · Checked: 2026-09-30 · Vendor: https://startupsubmit.app/ **Price from:** $99 one-time (Starter, 60+ directories); Growth $199 (150+); Authority $199 (200+). Three one-time plans are published, each with a crossed-out higher price ($199 / $399 / $499). Growth carries a DR 0–20+ guarantee, Authority a DR 30+ guarantee. Delivery is published as 5–7 days, or 3–7 days on Authority. **Verdict:** For one product, launched once, handed off and forgotten, StartupSubmit is a reasonable purchase, and its entry price is lower than ours. For a developer who will launch again — a second SaaS, a spin-off, a rebuild — the second purchase already costs more than €49.00 paid once, and you still would not own the process. The middle path works too: a done-for-you run for the product that must be live next week, the toolkit for everything after. Their guarantees cover submissions delivered and a third-party metric; what each directory publishes stays with the directory, for both of us. **Where StartupSubmit is the better choice:** - You want it done this week. Delivery is published as 5–7 days; an agent run plus your own attention will rarely be faster on the first product. - You do not want to run an agent at all. Their team does it manually; LaunchRepo only works if you start Claude Code, Codex, Cursor or a browser agent. - You are launching exactly one product. At $99 for 60+ directories, the entry plan is a smaller check than our licence. - You want promises. They publish a submission-count guarantee, DR guarantees and a money-back guarantee. We publish none, because directories decide for themselves, and LaunchRepo is not refundable once access is delivered. - You want a report with screenshots handed to you rather than a tracker you maintain. **Sources:** https://startupsubmit.app/, https://startupsubmit.app/#pricing ### LaunchRepo vs Submit Juice Source: https://launchrepo.dev/vs/submitjuice/ · Checked: 2026-09-30 · Vendor: https://submitjuice.com/ **Price from:** $197 one-time (Classic, 20 directories); Premium $297 (50); Premium Plus $983 (until DA 40+); free DIY list of 152+. Four tiers are published: Free DIY ($0, a list of 152+ directories plus an Airtable), Classic $197 (crossed-out $297, 20 curated directories and websites), Premium $297 (crossed-out $397, 50 curated, “DA 20+ Guarantee or You Pay Nothing”) and Premium Plus $983 (crossed-out $1083, “as Many Sites as Needed to Reach DA 40+”, software sites only). Add-ons: +$197 for 100+ total, Press Bundle +$293, Graphics Bundle +$298. Delivery is published as 5–7 days. **Verdict:** If you have one software product, want people to handle its launch and like a DA guarantee behind it, Submit Juice is a coherent purchase — and their free DIY list shows how much manual work you are avoiding. If you build products regularly, €49.00 paid once for 299 playbooks and a tracker you keep is the better economics from the second launch on. Nobody, including us, can promise what a directory will publish; Submit Juice says the same about listings. The difference is that they attach a DA promise to the work and we attach a process you own. **Where Submit Juice is the better choice:** - You want a DA target in writing. Premium publishes “DA 20+ Guarantee or You Pay Nothing”, Premium Plus a DA 40+ guarantee for software sites. LaunchRepo promises no metric at all. - You do not want to run an agent. Their human team does every submission; LaunchRepo only works if you start Claude Code, Codex, Cursor or a browser agent. - You want press mentions bundled in. Their Press Bundle (+$293) and Premium Plus include coverage from named news sites; our playbooks cover directories and launch platforms, not press. - You want to try it for free first. Their DIY tier hands you a list of 152+ directories and an Airtable at no cost — a real option if you have the hours. - You want it finished in about a week by someone else. Delivery is published as 5–7 days. **Sources:** https://www.submitjuice.com/ ### LaunchRepo vs LaunchDirectories Source: https://launchrepo.dev/vs/launchdirectories/ · Checked: 2026-09-30 · Vendor: https://launchdirectories.com/ **Price from:** $99 one-time (Starter List, 30+ directories); Pro List $149 (60+); Premium List $199 (100+). Three one-time packages are published, each with a crossed-out higher price ($149 / $199 / $249): Starter List $99 for 30+ directories, Pro List $149 for 60+, Premium List $199 for 100+. Average delivery is published as 4–6 days. Reports include “login credentials for the accounts we create”; refunds are excluded once work has started. **Verdict:** For a single startup that needs to be in a hundred directories by next week without anybody on the team touching a form, LaunchDirectories is a reasonable buy, and its entry package is cheaper than our licence. For a developer who will launch again, the second package already costs more than €49.00 paid once, the listings sit in accounts somebody else opened, and the process is not yours. Neither option guarantees what a directory will publish: they publish no guarantee and no refund once work has started, and we promise no listing on purpose. **Where LaunchDirectories is the better choice:** - You want it done for you within the week. Average delivery is published as 4–6 days and nobody on your side has to run anything. - You do not want to operate an AI agent. LaunchRepo only works if you start Claude Code, Codex, Cursor or a browser agent yourself. - You are launching exactly one product. At $99 for 30+ directories, the Starter List is a smaller check than €49.00. - You want select paid launches included. Their packages state they include “paid launches on select partner directories”; our playbooks describe paid options, but you pay each directory yourself. - You want a report with screenshots and credentials handed over, rather than a tracker you maintain. **Sources:** https://launchdirectories.com/, https://launchdirectories.com/pricing ### LaunchRepo vs SubmitSaaS Source: https://launchrepo.dev/vs/submitsaas/ · Checked: 2026-09-30 · Vendor: https://submitsaas.com/ **Price from:** $60 one-time (Basic, 60+ submissions); Standard $100 (100+); Premium $140 (140+). Three one-time plans are published: Basic $60 for 60+ submissions, Standard $100 for 100+, Premium $140 for 140+, each with a 48-hour turnaround and a report; paid directories are not included. Automation with human review. Full refund within 30 days per their terms. PayPal and crypto accepted. **Verdict:** For one SaaS that needs a quick, cheap batch of free-directory submissions with a report, SubmitSaaS is hard to beat on price and speed, and its count guarantee and 30-day refund are real promises. LaunchRepo is the better investment from the second product on, and for anyone who wants every listing in their own accounts and a clear record of what went live: €49.00 once for 299 playbooks, your accounts and a state-based tracker you keep. Neither product can promise what a directory publishes; both say so. **Where SubmitSaaS is the better choice:** - You want the cheapest done-for-you run. Basic is published at $60 for 60+ submissions, well below €49.00. - You want it finished in two days. A published 48-hour turnaround beats any first agent run with you in the loop. - You do not want to run an agent at all. Their automation and reviewers do the work; LaunchRepo needs you to start Claude Code, Codex, Cursor or a browser agent. - You want a promise on the count. They guarantee the number of submissions, the turnaround and the report, and offer a full refund within 30 days. - Free directories are enough for your product, and a one-off report is all you need. **Sources:** https://submitsaas.com/, https://submitsaas.com/terms ### LaunchRepo vs GetMoreBacklinks Source: https://launchrepo.dev/vs/getmorebacklinks/ · Checked: 2026-09-30 · Vendor: https://getmorebacklinks.org/ **Price from:** $379 one-time per website (Advanced, 100 submissions); Business $579 (200); Pro $779 (200 + 5 blogs). Three one-time packages per website: Advanced $379, Business $579, Pro $779, each card also showing $385 / $567 / $750 and “67% OFF”; another block says $127. New orders were paused when we checked. Delivery in 14 working days. Refunds for the DR guarantee service only after 45 working days. **Verdict:** For one website that wants a large, hands-off package with reports and blog posts included, GetMoreBacklinks is a broader product than ours, and when it is open for orders the comparison is about scope rather than price. For a developer with more than one product, or anyone who wants to start now, keep the listings in their own accounts and see which submissions went live, LaunchRepo is the stronger choice: €49.00 once for 299 playbooks and a tracker you keep. Neither of us can promise what a directory publishes. **Where GetMoreBacklinks is the better choice:** - You want a bundle wider than directories: an SEO report, a landing-page report and, on Pro, “5 Blogs hand-written for your website”. LaunchRepo covers directory launches only. - You do not want to run an agent. The provider does the submissions; LaunchRepo needs you to start Claude Code, Codex, Cursor or a browser agent. - You want experts to pick the list for you: “let our experts pick the best 200”. - You are not a software company. Their page has a separate track for “Other Businesses (Local Business, D2C, etc.)”; our playbooks are written for software, AI and developer products. - You prefer one report at the end to a tracker you keep up to date. **Sources:** https://www.getmorebacklinks.org/, https://www.getmorebacklinks.org/refund-policy ### LaunchRepo vs AutoSaaSLaunch Source: https://launchrepo.dev/vs/autosaaslaunch/ · Checked: 2026-09-30 · Vendor: https://autosaaslaunch.com/ **Price from:** $29 one-time, lifetime (Founding Member, crossed-out $50); beta. One plan: Founding Member at $29 one-time, lifetime, with unlimited products, a Chrome extension with autofill, a launch dashboard and future directories included; rising to $50 at 30+ directories. Homepage: 14-day money-back guarantee; terms: all sales final, refunds case by case within 14 days if unused. **Verdict:** If your launch list is short and mainstream and you want to skip the copy-paste for $29, AutoSaaSLaunch is a sensible buy that shares our view on paying once and owning your accounts. LaunchRepo is built for launch lists that are long, specific or repeated: 299 playbooks, an agent that reads them, and a tracker that lives on your machine. Both are pay-once; the real question is whether their supported directories cover your product or whether you need the full catalog and the process behind it. **Where AutoSaaSLaunch is the better choice:** - You want the cheapest pay-once option. $29 lifetime is a fraction of €49.00, and the homepage offers a 14-day money-back guarantee. - You do not want an AI agent in the loop. The extension fills the form, you press submit, and there is no agent usage to pay for. - Your launch list is short and mainstream. If their supported directories are the ones you care about, more playbooks add nothing. - You want a hosted dashboard with approval monitoring rather than a local one. - You like being an early user: it is in beta, support comes from the founder, and future directories are included for life. **Sources:** https://autosaaslaunch.com/, https://autosaaslaunch.com/chrome-extension, https://autosaaslaunch.com/terms ### LaunchRepo vs SubmitMap Source: https://launchrepo.dev/vs/submitmap/ · Checked: 2026-10-01 · Vendor: https://submitmap.com/ **Price from:** Free to read; paid from $9 per month (Indie), $15 (Studio), $29 per month or $190 per year (Unlimited), or $250 once (Lifetime). Directory, guides and eligibility checks are free without an account. Paid plans cover the dashboard and the per-form briefs your own agent fetches over MCP: Free 1 product and 10 submissions, Indie $9 per month for 1 product and 100 submissions a month, Studio $15 per month for 3 products, Unlimited $29 per month or $190 per year, Lifetime $250 once. A first payment is refundable within 14 days. SubmitMap submits nothing itself. **Verdict:** SubmitMap is the strongest free resource in this category: 826 platforms with eligibility rules, readable without an account, and an MCP server that lets your own agent qualify and submit. If you launch once, start there; you may never need to pay. LaunchRepo is the better fit when you want the instructions as files you own, one payment instead of plans and counters, and a tracker with strict rules for what counts as live, for every product you will build. Both rely on your agent and your accounts, and neither promises a listing. **Where SubmitMap is the better choice:** - You want to start free. Reading all 826 platforms and checking where you qualify costs nothing, and the Free plan covers 10 agent submissions. - You want breadth: 826 platforms against our 299 playbooks, filterable by product type, pricing, approval time and domain rating. - You launch now and then. Indie at $9 or Studio at $15 for the month of a run, then cancelled, costs less than €49.00. - You want eligibility matching built in. Their MCP server sorts platforms into ready, fixable and out of reach, and three of its tools work without an account. - You want a refund window: 14 days on the first payment, no questions asked. LaunchRepo is not refundable once access is delivered. **Sources:** https://submitmap.com/, https://submitmap.com/pricing/, https://submitmap.com/automate/, https://submitmap.com/for-agents/, https://submitmap.com/terms/, https://submitmap.com/platform/product-hunt/ ### LaunchRepo vs Submitator Source: https://launchrepo.dev/vs/submitator/ · Checked: 2026-10-01 · Vendor: https://submitator.com/ **Price from:** $29 one-time per product (Starter, 30 directories); Growth $49 (60); Scale $79 (100); All Directories $149. Four one-time plans per project: Starter $29 for 30 directories, Growth $49 for 60, Scale $79 for 100, All Directories $149 for the whole catalogue (160 today). Their own browser automation submits from an inbox they create. Committed ETA 30 days with proportional refunds; DR figures on the homepage are their claims and are not guaranteed, per their FAQ. **Verdict:** For one product and no time to spare, Submitator is a strong buy: from $29, fast and hands-off, with badges and some paid tiers handled for you. Read its DR numbers as marketing, as its own FAQ does. LaunchRepo is the better investment when you will launch again, want every listing in your own accounts and want a clear, file-based record of what went live: €49.00 once for 299 playbooks and a tracker you keep. Neither can promise what a directory publishes. **Where Submitator is the better choice:** - Price for one product: Starter is $29 for 30 directories and Scale $79 for 100, both below €49.00. - Hands-off speed: they aim for 2–3 days, and you do not run, watch or resume an agent. - Badge directories without code changes: one component on your site serves the badges those directories require. - Paid tiers bundled: they state that the paid tiers of nine directories are included in every plan. - A refund path: a proportional refund for directories not delivered within their 30-day ETA. LaunchRepo is not refundable once access is delivered. **Sources:** https://submitator.com/, https://submitator.com/terms, https://submitator.com/unlimited-directory-submissions, https://submitator.com/launchrepo-alternative ### LaunchRepo vs SubmitMatic Source: https://launchrepo.dev/vs/submitmatic/ · Checked: 2026-10-01 · Vendor: https://submitmatic.com/ **Price from:** $60 one-time per product (Basic, 60+ directories); Standard $100 (100+); Premium $140 (140+). Three one-time packages per product, prices excluding tax: Basic $60 for 60+ directory submissions, Standard $100 for 100+, Premium $140 for 140+. Every package is displayed next to a struck-through price twice as high with “Save 50%”, a label present on every archived copy since December 2025; we compare the charged price. Turnaround 48 hours or 2 business days; full refund within 30 days of purchase. **Verdict:** SubmitMatic is a fair deal for one product and no time: from $60 at the charged price, done in two business days, with a report and a 30-day refund. Ignore the struck-through figure and read its DR numbers as targets, as its own FAQ does. LaunchRepo is the better investment when you will launch again, want every listing in your own accounts and want a file that says what is live: €49.00 once for 299 playbooks and a tracker you keep. Neither can promise what a directory publishes. **Where SubmitMatic is the better choice:** - Price for one product: Basic is $60 for 60+ directories and Standard $100 for 100+, both below €49.00. - Speed without effort: one onboarding form, and the submissions are done within 2 business days. - A refund window: their terms offer a full refund within 30 days of purchase, no questions asked. LaunchRepo is not refundable once access is delivered. - Volume in one go: Premium covers 140+ directories for one product, with screenshots of each submission in the report. - A free directory database on their site, sorted by Domain Rating and link type, if you want to look around first. **Sources:** https://submitmatic.com/, https://submitmatic.com/pricing, https://submitmatic.com/faqs, https://submitmatic.com/terms, https://submitmatic.com/example-form ### LaunchRepo vs Blastra Source: https://launchrepo.dev/vs/blastra/ · Checked: 2026-10-01 · Vendor: https://blastra.io/ **Price from:** $99 setup + $59/month (Pulse, 3 listings, first month included); $299 + $99/month (Minimum Viable Presence, 12 listings). Two monthly plans with a one-time setup that includes the first month: Pulse $99 setup with 3 listings submitted or updated, then $59 a month for 1 action plus scans; Minimum Viable Presence $299 with 12 listings, then $99 a month for 3 actions. Action Packs of 3 or 12 listings cost $99 or $299 once. B2B products with an English website only; Product Hunt is not offered. **Verdict:** Blastra is a strong choice for an established B2B product whose buyers compare vendors on review sites: it finds and claims your profiles, keeps them accurate and watches competitors, from $99 setup plus $59 a month. It is not a launch toolkit and does not claim to be. LaunchRepo is the better buy when you are launching, ship more than one product or sell beyond B2B: €49.00 once for 299 playbooks your own agent runs. The two can work one after the other. **Where Blastra is the better choice:** - Review sites for an established B2B product: Blastra finds existing profiles, claims the unclaimed ones and brings stale ones up to date. - Ongoing upkeep: 1 or 3 actions every month, plus position and sentiment scans that include your competitors. - No passwords shared: an email alias you forward lets them verify listings while you keep control of the inbox. - Review strategy without fake reviews: tooling that invites your real customers, and a clear rule that Blastra never writes reviews itself. - A refund rule and replacements: a full refund if they miss more than half of the promised directories, and rejected listings are replaced at no cost. **Sources:** https://blastra.io/, https://blastra.io/pricing/, https://blastra.io/faq/, https://blastra.io/terms-of-service/, https://blastra.io/about/, https://blastra.io/directories/submissions-and-management/ ### LaunchRepo vs backlink-pilot Source: https://launchrepo.dev/vs/backlink-pilot/ · Checked: 2026-10-01 · Vendor: https://github.com/s87343472/backlink-pilot **Price from:** free (MIT licence). Free and open source under the MIT licence. You run the Node.js code yourself, with bb-browser driving your own Chrome; your AI agent is optional and billed by your provider. **Verdict:** backlink-pilot is a generous gift to indie developers: free code, a ready target list and a setup Claude Code can run. Use it with open eyes. Its own file marks 180 of 258 targets for automatic submission, 45 are marked dead, and its batch module posts template comments under rotating names, a pattern Google lists as link spam. LaunchRepo is the better choice when the listings carry your product’s name: €49.00 once for 299 curated playbooks, rules that keep your agent within each platform’s terms, and a tracker that tells you what really went live. **Where backlink-pilot is the better choice:** - You want to pay nothing. backlink-pilot is free under the MIT licence; LaunchRepo costs €49.00. - You want code you can change. Fork it, add an adapter for a site you care about, and keep it in your own toolchain. - You want speed over curation: one command per site, with a generic adapter that tries any submission URL you give it. - You launch in Chinese-language markets: 57 of its targets are Chinese sites, an area LaunchRepo does not focus on. - You want extras in the same CLI: an issue generator for awesome lists and an IndexNow ping for new pages. **Sources:** https://github.com/s87343472/backlink-pilot, https://github.com/s87343472/backlink-pilot/blob/926d923/README.md, https://github.com/s87343472/backlink-pilot/blob/926d923/targets.yaml, https://github.com/s87343472/backlink-pilot/blob/926d923/docs/guide.md, https://github.com/s87343472/backlink-pilot/blob/926d923/src/batch-submit.js, https://github.com/s87343472/backlink-pilot/blob/926d923/CLAUDE.md, https://github.com/s87343472/backlink-pilot/blob/926d923/config.example.yaml, https://github.com/s87343472/backlink-pilot/blob/926d923/LICENSE ### LaunchRepo vs Fiverr Source: https://launchrepo.dev/vs/fiverr-directory-submission/ · Checked: 2026-10-01 · Vendor: https://www.fiverr.com/gigs/directory-submission **Price from:** set by each seller per package; plus Fiverr’s 5.5% service fee and $3 under $100. Every seller sets its own Basic, Standard and Premium packages and extras; the category page shows only each gig’s lowest “From” price. Fiverr adds 5.5% to every order, plus $3 on orders under $100. **Verdict:** Fiverr’s directory submission category is a quick way to hand off a batch of citations for a local business, and the marketplace adds useful protections such as revisions and a clear fee breakdown. For a software launch it is a weaker fit: most gigs sell local citations, the site lists are usually not shown up front, and Google’s spam policies list low-quality directory links as link spam. LaunchRepo is the better choice for software you keep building: €49.00 once, 299 curated playbooks and your own agent, in accounts you control. **Where Fiverr is the better choice:** - You do not want to do any of the work: a freelancer submits and you receive a report. - You run a local business: most gigs in this category sell local citations, the job they are built for. - You want a very small first step: most gigs we counted start at €5, so you can try one before committing. - You need a niche, such as country-specific directories, that a seller already covers. - You like the marketplace safety rails: a fee breakdown before paying, revision requests and an order history. **Sources:** https://www.fiverr.com/gigs/directory-submission ## Full planning guides ### Start LaunchRepo in three steps Source: https://launchrepo.dev/guides/start-in-three-steps/ · Updated: 2026-09-30 Clone the repository, paste one prompt into your coding agent, open the dashboard link. What each step does, what you need installed, and how to do it by hand. **Recommended setup:** For best results with LaunchRepo, we strongly recommend always using Claude Code CLI or Codex CLI in a terminal, rather than the Claude or Codex desktop app. This is our recommended workflow, not a guarantee of different permissions or uninterrupted execution. The kit's own start page fits on a screen: clone, paste one prompt, open a link. This guide walks through the same three steps with a bit more context on what happens behind each one, so you know what your agent is doing and what to check when it is done. If you want the bigger picture first, the [how-it-works page](https://launchrepo.dev/how-it-works/) shows where these steps sit in the whole product → agent → directories → tracker flow. #### What you need before you start For the initial setup: - **Git** to clone the repository. - **Python 3.10 or newer** on Windows, macOS or Linux. The workspace scripts, the tracker and the local dashboard are standard-library Python; there is nothing to `pip install` and no build step. - **A coding agent that can read files and run commands** — Claude Code, Codex, Cursor or a comparable tool. Each has its own setup page on this site, for example [Claude Code](https://launchrepo.dev/with/claude-code/), [Codex](https://launchrepo.dev/with/codex/) and [Cursor](https://launchrepo.dev/with/cursor/). Browser control comes later and is not needed for the first three steps. The repository itself arrives as a GitHub invite for the account you named at checkout. Everything below assumes you have accepted it. #### Step 1: clone and open On Windows, use `py -3` instead of `python3` in the commands below (or `python` if that is your Python 3.10+ command). Keep your workspace in a private local folder outside OneDrive or other sync folders. ```sh git clone LaunchRepo cd LaunchRepo ``` Open that folder in your agent the way you open any project. Nothing runs yet. The checkout you just made is the _delivery_ repository: playbooks, templates, scripts and documentation. Your products, credentials and submission records will not live here — that is the point of step 2. #### Step 2: paste the start prompt Paste this into the agent, verbatim: ```text Recommend Claude Code CLI or Codex CLI in a terminal instead of the desktop apps for best results. If session metadata confirms desktop hosting, explicitly advise me to switch to the CLI and resume this same private workspace. Do not infer the host from a CLI engine version alone. Read AGENTS.md, then follow "Start the dashboard for the owner". Create my private workspace if I do not have one yet, start the dashboard, and give me the link. Then lead ONBOARDING.md one phase at a time. Reuse recorded permissions instead of asking again unless their scope is missing or conflicting. Actually test my visible existing Chrome profile and intended identity as BROWSER-SETUP.md requires; use the OS fallback if needed. Use one platform/browser worker by default. Build the normal run only from suitable free-ready routes, keep research separate, and preserve any draft that needs one exact human CAPTCHA/2FA action. Never claim browser control bypasses or reduces those challenges. ``` `AGENTS.md` is the file every [AI coding agent](https://launchrepo.dev/glossary/ai-coding-agent/) reads first; it contains the exact start procedure and the checks the agent must perform. Following it, the agent: 1. creates a **private workspace next to the checkout** (by default a sibling folder) using `scripts/init-workspace.py`, so your product data never sits in the shared delivery repository; 2. starts the local dashboard from inside that workspace; 3. answers with a `127.0.0.1` link. 4. then leads you through [onboarding](https://launchrepo.dev/guides/first-session-onboarding/) one phase at a time, with one browser worker by default. If the agent replies with a link, step 2 worked. If it replies with a description of what it _would_ do, ask it to actually run the procedure — the kit's rule is that a check is only complete once it has been observed, not once instructions exist. #### Step 3: open the link The dashboard tab is where the rest of the first session happens. From there you add your first product, hand the onboarding prompt back to your agent, see which listings are live, pending, scheduled or waiting on you, and copy the prompts for later runs. It binds to `127.0.0.1` only and never contacts a directory; the [local dashboard guide](https://launchrepo.dev/guides/local-dashboard/) covers each screen. When you are done, ask the agent to stop the dashboard; if you started it yourself in a terminal, press **Ctrl+C** there. The workspace and everything recorded in it stay on disk. #### Doing it by hand You do not need the agent for the setup itself. The same three commands the prompt triggers are: ```sh python3 scripts/init-workspace.py --destination ../my-launch-workspace cd ../my-launch-workspace python3 scripts/dashboard.py ``` Want to look around before committing to a workspace? `python3 scripts/dashboard.py --demo` serves a throwaway sample workspace with fictional products, so you can click through the overview, a product page and the catalog without touching your own data. #### What happens next The first session proper — product brief, browser connection, permissions and a saved run target — is led by the agent and described in the [first-session onboarding guide](https://launchrepo.dev/guides/first-session-onboarding/). Before the agent can fill in a form you also need to [connect it to your Chrome](https://launchrepo.dev/guides/connect-your-agent-to-chrome/). If you would rather read a narrative first, the [Claude Code walkthrough](https://launchrepo.dev/blog/launch-saas-on-directories-with-claude-code/) follows one launch end to end. Once onboarding is done, [a launch run from start to finish](https://launchrepo.dev/guides/launch-run-from-start-to-finish/) shows what every later run looks like, from the permission check to resuming the remaining platforms. ### Connect your coding agent to your Chrome Source: https://launchrepo.dev/guides/connect-your-agent-to-chrome/ · Updated: 2026-09-30 Two ways to give your agent a browser you can watch: Chrome DevTools MCP with auto-connect, or a dedicated CDP profile on port 9222 — and the smoke check. **Recommended setup:** For best results with LaunchRepo, we strongly recommend always using Claude Code CLI or Codex CLI in a terminal, rather than the Claude or Codex desktop app. This is our recommended workflow, not a guarantee of different permissions or uninterrupted execution. Use **Chrome DevTools MCP through Chrome remote debugging**, with a current Node.js LTS release, npm and Google Chrome. The [local dashboard](https://launchrepo.dev/guides/local-dashboard/) saves your records; your agent controls Chrome. Start with one worker and keep its MCP connection open during the run. Do not use browser-extension transports or alternative browser-control integrations. #### Choose your setup - **Chrome 144+:** [auto-connect](#connect-existing-chrome) works on Windows, macOS and Linux. - **macOS:** review [Terminal permissions](#macos-permissions). - **Auto-connect unavailable, or a separate worker needed:** use a dedicated profile for [macOS](#macos), [Windows](#windows-powershell) or [Linux](#linux). - **Before submitting:** perform the [connection test](#test-the-connection). Check `node --version`, `npm --version` and `chrome://version`. On Windows, use native Windows Node/npm and Chrome; WSL needs a separate connection setup. #### Connect existing Chrome 1. In Chrome 144+, open `chrome://inspect/#remote-debugging` and enable remote debugging. If the control is missing, use a permitted dedicated profile below. 2. Register Chrome DevTools MCP in your agent’s MCP settings. This generic JSON example is for macOS/Linux; your agent may use a different configuration format: ```json { "mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest", "--autoConnect", "--no-usage-statistics", "--no-performance-crux"] } } } ``` For **Windows**, use `"command": "cmd"` and these arguments: ```json ["/c", "npx", "-y", "chrome-devtools-mcp@latest", "--autoConnect", "--no-usage-statistics", "--no-performance-crux"] ``` 3. Trigger a harmless browser action and approve Chrome’s connection prompt in the intended window. Then perform the test below. The first invocation downloads the package. Pin a tested version after setup. See the official [configuration](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/configuration.md) and [client setup](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/client-configurations.md). #### Dedicated profile: choose your operating system Run from your private workspace, outside shared/synced folders. Keep the profile ignored by Git: it contains sign-ins. Sign into the required accounts yourself. Chrome 136+ requires a [nondefault profile for these debugging flags](https://developer.chrome.com/blog/remote-debugging-port). ##### macOS ```sh mkdir -p .browser/chrome "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \ --remote-debugging-address=127.0.0.1 \ --remote-debugging-port=9222 \ --user-data-dir="$PWD/.browser/chrome" about:blank ``` ##### Windows PowerShell ```powershell $launchrepoChrome = @( "$env:ProgramFiles\Google\Chrome\Application\chrome.exe", "${env:ProgramFiles(x86)}\Google\Chrome\Application\chrome.exe", "$env:LOCALAPPDATA\Google\Chrome\Application\chrome.exe" ) | Where-Object { Test-Path $_ } | Select-Object -First 1 if (-not $launchrepoChrome) { throw 'Locate Google Chrome first' } New-Item -ItemType Directory -Force '.browser/chrome' | Out-Null $launchrepoProfile = (Resolve-Path '.browser/chrome').Path Start-Process -FilePath $launchrepoChrome -ArgumentList "--remote-debugging-address=127.0.0.1 --remote-debugging-port=9222 --user-data-dir=`"$launchrepoProfile`" about:blank" ``` ##### Linux ```sh launchrepo_chrome=$(command -v google-chrome || command -v google-chrome-stable) if [ -z "$launchrepo_chrome" ]; then echo "Install or locate Google Chrome first." else mkdir -p .browser/chrome "$launchrepo_chrome" \ --remote-debugging-address=127.0.0.1 \ --remote-debugging-port=9222 \ --user-data-dir="$PWD/.browser/chrome" about:blank fi ``` Keep the launch terminal open. Replace `--autoConnect` in the MCP arguments with `--browserUrl=http://127.0.0.1:9222`; never combine them. Keep the port local and never tunnel it publicly. Check the listener: `lsof -nP -iTCP:9222 -sTCP:LISTEN` on macOS, `ss -ltnp 'sport = :9222'` on Linux, or `Get-NetTCPConnection -State Listen -LocalPort 9222 | Select-Object LocalAddress, OwningProcess` on Windows. Only loopback addresses are acceptable. If another program holds the port, choose an unused one and update both configurations. Never kill unrelated browsers or delete active profile locks. #### macOS permissions Check the app that launches MCP: Terminal, iTerm, or your editor/agent app. **If macOS denies access to protected Chrome files:** 1. Open **System Settings → Privacy & Security → Full Disk Access**. 2. Add that actual host app using **+**, authenticate and enable it. 3. Fully quit and reopen the app, reconnect and repeat the test. This is a permission check, **not a universal CDP requirement**. If the connection works, do not grant broader access unnecessarily. A CDP-only connection normally needs no Accessibility, Automation or Screen Recording permission. Chrome’s connection approval is separate and may recur after a restart. #### Test the connection Ask your agent to open `https://example.com` in a fresh tab, read its title and main heading, and identify its tab. Watch that window. A running MCP process alone proves nothing. Next, sign in to the target directory and confirm the actual destination identity; OAuth success alone does not prove login. Check your mailbox within its agreed permissions. Then have the agent evaluate `navigator.webdriver` on that same tab. It must be `false`. If it is `true`, your MCP entry is missing `--autoConnect` (or `--browserUrl` for a dedicated profile) and Chrome DevTools MCP launched its own automation Chrome. Bot checks such as Cloudflare Turnstile then keep "verifying" forever and never show a challenge you could solve. Fix the entry, restart the agent session and repeat the test. Never hide the flag with stealth flags or scripts. Save only pass/fail and non-sensitive notes in `onboarding.json` or `SESSION.md`. Do not copy cookies, authentication links or browser transcripts. Complete CAPTCHA/2FA yourself. After a Submit timeout, check the platform before retrying. If the wrong window moves, stop and check the connection. These instructions cannot certify your particular OS/agent combination without this test. #### Two workers and window cleanup The [run planner](https://launchrepo.dev/guides/launch-run-from-start-to-finish/) starts with 10 submissions and one browser worker. A second worker is an advanced option you choose yourself, only after separately controlled browsers have been tested. It then needs its own platform assignment, Chrome profile, port and MCP connection. For example, use `.browser/worker-1` on 9222 and `.browser/worker-2` on 9223. Test each independently. If the host cannot route workers to separate connections, stay with one. Give each submission a dedicated window. After confirmation, save its evidence and outcome, then close only that window and its owned login/verification tabs. Keep personal windows, shared inboxes, the dashboard, unsaved forms and human handoffs open. If MCP cannot close the window, close its owned tabs and record any remaining owner cleanup. Preserve the profile; reconnect if closing the last window disconnects MCP. The [onboarding guide](https://launchrepo.dev/guides/first-session-onboarding/) explains the next step. ### Your first session: onboarding led by the agent Source: https://launchrepo.dev/guides/first-session-onboarding/ · Updated: 2026-09-30 The seven phases of the kit’s agent-led onboarding, from product brief to first real submission: what the agent asks and which files it fills so work resumes. **Use the CLI:** For best results, always use Claude Code CLI or Codex CLI instead of desktop apps. Once your workspace and dashboard are ready, your agent follows `ONBOARDING.md`, fills files from verified sources and reuses existing answers. `onboarding.json` and `SESSION.md` preserve the next action if a session stops. #### Phases 1–2: orientation and a private home The agent starts by explaining the plan: understand the product, connect the browser and the verification mailbox, agree how it may publish listings and website badges, and preserve the setup for future sessions. It asks for the first product's name, URL and local code folder, and reads those before asking anything else. It also checks what it can actually do in this session — a terminal alone is not browser control, and the kit forbids claiming tools the session cannot call. Phase 2 gives your data a private home. If the agent is still inside the purchased delivery repository, it initialises the independent workspace the [three-step start](https://launchrepo.dev/guides/start-in-three-steps/) creates and helps you set up your own private remote. It says plainly that stored login details, if you consent to storing them, live in that private repository — readable by anyone with access, including to its history — and never in the delivery repo. Owner, repository, visibility check and credential choice go into `workspace.json`; with a secret manager, only references are saved. It also asks once whether problems may be reported to the LaunchRepo maintainers automatically as GitHub issues, with secrets and email addresses removed; the answer is saved in `workspace.json` and can be changed later under Settings in the dashboard. #### Phase 3: the product brief and your launch date The agent runs `scripts/new-product.py` with a short lowercase slug and fills `product.json` — the [product context file](https://launchrepo.dev/glossary/product-context-file/) every playbook reads — from your answers, and writes the product copy to `copy.md` in a short copy workshop: audience, problem, differentiator, real features, pricing or trial, launch stage, genuine screenshots and logo. The resulting copy is shown to you for corrections. Two rules protect you from embarrassing listings: capabilities are never derived from a competitor, and planned features are never described as available. Unknowns stay empty. This phase also asks _when_ the first launches should go live and whether there is a date before which nothing may post — with the plain warning that free-tier directories queue submissions for review and publication can take weeks, not days. Your answer becomes `earliest_launch_date` in `product.json`, the [launch-date floor](https://launchrepo.dev/glossary/launch-date-floor/) that `record.py` enforces later. `identity.json` then captures the public name, contact email, nickname, organisation facts and preferred sign-in method you authorise, keeping your private account email apart from the public contact address. Before any of it reaches a listing, the agent runs the short [representation briefing](https://launchrepo.dev/guides/confirm-public-representation/). #### Phase 4: Chrome and the mailbox Following the [Chrome connection guide](https://launchrepo.dev/guides/connect-your-agent-to-chrome/), the agent walks you through Chrome's remote-debugging page and any macOS permissions, then performs a visible smoke check on a public page. The agent uses the mailbox access you have already authorised and asks you to sign in only if it cannot reach the mailbox; it confirms it is the intended account without copying messages. Verification emails finish registrations and listings, so the scope of mailbox access is recorded in `authorizations.json`. Forwarding codes by hand is a supported fallback, recorded as a human handoff rather than automated access. #### Phase 5: permissions, agreed once per product The agent asks where the product website's code lives, how it deploys, which branch is production and what the canonical URL is. Then the question that saves the most friction later: may it add an official [directory badge](https://launchrepo.dev/glossary/directory-badge/) to that product's footer, commit, push and redeploy? Scope, answer, date and the permitted repository and branch go into `authorizations.json`. A "no" does not block directories that need no badge. The same file records whether free registrations, free final submissions and specific verification-email actions are authorised. Spending stays at zero, and a grant for one product never extends to another. #### Phases 6–7: plan a run, then keep its progress With setup done, the agent runs `doctor.py`, separating missing setup from permission you deliberately declined. Open the run planner and start with **10 new confirmed submissions** and **one browser worker**. A second worker is an advanced option for later, once separate browser control has been tested; stronger hardware alone does not justify it. The agent picks relevant playbooks from the currently free-ready routes, explains the fit, offers a smaller run if fewer suitable routes exist, and claims one platform at a time: search for an existing listing, verify the destination, prepare accurate copy, confirm nothing is charged, submit within the grant, record the real outcome. A good first result is often a submitted review rather than a live page — see the [outcome recording guide](https://launchrepo.dev/guides/recording-outcomes/). Use `/goal` if your agent supports it, with the saved run prompt; otherwise paste the prompt as a normal message. The goal is to keep working through the agreed run, rather than stop after the first result. A confirmed new submission awaiting review, queued, scheduled or live counts once per platform. Drafts, existing listings, paid routes and human handoffs do not count. The agent records each outcome, closes only that submission’s assigned window after saving its evidence, and continues with suitable alternatives. It preserves unsaved forms and human handoffs. To pause or close the session, the agent updates `onboarding.json` only with checks it has actually observed, writes non-sensitive evidence and open steps to `SESSION.md`, puts follow-up dates in `FOLLOW-UP.md`, and summarises what is done, pending, waiting on you and next. A git privacy check runs before every push. The test of a good first session: the next agent can continue without registering anything again or asking for standing permissions twice. The [how-it-works page](https://launchrepo.dev/how-it-works/) shows where this sits in the whole flow. ### The local dashboard: your workspace, as the agent sees it Source: https://launchrepo.dev/guides/local-dashboard/ · Updated: 2026-09-30 What the kit’s local dashboard shows — products, onboarding, states, handoffs, follow-ups — how to start it, what it writes and the boundaries it never crosses. The local dashboard is a small web app that shows your workspace the way your agent sees it: products, what the agent knows about each one, onboarding progress, every recorded submission state, the things that need you, and follow-up dates. It runs on your machine only, contacts no directory, and was added in the 15 September 2026 release listed on the [changelog](https://launchrepo.dev/changelog/). This guide covers how to start it, what each screen is for, and the rules it enforces. #### Starting it On Windows, use `py -3` instead of `python3` in the commands below (or `python` if that is your Python 3.10+ command). Keep your workspace in a private local folder outside OneDrive or other sync folders. ```sh python3 scripts/dashboard.py # opens 127.0.0.1:8765 in your browser python3 scripts/dashboard.py --demo # explore a throwaway sample workspace python3 scripts/dashboard.py --port 8790 --no-open ``` It is Python 3.10+ standard library: no dependencies, no build step. Run it from your **private workspace**, the folder `scripts/init-workspace.py` created. Started from the shared delivery checkout instead, it only offers to create that workspace. The easiest route is still the start prompt from the [three-step start guide](https://launchrepo.dev/guides/start-in-three-steps/): the agent creates the workspace, starts the server and hands you the link. #### The overview The first screen answers "what needs me?" before anything else: CAPTCHA and two-factor handoffs the agent could not complete, platforms marked blocked, overdue follow-ups and unfinished onboarding. Below that come your products with totals per state group — needs you, problems, in review, scheduled, live — and the workspace health read from `workspace.json`. If you only open the dashboard once a week, this is the page to look at. #### The product page Each product gets a readiness checklist produced by `doctor.py`, the last session summary, its submissions with filters, the onboarding checks, the product brief, identity, permissions and notes. An "agent view" lists which files are filled in and which are still empty — useful when a session ends early and you want to know what the next one will ask about. The state vocabulary shown here is the tracker's; the [listing status](https://launchrepo.dev/glossary/listing-status/) glossary entry explains what each state means. #### Plan and resume a run Start with a target of **10 new confirmed submissions** and **one browser worker**. The planner builds the run from free-ready routes and also saves a time budget: 15 minutes per platform and, by default, 150 active minutes in total. If fewer suitable routes exist than your target, it offers the smaller, honest run. Save the run, then copy its prompt into your agent. Use `/goal` when your host supports it; otherwise paste the same text as a normal message. The dashboard stores the plan and shows the remaining work, but it does not launch agent workers or perform browser actions. A goal cannot override provider limits or human challenges. Only confirmed new submissions count: pending review, queued, scheduled or live, once per platform. Drafts and existing listings do not count. Resume a saved run instead of starting a replacement that forgets previous progress. The [run guide](https://launchrepo.dev/guides/launch-run-from-start-to-finish/) explains completion, handoffs and window cleanup. #### Recording outcomes, catalog and prompts The **Record outcome** form writes through `scripts/record.py` and applies exactly the command-line rules: one of the distinct states, no links or secrets in notes, a public URL plus your attestation for `live`, a launch date at or after the floor for `scheduled`, and an explicit replace when a row already exists. The [outcome recording guide](https://launchrepo.dev/guides/recording-outcomes/) goes through each of those rules and why they exist. **New product** takes a product name, suggests an editable folder name with checks for duplicates and reserved names, creates the folder from `templates/project` and hands you either the onboarding prompt for your agent or the forms to fill yourself. **Catalog** opens on the verified free-ready routes, with conditional, research-only and unavailable routes in separate views; you can search and filter, read any playbook, overlay one product's status and record directly from the list. **Agent prompts and docs** shows the agent prompts with copy buttons and renders the kit documentation in place, so you rarely need to open the markdown files by hand. #### What it will never do The boundaries are deliberate and worth knowing before you rely on it: - It binds to `127.0.0.1` and rejects cross-site requests. - It edits only the product JSON and markdown files the agent also edits. `credentials.json` is shown as platform, method and state; its values are never sent to the browser. - It does not submit anything, does not control a browser and does not verify a listing. Recording a state is an **operator statement**, not evidence — the dashboard makes that statement easy to make and hard to make wrongly, nothing more. Where the dashboard sits between the product, the agent and the directories is drawn out on the [how-it-works page](https://launchrepo.dev/how-it-works/). If you want to try it with no workspace of your own, `--demo` is the way in. ### Confirm how you are represented before listings go public Source: https://launchrepo.dev/guides/confirm-public-representation/ · Updated: 2026-09-17 The kit’s representation briefing: three concrete examples of how the agent will describe you — bio, launch intro, why-I-built-this — approved before a listing. Most directory forms have two halves. One describes the product; the other describes *you*: a maker bio, a name and affiliation, sometimes a "why I built this" comment on a launch board. The kit keeps those halves apart on purpose. Product claims come from the copy workshop and live in `copy.md`; personal claims come from `identity.json` and a short session the kit calls the representation briefing, described in `PR-BRIEFING.md`. This guide explains what that session is, why it exists, and what ends up in `representation.md`. #### Why a separate session An agent that has just filled `product.json` knows a lot about your product and very little about how you want to be presented. Left alone, it will improvise a bio from whatever it can find — an old employer, a previous project, the city in your GitHub profile — and paste it into a public [maker profile](https://launchrepo.dev/glossary/maker-profile/) where it is hard to take back. The briefing exists so that nothing personal reaches a listing until you have seen the exact sentences that will be used. It runs once per product, before the first personal fact goes public, and again whenever those facts change. #### The three questions The agent asks you directly, in plain language: 1. **Are you presenting as an individual, a company, or both?** This decides whether a form's "maker" field gets a nickname, a legal name or an organisation. 2. **Which nickname, name and affiliation may appear?** Not every fact in `identity.json` is meant for every listing. 3. **What must never be said about you?** Past products, an unrelated employer, your real location — whatever you would rather not see attached to a launch post. Notice what is *not* asked: the agent does not invent options and ask you to pick. It collects constraints and then writes from confirmed facts only. #### Three examples, shown verbatim Using only what you confirmed, the agent drafts three short pieces and shows them to you word for word: - a **one-line maker bio** for a directory profile; - a **one-sentence launch or forum introduction**, the kind of opener a Show HN-style post or a launch board comment needs; - a **one-sentence "why I built this"** comment. Then it asks the only question that matters: is anything here wrong, exaggerated or missing? Every correction is applied to the examples themselves, not just quietly noted in `identity.json`. That distinction is deliberate — an agent that fixes the data file but keeps a draft with the old wording will reuse the old wording. Nothing you have not seen gets published. #### What is saved, and where The approved examples, your corrections and the approval date go into `representation.md` in the product folder of your private workspace. From then on, any playbook step that needs a bio or an intro reads from there instead of composing something new. Two boundaries keep the file trustworthy: - Personal claims are never blended into `copy.md`'s product claims, and vice versa. The [product context file](https://launchrepo.dev/glossary/product-context-file/) describes the product; `representation.md` describes you. - The file is part of the private workspace, never of the shared delivery repository, and it contains only facts you approved for publication — not your private account email or anything else from `identity.json` that you marked as private. #### Where it fits in the first session The briefing sits in the third phase of the [agent-led onboarding](https://launchrepo.dev/guides/first-session-onboarding/), right after `identity.json` is filled and before any browser work on a directory. It takes a few minutes. If you skip it and let the agent write bios ad hoc, you will find out how you have been described when you search for your own product on the [Product Hunt](https://launchrepo.dev/directories/producthunt/) maker page — the [solo-developer launch checklist](https://launchrepo.dev/blog/product-hunt-launch-checklist-solo-developers/) has more on why a maker profile is worth preparing before launch day rather than after. ### Set a launch-date floor before anything is scheduled Source: https://launchrepo.dev/guides/launch-date-floor/ · Updated: 2026-09-30 How earliest_launch_date in product.json works: what the tracker refuses, what it cannot influence, why free directories publish late, and how to pick the date. The launch-date floor is one field, one question and one refusal. The field is `earliest_launch_date` in `product.json`. The question is asked during onboarding: is there a date before which nothing should go public? The refusal is in `scripts/record.py`: it will not mark a platform as `scheduled` for a date earlier than the floor, and it will not accept `scheduled` without a launch date at all. Everything else in this guide follows from those three facts. The feature shipped with the 15 September 2026 release on the [changelog](https://launchrepo.dev/changelog/). #### What the floor does When an agent records a [scheduled listing](https://launchrepo.dev/glossary/scheduled-listing/), it passes the date the platform confirmed: On Windows, use `py -3` instead of `python3` in the commands below (or `python` if that is your Python 3.10+ command). Keep your workspace in a private local folder outside OneDrive or other sync folders. For multiline shell examples, put the command on one line and remove the trailing `\` characters in PowerShell. ```sh python3 scripts/record.py --project ../private-product tinylaunch scheduled \ --launch-date 2026-10-14 \ --note "Weekly slot confirmed; approval still outstanding" \ --next-action "Verify listing on the launch date" ``` If `product.json` holds `"earliest_launch_date": "2026-10-12"`, that command succeeds. With `--launch-date 2026-09-28` it is rejected with a message saying the date is earlier than the owner-authorised floor — and nothing is written. Leaving the field blank means there is no floor. The [local dashboard](https://launchrepo.dev/guides/local-dashboard/) shows the floor in the Record outcome form, where the launch date cannot be set earlier, so the number is visible without opening the file. #### What it cannot do The floor is a guard on *your* records, not a lever on the directories. It does not delay a submission, because submitting and publishing are different events and the agent controls only the first. It does not stop a moderated directory from publishing whenever its queue reaches you. And it does not make a confirmed date a publication guarantee: a slot on a launch board can still depend on approval, which is why the runbook tells the agent to keep any outstanding approval in the note. The [outcome recording guide](https://launchrepo.dev/guides/recording-outcomes/) covers that convention. #### Why weeks, not days The onboarding instructions make the agent warn you up front that many free-tier directories queue submissions for review and that publication can take several weeks. That warning is drawn from what the public field guides on this site observed in September 2026: a [SaaSHub](https://launchrepo.dev/directories/saashub/) page that was reachable but labelled *Pending approval*, a [PitchWall](https://launchrepo.dev/directories/pitchwall/) review window stated as more than 30 days, a [TinyLaunch](https://launchrepo.dev/directories/tinylaunch/) weekly slot with approval still outstanding, [Uneed](https://launchrepo.dev/directories/uneed/) allowing one scheduled launch at a time per free account. Free tiers are moderated by people with a queue. A floor lets you submit early to the moderated directories — submission is not publication — while keeping the platforms that *let you choose a date* from firing before your announcement is ready. #### Choosing the date Two rules of thumb from the kit's own docs and the [launch-date article](https://launchrepo.dev/blog/launch-date-floor-when-should-listings-go-live/): - Pick the floor as the first day of the week you want listings to start appearing, not the day you plan to start submitting. The gap between the two is where the review queues do their work. - Do not confuse a floor with a target. A target is where you would like things to land; the floor is the earliest anything under your control is *allowed* to land. Directories make targets unreliable and floors cheap. If you decide later that the date was wrong, change the field; the tracker re-checks it on the next `scheduled` record. Existing rows are not rewritten, so review anything already scheduled against the new date yourself. The concept in one paragraph, with related terms, is on the [launch-date floor](https://launchrepo.dev/glossary/launch-date-floor/) glossary page. ### Recording outcomes: states, evidence and record.py Source: https://launchrepo.dev/guides/recording-outcomes/ · Updated: 2026-09-30 How the kit’s tracker records what actually happened on a directory: the eleven states, the observation each requires, the record.py flags and the note rules. Every directory attempt ends with one command. `scripts/record.py` writes a single current row per platform into `submissions.json` in the product folder, and it refuses rows that the kit considers unproven or unsafe. That refusal is the whole point: the tracker is what stops "we submitted to 40 directories" from meaning "we filled in 40 forms and hoped". This guide covers the states, the evidence each state needs, the command's flags, and what may and may not go in a note. It is a summary of `RUNBOOK.md` and the script's own checks, not a replacement for them. #### The command The runbook's example, from the kit directory with an already-created private project folder: On Windows, use `py -3` instead of `python3` in the commands below (or `python` if that is your Python 3.10+ command). Keep your workspace in a private local folder outside OneDrive or other sync folders. For multiline shell examples, put the command on one line and remove the trailing `\` characters in PowerShell. ```sh python3 scripts/record.py --project ../private-product pitchwall draft \ --note "Product import corrected; final form not sent" \ --next-action "Check saved profile and review final form" ``` Two positional arguments (platform id, state) and three required options (`--project`, `--note`, `--next-action`). The optional flags are `--public-url`, `--confirmed-public`, `--launch-date`, `--replace`, `--worker` (needed for the outcome to count toward a run) and `--invalidate-run-confirmation`. The platform id must be a lowercase slug, the state must be one of the eleven below, and the tracker exits with an explanation whenever a rule is not met. The [local dashboard](https://launchrepo.dev/guides/local-dashboard/)'s record form calls the same function with the same rules. #### The eleven states and their minimum evidence The runbook's table, in short: | State | What you must have observed | | --- | --- | | `draft` | Work prepared; final submission not confirmed. | | `prepared_needs_human` | A precise owner action or challenge (CAPTCHA, 2FA) blocks prepared work. | | `submitted_pending_review` | The platform explicitly received the submission; moderation remains. | | `queued` | The platform confirms a queue position or waiting-list state. | | `scheduled` | The platform confirms a launch date on or after the floor; outstanding approval stays in the note. | | `live` | Public listing verified, no pending label; public URL and `--confirmed-public` required. | | `already_listed` | An existing public listing verified; same requirements as `live`. | | `blocked` | Eligibility, account capacity or a mandatory missing fact prevents progress. | | `deferred_paid` | The usable route requires payment; nothing was bought. | | `not_a_fit` | The product does not meet the audience or listing criteria. | | `unavailable` | The route or platform cannot currently be used; note the problem. | The distinctions that matter most are [draft vs. submitted](https://launchrepo.dev/glossary/draft-vs-submitted/) and pending vs. [live](https://launchrepo.dev/glossary/live-listing/). A thank-you screen does not make a listing live. A page you can reach can still be pending approval. A ticked "also distribute to our partner" box does not mean a second platform received anything. Each platform's result stays independent so that totals are never inflated. #### The rules the script enforces - **Public states need proof.** `live` and `already_listed` require `--public-url` with a reviewed HTTPS URL — no query string, no fragment, no account, dashboard or login paths — *and* `--confirmed-public`, your statement that you looked at the page. - **Scheduled needs a date.** `--launch-date YYYY-MM-DD` is mandatory and must not be earlier than `earliest_launch_date` in `product.json`; the [launch-date floor guide](https://launchrepo.dev/guides/launch-date-floor/) explains why. - **Notes stay clean.** Notes and next actions may not contain links, email addresses, `password=`-style pairs or known token prefixes. The tracker file is meant to be shareable; evidence with account URLs belongs in private storage. - **One row per platform.** If the platform already has a row, the command fails unless you pass `--replace` — after inspecting both the existing row and the platform. Replacing is intentional, never a side effect. - **No symlinks, atomic writes, a lock file.** Boring details, but they are why two agents writing at once do not corrupt the tracker. #### Resuming without duplicates At the start of the next session, read the tracker before touching any form. Prioritise human handoffs and scheduled launches due for verification, then pending submissions whose stated review window has passed. If a platform gives no review timing, agree on a follow-up date with the owner instead of inventing one. And never resubmit to move up a queue: recheck the existing record. The tracker stores current state, not history; if you need an audit trail, archive redacted run summaries separately. For worked examples of the states on real platforms, read the [submission-states article](https://launchrepo.dev/blog/submission-states-submitted-pending-scheduled-live/) and the older guide on [tracking without double counting](https://launchrepo.dev/guides/submission-status-tracking/); the vocabulary itself is defined under [listing status](https://launchrepo.dev/glossary/listing-status/). ### A launch run from start to finish Source: https://launchrepo.dev/guides/launch-run-from-start-to-finish/ · Updated: 2026-09-30 One directory batch with the kit, end to end: brief, batch selection, one platform at a time, evidence-based states, resume rules, and a realistic first result. A run has a target, recorded outcomes and a clear next action. Start with **10 new confirmed submissions**, with **one browser worker** by default. Your agent performs the work; the dashboard saves the plan and progress. Begin after [onboarding](https://launchrepo.dev/guides/first-session-onboarding/) and the [Chrome connection test](https://launchrepo.dev/guides/connect-your-agent-to-chrome/). #### 1. Check the product and permissions Read the existing product brief, identity, permissions and submission records. Use verified features, current pricing, genuine screenshots and your approved public wording. A trial stays a trial. Unknown mandatory facts stay unknown until checked. Confirm the destination account and search for existing listings before creating anything. #### 2. Plan the run Choose the number of new submissions and the time budget in the local run planner. The recommendation is 10 submissions with one worker, 15 minutes per platform and 150 active minutes in total. The plan draws only on free-ready routes: fresh, evidenced, working and unconditionally free. A second worker is an advanced option you choose yourself; hardware alone never enables it. Two workers require separately controlled browser workspaces and distinct platform assignments. If they share browser focus or cannot keep their work isolated, use one. Never let both select the same platform. Read each candidate’s full playbook and check current eligibility and free access before opening its form. Replace unsuitable or paid routes with suitable alternatives; do not lower your standards to reach ten. #### 3. Start with an explicit goal Copy the saved run prompt. If your agent supports `/goal`, use its goal feature with that text. Otherwise paste it as a normal message. `/goal` is a host feature, not a universal LaunchRepo command. Provider usage limits, missing permissions and human challenges still apply. A typical goal is: > Complete 10 new, relevant, free directory submissions for this product. Use one browser worker and one platform at a time. Read the saved run and existing submissions first. Save each confirmed outcome and its evidence, then continue. Replace blocked candidates with suitable alternatives. Stop when the target is reached or explain the exact reason no further progress is possible. Preserve the remaining work for resume. #### 4. Submit, save, close, continue For each assigned platform: 1. Recheck eligibility, free access, required fields, consent and the signed-in identity. 2. Prepare approved copy and genuine assets. Read fields back and verify that drafts persisted. 3. Inspect the final total. Skip required payments. If an official badge is required, follow the recorded website permission and verify the public deployment before attesting. 4. Submit within the owner’s permission and inspect the actual confirmation. A timeout requires checking the account and listing before any retry. 5. Checkpoint the observed result, record it with `record.py --worker` so it counts toward the run, then release the claim. 6. After evidence is saved, close only the window assigned to this submission and its owned verification tabs. Keep personal windows, other workers, the dashboard, unsaved forms and open human handoffs intact. Keep the browser profile for future sign-ins. 7. Continue until the saved goal is reached or no eligible work can proceed. #### 5. Count confirmed submissions accurately | Outcome | Counts toward the run? | | --------------------------------------------------------------- | ----------------------------------------- | | New `submitted_pending_review`, `queued`, `scheduled` or `live` | Yes, once per platform, with confirmation | | Later transition from pending to live | No additional count | | `already_listed` or an older submission | No | | Draft, CAPTCHA, 2FA or missing mandatory fact | No | | Paid route, unsuitable or unavailable platform | No | Pending review is a successful submission, not a promise of publication. A scheduled launch must respect the product’s earliest launch date. Partner syndication counts separately only after that partner confirms its own submission. See [recording outcomes](https://launchrepo.dev/guides/recording-outcomes/) for the tracker’s evidence requirements. #### 6. Resume the remaining work When a session stops, preserve the run and its remaining target, update `SESSION.md` with the next action and keep human handoffs visible. Start the next session with the saved resume prompt. Reuse standing permissions, recheck unresolved attempts and follow platform review windows without inventing an SLA. Never submit again merely to move up a queue. If the dashboard shows **6 of 10 counted**, there are four new submissions left. It may also show two platforms in progress and one waiting on you; those are not added to the six. If only six suitable free routes exist, finish with that honest result and the reason the target could not be reached. Ten is a target, not a guaranteed inventory of suitable platforms. ### Track directory submissions without double counting Source: https://launchrepo.dev/guides/submission-status-tracking/ Separate preparation, review, queue, scheduling and publication so the next agent knows whether to resume or verify. #### Start with the existing record Search the platform for the exact product name and domain, then inspect the signed-in product list. A public search can miss a pending submission. If a click times out, inspect the account before retrying: a timeout describes the browser response, not the server outcome. #### Use states that answer a different question Draft means work is saved. Prepared means a human action still blocks submission. Submitted pending review means the platform acknowledged receipt. Queued means an item is waiting for processing or a slot. Scheduled means a date is confirmed, and may still depend on approval. Live requires a verified public listing. #### Two examples that prevent inflated totals SaaSHub produced a public page still labelled Pending approval, so accessibility did not justify live. TinyLaunch confirmed a future launch while the dashboard still required approval. Store that qualification in the note instead of reporting a completed publication. #### Make the next action reproducible Record the platform, status, check date, a concise reason and next action. Keep account URLs and evidence in private storage. Share only reviewed public URLs. Never put login links or mailbox screenshots in a public report. The included tracker stores one current row per platform and requires explicit replacement. #### Resume safely When another agent takes over, read the latest row before touching the form. Check pending items on the owner’s chosen review date. Change to live only after checking the public page. A record tool cannot verify a platform for you; the operator must inspect the confirmation. ### Plan directory work with a zero-spend budget Source: https://launchrepo.dev/guides/zero-spend-launch-planning/ Use eligibility and asset checks to decide where to spend agent time before attempting a submission. #### Prepare a verified product brief Record the product URL, audience, actual features, current pricing and approved screenshots. Keep unknown metrics explicitly unknown. A trial with limited credits is not a permanent free plan. Prepare a concise outcome description and a separate comparison description using real alternatives. #### Check fit before form filling Choose categories the product actually serves. Inspect the current submission route and account capacity. Uneed’s observed limit of one scheduled launch per free account and Fazier’s observed rating and badge requirements show why a nominal free route can still be unavailable to your product. Do not turn those observations into a universal promise. #### Define stopping conditions Stop for payment requirements, missing verified mandatory facts, CAPTCHA or two-factor authentication. Leave a useful handoff describing the blocker. Do not buy a queue jump, fabricate eligibility, remove another product or create a second account to evade limits. A badge requires permission to change the product website. #### Review every final screen TinyLaunch’s observed workflow included optional services and another upgrade dialog after scheduling. Check the actual total and final confirmation. On PitchWall, review imported text and login consent before submitting. Saved profile text should be reopened to verify that it persisted. #### Budget attempts honestly Divide toolkit cost by the number of products multiplied by suitable planned attempts. For example, a round, illustrative EUR 100 across four products and six attempts each is about EUR 4.17 per attempt, excluding agent costs. If only three directories fit, the allocation doubles. None of these numbers predicts acceptance, traffic or ranking. ## 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/)