TUM Hyperloop's tech stack
What does TUM Hyperloop use?
TUM Hyperloop (tumhyperloop.com) uses at least 14 tools we can see from public records, including STRATO for hosting, Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
- Industry
- Transportation/trucking/railroad
- Size
- 51–200 employees
- Based in
- Garching bei München, Germany
- Founded
- 2015
- Company page
- Tools found
- 14
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
TUM Hyperloop'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
6 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
TUM Hyperloop tech stack FAQ
What tools does TUM Hyperloop use?
We've found 14 tools at TUM Hyperloop (tumhyperloop.com). Edge & Hosting: STRATO. Application: jQuery, Font Awesome and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress, Elementor and Rank Math. Company Ops: reCAPTCHA and iubenda. Last checked October 7, 2026.
What cloud does TUM Hyperloop run on?
TUM Hyperloop uses STRATO for hosting. We found STRATO through website code.
What analytics tools does TUM Hyperloop use?
TUM Hyperloop uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does TUM Hyperloop use?
TUM Hyperloop uses WordPress, Elementor and Rank Math for its website. We found WordPress through website code.
Does TUM Hyperloop use jQuery?
Yes. We found jQuery at TUM Hyperloop through website code. jQuery is used by 762,159 companies we track.
How does runsonwhat know what TUM Hyperloop uses?
We read public traces only: TUM Hyperloop'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.