runsonwhat

System Sensor's tech stack

What does System Sensor use?

System Sensor (systemsensor.com) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Marketo for marketing, Akamai mPulse for monitoring and Cloudflare for content delivery. Last checked .

Industry
Industrial Manufacturing
Size
201–1,000 employees
Based in
St. Charles, United States
Founded
1984
LinkedIn
Company page
Tools found
12
Categories
10
Layers
5 of 5
Last checked
Oct 2026

System Sensor'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

Application

1 tool, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Collaboration

Dev Tools

Finance & Legal

Security & Compliance

System Sensor tech stack FAQ

What tools does System Sensor use?

We've found 12 tools at System Sensor (systemsensor.com). Edge & Hosting: Cloudflare and Akamai. Application: Vimeo. Data & Observability: Adobe Experience Platform Tags and Akamai mPulse. Go-to-market: Marketo. Company Ops: Microsoft 365, Atlassian and DocuSign. Last checked October 3, 2026.

What email provider does System Sensor use?

System Sensor uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and DNS verification records.

What marketing software does System Sensor use?

System Sensor uses Marketo for marketing. We found Marketo through custom domain, email records and website code.

Does System Sensor use Microsoft 365?

Yes. We found Microsoft 365 at System Sensor through email records and DNS verification records. Microsoft 365 is used by 375,038 companies we track.

How does runsonwhat know what System Sensor uses?

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