runsonwhat

IAME KARTING's tech stack

What does IAME KARTING use?

IAME KARTING (iamekarting.com) uses at least 17 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

Size
1–10 employees
Based in
Zingonia, Italy
Founded
1968
LinkedIn
Company page
Tools found
17
Categories
8
Layers
5 of 5
Last checked
Oct 2026

IAME KARTING'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

CDN & Edge

Application

6 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

8 tools, what the team runs on day to day

IAME KARTING tech stack FAQ

What tools does IAME KARTING use?

We've found 17 tools at IAME KARTING (iamekarting.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Microsoft 365, Google Workspace and Let's Encrypt. Last checked October 3, 2026.

What email provider does IAME KARTING use?

IAME KARTING uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does IAME KARTING use?

IAME KARTING uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does IAME KARTING use?

IAME KARTING uses WordPress for its website. We found WordPress through website code.

Does IAME KARTING use Microsoft 365?

Yes. We found Microsoft 365 at IAME KARTING through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what IAME KARTING uses?

We read public traces only: IAME KARTING'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.