TAMI Industries's tech stack
What does TAMI Industries use?
TAMI Industries (tami-industries.com) uses at least 7 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Mechanical or Industrial Engineering
- Size
- 11–50 employees
- Based in
- Les Laurons, France
- Founded
- 1993
- Company page
- Tools found
- 7
- Categories
- 5
- Layers
- 4 of 5
- Last checked
- Oct 2026
TAMI Industries'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.
Application
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Workspace
TAMI Industries tech stack FAQ
What tools does TAMI Industries use?
We've found 7 tools at TAMI Industries (tami-industries.com). Application: jQuery. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365. Last checked October 3, 2026.
What email provider does TAMI Industries use?
TAMI Industries uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does TAMI Industries use?
TAMI Industries uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does TAMI Industries use?
TAMI Industries uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does TAMI Industries use Microsoft 365?
Yes. We found Microsoft 365 at TAMI Industries through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what TAMI Industries uses?
We read public traces only: TAMI Industries'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.