Submit an AI tool to LaunchAI
Publish a clear product page with the information people need to decide whether your tool fits their workflow. The listing stays connected to your maker profile and official website.
Prepare a listing people can evaluate
- Official product URL. Use the canonical public website, without tracking parameters or an embedded login.
- Specific product story. Explain the audience, problem, workflow, important features, and practical limits in at least 240 characters.
- Accurate discovery fields. Choose the current pricing model, supported platforms, and up to three relevant categories.
- Useful media. A clear logo and product screenshot help readers inspect the actual product instead of relying on marketing copy.
- Repository details when relevant. Include the public repository and mark the product open source only when people can inspect the code.
What happens after submission
You will sign in before opening the publishing form. LaunchAI can read public metadata from the official website to prefill part of the listing, but you remain responsible for checking every field. Once the required details and categories are saved, the product receives a public URL and appears in the directory.
The product page identifies the maker when it was submitted through a profile. Website links on maker-published pages use the standard ugc relationship so search engines understand that the destination was supplied by a user. Submission is for discovery and referral traffic; it does not guarantee indexing, ranking, clicks, reviews, or a particular kind of backlink.
Quality and safety rules
Submit a working product that a visitor can understand from public information. Do not use another company's identity, submit duplicate domains, hide the destination behind unrelated redirects, or make claims that cannot be checked. Uploaded screenshots must belong to your product and may not expose customer data, credentials, private conversations, or confidential interfaces.
Listings can be corrected, limited, or removed when the destination becomes unsafe, deceptive, unavailable, or materially different from the submitted description. The directory is not a security certification or procurement review. Visitors should still inspect current product terms, data handling, prices, and technical requirements on the official website.
How to write a useful product description
Lead with the person and job. Then explain the input, the workflow, the output, and the point where a person reviews or controls the result. Name supported environments and material limits when they affect adoption. Concrete statements help readers compare products; broad claims such as "the best AI platform" do not.
A useful description can answer five questions in a few paragraphs: Who is it for? What recurring problem does it address? What does the user provide? What result does the product return? What should a buyer verify before relying on it? You can update the source material before submission when the public website does not explain these details clearly.
Common submission questions
Does it cost money to submit?
The current maker publishing flow does not charge a listing fee. A future paid promotion product, if introduced, would need to be disclosed separately from ordinary directory inclusion.
Can agencies or teams submit a product?
Yes, provided the account has authority to represent the product and the listing points to its official public website. Use a clear organization or maker identity on the connected profile.
Can I submit a product that is still in beta?
Yes when a visitor can access or meaningfully evaluate the current product. State beta limits, waitlist status, platform support, and pricing accurately rather than describing planned features as available.
Ready to publish the product page?
Sign in, import the public details, review every field, and add the context that an automated import cannot know.