Lexical Computing's tech stack
What does Lexical Computing use?
Lexical Computing (lexicalcomputing.com) uses at least 13 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
- Industry
- Corpus Linguistics
- Size
- 11–50 employees
- Based in
- Stránice, Czechia
- Founded
- 2011
- Company page
- Tools found
- 13
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Lexical Computing's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Application
5 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
Lexical Computing tech stack FAQ
What tools does Lexical Computing use?
We've found 13 tools at Lexical Computing (lexicalcomputing.com). Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: reCAPTCHA and Cookiebot. Last checked October 3, 2026.
What analytics tools does Lexical Computing use?
Lexical Computing uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Lexical Computing use?
Lexical Computing uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Lexical Computing use jQuery?
Yes. We found jQuery at Lexical Computing through website code. jQuery is used by 576,040 companies we track.
How does runsonwhat know what Lexical Computing uses?
We read public traces only: Lexical Computing's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.