thinkRED's tech stack
What does thinkRED use?
thinkRED (thinkred.de) uses at least 13 tools we can see from public records, including IONOS for hosting, Microsoft 365 for email and documents, Matomo for analytics and WordPress for its website. Last checked .
- Industry
- IT Services
- Size
- 51–200 employees
- Based in
- Bochum, Germany
- Company page
- Tools found
- 13
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
thinkRED'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
1 tool, where the bytes are served from
Hosting & Cloud
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
5 tools, what the team runs on day to day
Workspace
Dev Tools
Security & Compliance
thinkRED tech stack FAQ
What tools does thinkRED use?
We've found 13 tools at thinkRED (thinkred.de). Edge & Hosting: IONOS. Application: jQuery, YouTube and Vimeo. Data & Observability: Matomo. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 7, 2026.
What cloud does thinkRED run on?
thinkRED uses IONOS for hosting. We found IONOS through website code.
What email provider does thinkRED use?
thinkRED uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does thinkRED use?
thinkRED uses Matomo for analytics. We found Matomo through website code.
What CMS does thinkRED use?
thinkRED uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does thinkRED use jQuery?
Yes. We found jQuery at thinkRED through website code. jQuery is used by 761,740 companies we track.
How does runsonwhat know what thinkRED uses?
We read public traces only: thinkRED'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.