LaunchRepoEvery few days someone asks me some version of the same question: “Why is LaunchRepo a single payment? You could make more with a subscription.” Fair question. It is also the question I would ask before buying, because a one-time price for something that touches 346 third-party websites sounds either generous or suspicious, and I would want to know which.
This is the honest answer, from the person who set the price. It covers what you pay, what you get, what happens to the price over time and — the part most pricing pages skip — what we deliberately do not promise. The short version is on the pricing page; this is the reasoning.
What you actually buy
LaunchRepo is a private GitHub repository. Inside: playbooks for 346 directories, a product.json template, AGENTS.md and a runbook for your agent, the browser setup guide, a tracker with record.py, and a local dashboard. You clone it. It runs on your machine, with your accounts, driven by an agent you already pay for.
There is no server of ours in that loop. No queue, no credits, no per-launch metering, no “your plan includes 3 products”. That is not a marketing choice; it is the architecture. A repository you have cloned is yours in a way a dashboard login never is, and a subscription for something you already hold a copy of would be a subscription for permission.
So the licence is written to match: one payment, perpetual use, unlimited software products you or your company own and operate, unlimited AI agents and team members working on them. Repository access is bound to one GitHub account; you may clone and keep your copy. Two limits, both stated in the terms: no resale or redistribution, and launching products for clients needs a separate licence. That second one is the only place where “unlimited” has an edge, and it is the edge you would expect — your products, not your agency’s roster.
Why not a subscription
I build SaaS products myself. When I launched seomap.dev on directories, the work was front-loaded: accounts, forms, verification emails and follow-ups in a burst, then months of nothing, then the next product. A monthly fee for that pattern is a fee for the months of nothing.
The comparison of submission services shows the three models side by side — subscription tools, pay-per-product services, and a one-time toolkit. Each fits someone. If you launch constantly and want somebody else’s software to do the submissions, a subscription is rational. If you want one launch done and never think about it, a per-product service is rational. LaunchRepo is for the third case: you ship more than one product, you already run an agent, and you would rather own the process than rent it.
The comparison pages name the vendors and their checked prices; here I only want to say the obvious thing plainly. If the second product is included, I make less money per customer than a subscription would. I am fine with that. I would rather be the repository you keep than the invoice you cancel.
How the price rises, and why
The launch price is EUR 99.98 including 19 % German VAT at the time of writing; the checkout shows the live number for your country. After every 20 completed sales the price rises by 20 %. The counter is real transactions, not a timer or a countdown. Whatever the checkout shows at the moment you buy is what you pay, and later steps in either direction do not affect you.
Two reasons for the ladder. First, early buyers take a risk on a product with a short track record and a small changelog; a lower price is the honest way to acknowledge that. Second, keeping playbooks accurate is ongoing work, and a slowly rising one-time price is a saner way to fund it than adding a subscription later and grandfathering everyone into a support ticket.
What the ladder is not: fake scarcity. The counter on the pricing page loads from the same backend that processes payments. If it says twelve left at this step, twelve sales will move it. If it does not load, the page says so and shows the launch price as a fallback.
What we deliberately do not promise
This is the section I care most about, because “pay once” invites people to fill in the blanks with “forever, everything, whenever I ask”. Here is what the terms actually say, in my words.
Updates. We may publish updates to the repository at our discretion. Updates we publish are included for everyone who bought — you do not pay again for a new playbook batch. But we do not promise any particular update, cadence or future scope. Directories change their forms. A playbook describes what we observed on the noted date. If a platform changes after your purchase, that is not a defect of LaunchRepo; it is the reason the tracker records dates.
Support. Support is by email, best effort, with no guaranteed response times. It is a small company. Support does not include performing submissions for you, configuring your AI agent, or resolving problems with a third-party platform or your account there. If that sounds thin, compare it with what a done-for-you service charges per product and decide which you need.
Outcomes. No listing, backlink, ranking or traffic is guaranteed. Every directory decides for itself. The playbooks default to the free path and never authorise a purchase on your behalf, and the tracker records deferred_paid when the only route costs money. If someone tells you a directory result is guaranteed, they are describing their refund policy, not the directory.
Agent costs. Your agent’s usage is billed by your provider — Anthropic, OpenAI, Cursor, whoever you use — and is not included. A launch run across dozens of directories costs real tokens. I do not know your number, and I will not print a made-up one.
Refunds. LaunchRepo is digital content, delivered immediately after payment, so all sales are final once access is delivered. That is why the public material exists: field guides, the guides, the FAQ, this blog. Read before buying; write to us if you are unsure whether it fits.
What “yours forever” means in practice
The thing most likely to outlast us is the repository on your disk. If The CodeCave stopped operating tomorrow, your clone would still contain the playbooks as of the last pull, your product files, your tracker and the dashboard, which runs on the Python standard library with no server. That is the concrete meaning of perpetual: not that we promise to exist forever, but that nothing you bought depends on us continuing to.
The about page has the company facts, the founder, and the seomap.dev pilot the toolkit came from. It is a small German GmbH, not a venture-backed platform, which is a large part of why the pricing looks the way it does.
Who should not buy this
- You want someone to do the submissions. A done-for-you service is the right product; the comparison pages say which ones publish what.
- You do not run an AI coding or browser agent yet. The repository assumes one; the agent pages explain what it needs.
- You expect a support SLA or a roadmap commitment. We offer neither, on purpose, and I would rather lose the sale than the trust.
- You launch client products. Write to us about a separate licence first.
Everyone else: one payment, every product you ever build, and a tracker that tells you the truth about what went live. That is the deal, and it is the whole deal.
Sources: the pricing page, the terms of service (sections on licence, updates, support and warranty) and the about page. Price stated as the launch price at the time of writing; the live price and step counter come from the checkout backend. No sales, revenue or customer figures are given.