runsonwhat

run.events's tech stack

What does run.events use?

run.events (run.events) uses at least 23 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, HubSpot for sales and Google Analytics for analytics. Last checked .

“The platform is fully EU-hosted and operated jointly by run.events GmbH (Germany) and run.events OÜ (Estonia).”

Industry
Software
Size
11–50 employees
Based in
Bingen, Germany
Founded
2015
LinkedIn
Company page
Re-check liveVisit run.events
Tools found
23
Categories
12
Layers
5 of 5
Last checked
Oct 2026

run.events'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

CDN & Edge

Application

4 tools, what the product is built with

Frontend

AI

Media & UI

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

10 tools, how they find and keep customers

Marketing

Ads & Pixels

Sales & CRM

Company Ops

4 tools, what the team runs on day to day

Workspace

Dev Tools

Security & Compliance

Companies like run.events also use

Tools common among companies with a similar stack that we haven't found at run.events.

Companies with a stack like run.events's

Ranked by shared tools, with rare tools counting more.

More Software companies

Other Software companies we've checked.

run.events tech stack FAQ

What tools does run.events use?

As of October 2026, runsonwhat has found 23 tools at run.events (run.events) in public records. Edge & Hosting: Cloudflare and Microsoft Azure. Application: Font Awesome, Tailwind CSS and Astro. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Meta Pixel and LinkedIn Insight Tag. Company Ops: Microsoft 365, Cloudflare Turnstile and Termly. Last checked October 21, 2026.

What cloud does run.events run on?

run.events uses Microsoft Azure for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Microsoft Azure through a subdomain that points at Microsoft Azure and DNS records. Microsoft Azure is used by 46,656 companies runsonwhat tracks.

What CRM does run.events use?

run.events uses HubSpot for its CRM, alongside HighLevel, Pipedrive and Apollo.io, according to runsonwhat (October 2026). runsonwhat found HubSpot through HubSpot code on run.events. HubSpot is used by 93,824 companies runsonwhat tracks.

What email provider does run.events use?

run.events uses Microsoft 365 for email and office software, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through email records that authorize Microsoft 365 and code on run.events. Microsoft 365 is used by 710,114 companies runsonwhat tracks.

What analytics tools does run.events use?

run.events uses Google Analytics for analytics, alongside Google Tag Manager and Microsoft Clarity, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on run.events. Google Analytics is used by 877,699 companies runsonwhat tracks.

Does run.events use Cloudflare?

Yes. runsonwhat found Cloudflare at run.events through Cloudflare code on run.events. Cloudflare is a CDN & Edge tool used by 702,317 companies runsonwhat tracks.

Which companies have a tech stack similar to run.events's?

The companies with the stacks most like run.events' are ToucanTech, deBCor Industries, Nomadis and Physis Informática, according to runsonwhat (October 2026). Each shares 7 to 11 tools with run.events, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what run.events uses?

runsonwhat reads public records only. Of the 23 tools at run.events, 18 were found through code on run.events, 2 through DNS records, 1 through email records, 1 through website configuration files and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and run.events about 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.