Concurrent's tech stack
What does Concurrent use?
Concurrent (concurrent.tech) uses at least 14 tools we can see from public records, including Netlify for hosting, Google Analytics for analytics and Storyblok for its website. Last checked .
- Industry
- Computer Hardware
- Size
- 51–200 employees
- Based in
- Colchester, United Kingdom
- Founded
- 1985
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
Concurrent'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.
Edge & Hosting
2 tools, where the bytes are served from
Hosting & Cloud
DNS
Application
5 tools, what the product is built with
Search
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Concurrent tech stack FAQ
What tools does Concurrent use?
We've found 14 tools at Concurrent (concurrent.tech). Edge & Hosting: GoDaddy and Netlify. Application: React, Adobe Fonts and Tailwind CSS. Data & Observability: Google Analytics, Plausible and Mouseflow. Go-to-market: Google Ads, LinkedIn Insight Tag and Storyblok. Last checked October 7, 2026.
What cloud does Concurrent run on?
Concurrent uses Netlify for hosting. We found Netlify through custom domain, DNS records and website code.
What analytics tools does Concurrent use?
Concurrent uses Google Analytics, Plausible and Mouseflow for analytics. We found Google Analytics through website code.
What CMS does Concurrent use?
Concurrent uses Storyblok for its website. We found Storyblok through website code.
Does Concurrent use Google Analytics?
Yes. We found Google Analytics at Concurrent through website code. Google Analytics is used by 560,920 companies we track.
How does runsonwhat know what Concurrent uses?
We read public traces only: Concurrent'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.