CESXY welcomes small projects made with AI, whether they took months or one afternoon. A person reviews every submission, and every listing is written plainly. This guide covers what qualifies, how to describe your project, what happens after you submit and why some builds are not listed.
What qualifies
It is public. An editor must be able to open and use your project at a public address. It should not need a private invite, a development setup or credentials only you hold. If it needs a login, say so. The listing will carry the login-required tag.
You have the right to share it. If you built it with other people, or it uses content, data or assets owned by others, make sure you have permission to show it publicly.
It does something. A qualifying project has a core action a visitor can complete. A landing page for a future product, a waiting list or a concept page does not qualify yet.
It respects visitors. It must not be built to harvest personal data, mislead people or manipulate them.
Projects in Health & Fitness, Finance and Family & Kids get extra review. Expect closer questions about what data the project asks for and what it claims to do.
Choosing a category
Pick one main category from the fixed list of 16. You may add up to two secondary categories. Narrower details belong in tags.
Writing a description that tells the truth
Your description is the first thing an editor reads. Once the project is listed, it is the first thing visitors see.
Open with one sentence that says what the project does and for whom. For example: paste a list of ingredients and get a shopping list grouped by aisle. Avoid sweeping claims.
Say whether it needs an account, whether it is free, whether any features are paid and whether it works on a phone. Editors record all of this. A description that matches what they find makes review simpler.
List known limits, such as file types, a single language or a usage cap. It is better that you tell us than that we find out.
Skip superlatives. CESXY listings read as use notes, and a description in the same register needs fewer edits.
What happens after you submit
Your project enters Fresh, the queue of unreviewed submissions, marked as creator-provided. You get a first response from us within 7 days.
Reviews run in queue order. We do not promise a review date, and we cannot move a project up the queue on request. You can check where your submission stands with the reference you receive. The status shows the current stage and the next step, not an estimated date.
When an editor has reviewed it, the project is either published with a badge and a short use note, or its status shows that it was not accepted.
Common reasons a build is not listed
The address does not load. The link is wrong, the project is offline or the host has paused it. Test it in a private browser window first.
The core action fails. The page loads but the main task does not complete, or it fails with an unclear error.
The description does not match. It claims features that are missing, or it leaves out a login or a payment.
Access is restricted. The editor cannot get in without an invite, a private key or credentials you did not supply.
Rights or safety concerns. The work may not be yours to share, it asks for more personal data than it needs, or it sits in a sensitive category without enough care.
It is not ready. It is still a concept, a placeholder or a waiting list.
Before you submit
Open the address in a private window and confirm it loads. Run the core action with at least three different inputs. Write the one-sentence description. Note login, payment and mobile requirements. List known limits. Confirm you have the right to share all of the work. If a login is needed, make a test-only account, never a personal one.
For a fuller pre-launch pass, read our Launch Checklist for AI-Built Web Apps. When you are ready, open Submit.