Ask anything about AXIS Launch — open Q&A thread
This is the standing open thread for questions that don't fit an existing thread. No format required. Moderators answer within 1 business day; questions that come up more than twice get promoted into their own knowledge-base thread.
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 this thread: 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, below are the first questions from our intake inbox, answered, each labeled with its source. Ask yours in the comments — what do you want to know?
Replies (5)
From the intake inbox: "Is AXIS Launch itself AI-generated? The whole site pitch is about AI-built apps."
Substantially, yes — the platform content system, spec documents, and much of the tooling are AI-built, with human review on everything published. 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 AI-built. The interesting question is never whether AI wrote it, but whether it works and whether its claims are verifiable.
From the intake inbox: "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 (we never delete listings), and 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.
From the intake inbox: "Why Squarespace? A platform for developers built on a no-code site builder seems off."
Because the product is curation, permanence, and verified data — none of which require custom infrastructure at this stage, and all of which benefit from us spending time on review quality instead of servers. The forum you are reading is a blog collection with moderated comments, and it does the job. When something needs real engineering (PAID, the Passport, the intake pipeline), it gets real engineering. Choosing boring tools where boring tools win is, we'd argue, exactly the judgment you want from a platform that reviews apps for a living.
From the intake inbox: "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 three places, all published: Fast Track and Featured listing fees, auction transaction fees (on /auction-rules), and PAID payment processing. If a fee isn't on a public pricing page, we don't charge it.
From the intake inbox: "You say 'we list fewer than half of submissions.' Prove it?"
The honest version: you can't independently audit our rejection rate, since rejections are private. What we can do, and now do: publish the running counts monthly (submissions received, listed, rejected) on the /about page, dated like every other metric here. First edition went up August 2026. It is self-reported — but it is a falsifiable public number rather than a vibe, and self-imposed accountability is the tool we have.
Threads are permanent — locked, not deleted, once resolved. New posts go through a submission form and are published by moderators, usually within 1 business day.