JStarted by Jonathan (AXIS Launch)
This is the standing thread for questions about AXIS Launch that don't fit an existing thread. To ask one, start a thread on GitHub Discussions (the link is at the foot of this page). A question worth a permanent answer gets its own thread here.
Fair game: listings, badges, auctions, PAID, pricing, moderation decisions, roadmap. Also fair game: pointed questions about the business model — I'd rather answer those in public than have them asked in private.
Not for Platform Q&A: co-founder searches, audit requests, or fundraising questions — those have their own categories with formats that will get you better answers.
To start it off, the replies below answer five questions we wrote ourselves, the pointed ones included.
Question: "Is AXIS Launch itself AI-generated? The whole site pitch is about AI-built apps."
Substantially, yes — the site's builders, its specification documents, much of its tooling and these threads were written with AI tools. We think that is table stakes now rather than a differentiator, which is exactly why 'AI-powered' isn't used as a selling word anywhere on the site: every app here is an AI app. The interesting question is never whether AI wrote it, but whether it works and whether its claims are verifiable.
Question: "What happens to my listing if AXIS Launch shuts down?"
Fair question to ask any young platform. Three honest answers: (1) listings are static, exportable pages — your listing content is yours and we will provide exports on request; (2) the permanence promise is about our policy while operating: a listing is never taken down for want of a payment, and it is retired only when the app itself shuts down or its badge is removed and stays removed after notice. We won't pretend a policy can outlive the company; (3) your PAID payment history is held on the PAID side, not on this site, so the verifiable asset survives independent of the directory.
Question: "Why is a platform for developers a set of static pages? No accounts, no feed, no live anything."
Because the product is curation, permanence and verified data, and none of those needs a live application. Every page here is plain HTML, built from files and checked before it is published; the forms and the admin desk are the moving parts. That keeps the time on review quality instead of servers, and it means a page loads the same for a person, a search engine and an agent. When something needs real engineering (PAID, the Passport, the intake pipeline), it gets real engineering. Choosing boring tools where boring tools win is, I'd argue, exactly the judgment you want from a platform that reviews apps for a living.
Question: "Do you take equity or commission in listed apps?"
No equity, ever — listings and badges involve no ownership stake, so our curation has no portfolio to talk up. Revenue comes from two places, both published: the seller's success fee when an auction closes (on /pricing), and payment processing through PAID, a separate Trust Fabric product. Listings are free, with no paid tier. If a fee isn't on a public pricing page, we don't charge it.
Question: "You say 'we list fewer than half of submissions.' Prove it?"
You can't audit it, and I won't pretend otherwise: rejections are private, and we don't publish how many submissions arrive or how many are listed. What you can check is the bar itself. It is published at /launch, the reasons for rejection are listed there, and every listing on the site is there for you to hold against it. If a listing doesn't meet the published bar, tell me, and I'll fix the listing or explain it.