runsonwhat

CMD Engine's tech stack

What does CMD Engine use?

CMD Engine (cmdengine.com) uses at least 15 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 .

Industry
Metal Engineering
Based in
Italy
Founded
1971
LinkedIn
Company page
Tools found
15
Categories
9
Layers
5 of 5
Last checked
Oct 2026

CMD Engine'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

Application

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

CMD Engine tech stack FAQ

What tools does CMD Engine use?

We've found 15 tools at CMD Engine (cmdengine.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Yoast SEO and Microsoft Ads. Company Ops: Microsoft 365, reCAPTCHA and iubenda. Last checked October 3, 2026.

What email provider does CMD Engine use?

CMD Engine uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.

What analytics tools does CMD Engine use?

CMD Engine uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does CMD Engine use?

CMD Engine uses WordPress, Yoast SEO and Elementor for its website. We found WordPress through website code.

Does CMD Engine use Microsoft 365?

Yes. We found Microsoft 365 at CMD Engine through DNS verification records, email records and website code. Microsoft 365 is used by 590,348 companies we track.

How does runsonwhat know what CMD Engine uses?

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