Our standard
How we curate
codeGuild is a curated catalog, not an open marketplace. Nothing lists itself. Every product that reaches the storefront has cleared the same bar, so that browsing here feels less like wading through listings and more like walking a well-kept shelf.
The four promises
Every product in the catalog is held to four promises. They are what “curated” actually means to us — the difference between a catalog you can trust and a pile of downloads.
Live demos on demand
Every product ships with a working demo you can open and click through before you spend anything. No screenshots standing in for software, no “contact us for a walkthrough” — if it is in the catalog, you can try it now.
Docs before payment
The full documentation — setup, configuration, architecture notes and the changelog — is readable before checkout, not locked behind a purchase. You should know exactly what you are getting and how to run it before you decide.
Honest licensing
License terms are written in plain language and shown on the product page. What you may build, ship and resell is stated up front, with no clauses that quietly change what you paid for.
Support with SLAs
Support is a commitment, not a hope. Each product lists a response-time SLA, and the studio behind it is on the hook to keep the software working against current runtimes and dependencies.
How products are reviewed
Before anything is published, it goes through a hands-on review. We are not checking a form — we are running the software and reading the code the way a buyer would.
- 01We install it clean. Every submission is stood up from scratch on a fresh environment using only the documentation provided. If the docs cannot get it running, it goes back.
- 02We exercise the demo. The live demo has to reflect the real product, not a trimmed-down mock. We click the core flows and confirm they behave as described.
- 03We read the code. We look for obvious security problems, abandoned dependencies and licensing that conflicts with what the seller claims. Quality of structure matters as much as whether it runs.
- 04We agree an SLA. Nothing publishes until the studio behind it commits to a support response time and to keeping the product maintained. That commitment is printed on the product page.
Curation does not stop at launch. Products that fall out of maintenance, break against current runtimes, or stop honoring their SLA are pulled from the catalog until they are put right.