The stack the company builds on and the tools it runs — useful for a pitch, a partnership, or sizing up a competitor without a single call.
The stack they build on and the tools they run — useful for a pitch, a partnership, or sizing up a competitor. It's one of the nine sections in every dossier, and below is exactly what this one does — what it surfaces, where those facts come from, and who leans on it.
Concretely, the tech fingerprint section gathers:
None of it requires the company's cooperation — it's all there in the open record, just scattered until the dossier pulls it into one place. You can see it rendered on a real business in the sample dossier.
Tech signals are detected from publicly observable surfaces only — the technologies a site loads in any visitor's browser, public DNS and infrastructure records, open engineering blogs and conference talks, and the stack named in job descriptions. Nothing here involves probing private systems or unauthorized access; it's the same fingerprint anyone viewing the public site could read. Detection is best-effort, so the section separates confidently identified tools from likely ones, links the evidence, and notes that the public surface can lag the internal reality — a company may have migrated off something still visible at the edge.
This section earns its keep for anyone whose work turns on it:
See how the whole file fits together on how it works, browse the other eight sections, or open a dossier and read this section on a company that matters to you.
No. It reads only publicly observable surfaces — the technologies a site loads for any visitor, public infrastructure records, open engineering content and job descriptions. The same fingerprint anyone viewing the public site could read.
Best-effort. The section separates confidently identified tools from likely ones and links the evidence. The public surface can lag the internal reality, so a migrated-off tool may still show at the edge.
the tools they build on, without a call.