Technographics & Tech Stacks
From AltData.wiki, The Alternative Data Encyclopedia
Technographics & Tech Stacks is one of the categories of alternative data covered by The Alternative Data Encyclopedia: Detection of technology stacks per company: which technologies each business uses, with evidence and date of observation, plus adoption-change events.
The field grew out of the sales-intelligence market — BuiltWith began profiling web technologies in 2007 and vendors like Datanyze followed — and funds adopted it after 2015 as a way to track cloud migrations, security spend and vendor churn. Technology-adoption change is now a standard ingredient in software and IT-services equity research.
For a first-party benchmark in this category, see TheirStack and its technographics dataset, indexed on this hub with delivery, history and refresh details.
The signal
Detection of technology stacks per company: which technologies each business uses, with evidence and date of observation, plus adoption-change events.
Rows typically map a company to a technology, a detection method (DNS, certificate, pixel, job ad) and a first/last-seen date. The derived layer adds adoption and abandonment events.
Why investors pay for it
Stack changes flag investment, migrations and vendor churn before they surface in revenue or surveys.
Vendors combine several collection techniques: crawling public web assets and partner badges, scanning DNS records and TLS certificates, and reading hiring signals from job postings. Each detection carries a confidence score and a timestamp, and change-detection pipelines compare successive snapshots to emit adoption and abandonment events rather than raw states.
Who uses it
Software equity analysts, GTM teams and VC read stack changes as churn, migration and investment signals.
Questions to ask vendors in this category
What mix of detection methods do you use? What is the false-positive rate? How precise are change events vs snapshots?
Complementary signals
This signal pairs naturally with adjacent categories of the encyclopedia:
Caveats and limitations
Detection coverage is uneven across stacks; web-only signals miss back-office software. History depth matters because change events, not stock levels, drive most of the alpha.
Compliance and legal considerations
Signals are derived from public web artifacts and job ads, so personal-data exposure is low. Buyers should still check scraping terms of service and ensure job-posting text is stripped of applicant names before use.