How we know

Stackprint is only worth reading if the evidence holds. These are the rules the data follows, and the places we deliberately claim less than the raw numbers would allow.

252 companies · last crawl 11 Oct 2026 · 9194 observations withdrawn

1. Every fact carries a date and a receipt

   A fact exists because something was observed: a response header, a DNS record, a line of page source, a sentence in a job post. We store what we saw, when we saw it and where, and the page links back to it. If we cannot say when we learned something, it does not go on the page.

2. Nothing is submitted by anyone

   No company, vendor or visitor can add, edit or remove a fact. Every row comes from our own crawl. That is also why vendors cannot pay for placement: there is nothing to place.

3. Job posts: engineering roles only

   A public job board says what a team runs that no crawler can see. We read only the engineering-side postings — engineers, data, infrastructure, security, QA — because a sales or partnerships post lists what customers and partners use, not what the company runs. Every company page shows how many posts we read, how many were engineering, and how many were left out.

4. A repeated line counts once

   Boards paste the same “our stack” line into every posting. Publishing a sentence twenty times is one statement by the company, not twenty, so we group those tools onto one card, quote the line, and count it a single time towards confidence. Separate mentions in separately written posts do each count.

5. One post is a hint, not a claim

   A tool named in a single job post appears under “Hints” and is never counted as a user of that tool. A tool listed as one option among several (“AWS, GCP, or Azure”) counts for a third of a firm mention, and if that is all we ever see, it stays a hint.

6. A verification record is an account, not usage

   A DNS record such as MS=ms12345 proves a company has an account somewhere. It says nothing about how much they use it, so those sit under “Verified accounts” and never count as the company's email or stack.

7. A job board must be provably theirs

   A board counts only when a posting URL sits on the company's own domain, the domain appears in the posting text, or the company's careers page links to that board. A matching name is not proof: “ghost”, “lovable” and “runway” all belong to other companies with those names, and we withdrew what they produced.

8. We withdraw, we do not delete

   When a rule turns out to be wrong we fix it and withdraw what it produced, with the reason. The original observation stays on record, marked withdrawn. Every one of them is listed on corrections, which is our own record of our own mistakes, not reports from users.

9. We crawl politely

   One request to a home page per scan, robots.txt checked first and obeyed, and an honest user agent that links to a page explaining the bot. Error pages and bot challenges are never fingerprinted: that HTML is not the site.