Edtech companies and the stack detection problem

The problem

Edtech companies distort stack detection, for a reason specific to them. Edtech companies sell to institutions on an academic calendar, so the buying window opens twice a year and closes hard, and stack detection has to work around it. Worth knowing about edtech companies, since stack detection inherits it: term dates move the whole pipeline, so a signal read in July means something else in October. There is 1 runnable example of stack detection for edtech companies below.

Traditional Search Tools

• The institution's own procurement portal, for edtech companies. Free, slow, and the only place a tender actually appears.
• BuiltWith. The reference dataset with history and reverse lookup by technology. Priced accordingly, and still the first place most people go.
• Wappalyzer. Free as an extension, cheap as an API, shallower than BuiltWith on history. Fine for a live check on a single account.
• Their integrations page. Companies list what they connect to. It is self reported, public, and frequently more accurate than any detector.
• View source and check the DNS. Script tags, DNS records, the login subdomain. A minute per company for someone who knows what to look for, and the signatures are public.

Doing it end to end

1. Start with one of edtech companies you already know, so a wrong stack detection answer is obvious rather than plausible.
2. Run Company Tech Stack Detection across your list of edtech companies, which carries 1 ready made setup for stack detection.
3. Read ten rows of stack detection on edtech companies by hand before you trust the rest of the list.

Mamba Labs Apify Actors

These are the actors we built for this job. If yours is not covered here, search from the bar at the top of the page or contact us here and tell us what you need.

• Company Tech Stack Detection1 preconfigured task on this page's job.