OpenMatch

Software selection as it actually happens: each function gates in turn, on the field the last one left. IT rules out what cannot pass a security review. Quality rules out what cannot run their processes. Finance rules out what cannot be defended. Every elimination keeps its reason and its source.

—

Rank by

1 · Your product

The URL is not a formality. A harvester renders your public site in a real browser, drives your pricing calculator and any wizards, and reads what a buyer would actually see — then proposes a draft record you can correct. What it cannot find, it records as undisclosed, because absence of a mention is never treated as evidence of absence.

Product name

Company

Public website

Include your pricing page if it lives on another domain. Interactive calculators are fine — preferred, in fact.

Contact email

Who to ask for — optional

Never shown to buyers, and never part of your public record. It is stored separately from the listing, and it exists for two things: getting you back to your listing if you lose the link, and reaching a human if a buyer disputes something on it. You can also find a listing again at any time by searching for your domain — no email needed for that.

2 · Let the code look at the software

A website tells us what you say. The software tells us what you built. Point this at your product folder and the reader works out what the product actually does — whether an administrator can build a form, whether workflows are configurable without you, whether the audit trail can be altered — and cites the file it found each answer in.

Your software folder

Nothing is uploaded. Your browser reads the folder locally and this page runs the reader on it; only the derived answers and their file citations are ever sent.

What the reader does, and what it refuses to do

The point is to let a machine confirm what you can do without asking you to hand your product to a competitor. The terms are narrow and worth reading:

Your source never leaves this machine. The reader runs in your browser. What is posted is the derived answer — "conditional fields, found in FormSchemas/_templates/ncr.json" — and nothing else.
Records are counted and ignored. Spreadsheets and exported registers are your customers' data, not your software. They are never read and never scored, and if the folder is full of them you will be told.
It reads mechanism, not vocabulary. A file named for a module proves less than a definition file carrying the key that implements it, and a word that appears in every page is treated as navigation rather than as evidence.
It cannot see a certificate. Source can show that signatures bind to records. It can never show that an auditor signed anything, so certification claims stay capped no matter what is in the folder.
It never reports absence. Not finding something is a fact about the search. Anything unfound stays undisclosed — exactly as it does for a vendor who never registered.
It can lower your score. If the software contradicts your site, the observation stands over the copy. That is the entire reason a buyer would believe any of it.

1 · Your product

2 · Let the code look at the software

What the reader does, and what it refuses to do

3 · What is still unanswered — optional