# How we admit and review listings

Canonical page: https://launchinyourcloud.com/guide/review-methodology/


A listing must identify a real product or configured solution, its license or commercial scope, installation and operating responsibilities, a relevant category, and a documented deployment path on at least one named provider in a customer-controlled account or application project. Community projects also need active maintenance and meaningful adoption evidence.

## Evidence that qualifies

A vendor installation guide, an explicit provider compatibility statement paired with installation instructions, or a documented provider, partner, institution or community deployment can establish a path. Read the edition, package, version and account boundary together. Third-party images and community wrappers keep their own publisher and maintenance qualifications.

## Evidence that does not establish a path

A generic Docker image, an integration with a cloud API, a vendor SaaS region, or a marketplace offer without an established customer deployment boundary is insufficient. A partner's deployment statement does not become a vendor support certification. Candidates with unresolved gaps remain [under review](/research/).

## Support and editions

Source-type labels describe who supplies the evidence, not a universal ranking. `vendorSupport: not-assessed` means we have not checked a current vendor support commitment for that exact deployment. Missing edition/version scope does not establish support. Buyer facts use the following states:

- **Not researched:** no field-specific review is recorded.
- **Sources checked — unresolved:** the cited sources did not establish an answer; the scope identifies what was checked.
- **Documented:** the source establishes the stated fact within its scope.
- **Edition-dependent:** the documented capability requires the stated edition, license or mode.
- **Explicitly unsupported:** the source expressly rules out the capability within the stated scope. Absence from a guide is insufficient.

Security controls are separate from compliance attestations. Published license pricing is separate from a workload-specific operating-cost estimate. A customer-hosted installation does not inherit a vendor SaaS certification. Parent platform facts are linked from configured solutions without silently inheriting entitlements or sizing.

## Equal treatment and publisher disclosure

FormKiQ publishes this directory. Its platform and configured business solutions are marked as publisher entries and use the same admission requirements. A configured solution is linked to its parent platform and is not described as a separate software platform. The directory offers a publisher exclusion filter.

## Review and correction

An editor checks sources before changing factual claims. Link-check automation flags problems but never advances review dates or publishes new claims. Source review dates differ from software release dates and build times. [Corrections](/submit/) should identify the listing, exact claim and public evidence. [Change history](/changes/) records additions, updates, removals and evidence changes from its stated baseline; it does not invent earlier history.

[Download evaluation templates](/guide/toolkit/).

## Related questions

- [Does “supported on AWS” mean software will work on any cloud?](https://launchinyourcloud.com/questions/provider-badge-evidence/)
- [How does LaunchInYourCloud decide which software to list?](https://launchinyourcloud.com/questions/listing-policy/)

