showstack

Is this your product?

This index describes 217 pieces of software and hardware, and it publishes 887 claims about what they can talk to. Most of those claims were written by people who use your product, not by you. You can fix that yourself, today, for nothing.

What this is not

It is worth being blunt, because every trade index eventually gets asked this question.

• You cannot buy an entry. Not a listing, not a position, not a badge, not a category. There is no rate card because there is no rate.
• Sponsoring does not move data. The sponsor button pays for a domain and a build minute. It is recorded in a completely different place from the dataset, by design, and no sponsor has ever seen an entry before it published.
• You cannot delete a true fact. If your protocol support needs a licence, that stays. If a firmware version broke something and the release notes say so, that stays. What you can do is correct it, date it, and tell us what changed.
• There are no logos here. Your name appears because you make the thing, in the same typeface as everybody else’s.

What verifying actually means

Every entry and every interop claim carries one of three confidence levels. They are not grades and the lowest one is not an accusation — it is just an honest note about where the fact came from.

The confidence ladder, and what moves an entry up it

Level	What it means	What we needed to see
unverified	Somebody in the field told us, and it is plausible.	Nothing yet. 0 entries sit here.
reported	A public document says so, but not a first-party one.	A manual, a forum post from an engineer, a conference talk. 307 entries.
verified	A first-party source says so and we linked it.	Your own documentation, spec sheet, release note or reply. 105 entries.

Note the third row carefully: a reply from you is a primary source. You do not need to publish anything new. If you comment on an issue saying “that is right, but the direction is output-only since firmware 4.2”, we cite the issue, credit you, and the entry moves up.

What you get out of it

• Your product described correctly where integrators check. Somebody specifying a system at 2am is reading a compatibility list. Right now, on 747 claims, that list is a stranger’s best recollection.
• Machine-readable, so it travels. Every entry is in a free JSON API with no key and no rate limit, which is exactly what assistants, procurement tools and spec generators read. A wrong entry here becomes a wrong answer in a dozen places.
• A permanent, citable record. Entries have stable URLs and a change history. When a customer asks whether you support a protocol, you can point at something neutral.
• Credit, if you want it. Your handle goes on the entry you fixed. If you would rather it did not, say so and it will not.

Where the index stands, by vendor

Generated from the dataset on every build, so it cannot be flattering. A low number is not a criticism of the company — it means the entries were written by users and nobody from the vendor has been through them yet. The link opens an issue with every entry we hold for you, already listed, ready to be ticked or struck out.

Three ways to do it, shortest first

1. Find your row above and click the link. It opens a GitHub issue listing every entry we hold for you. Tick what is right, strike what is not, and stop. We do the editing.
2. Correct one page. Every entry page has an Edit this entry on GitHub link that opens the underlying file in a browser text box. It is one YAML file per product, and you do not need to install anything.
3. Send us a document. Open an issue with a link to the manual or spec sheet and which entry it corrects. Somebody will do the transcription.