Matrix Executions's tech stack
What does Matrix Executions use?
Matrix Executions (matrixexecutions.com) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Sentry for monitoring. Last checked .
- Industry
- Financial Services
- Size
- 51–200 employees
- Based in
- Chicago, United States
- Founded
- 2018
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Matrix Executions'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
4 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Workspace
Dev Tools
Matrix Executions tech stack FAQ
What tools does Matrix Executions use?
We've found 10 tools at Matrix Executions (matrixexecutions.com). Application: jQuery, Vimeo and Anthropic. Data & Observability: Google Analytics and Sentry. Go-to-market: WordPress and Elementor. Company Ops: Microsoft 365 and Atlassian. Last checked October 7, 2026.
What email provider does Matrix Executions use?
Matrix Executions uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.
What analytics tools does Matrix Executions use?
Matrix Executions uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Matrix Executions use?
Matrix Executions uses WordPress and Elementor for its website. We found WordPress through website code.
Does Matrix Executions use jQuery?
Yes. We found jQuery at Matrix Executions through website code. jQuery is used by 761,132 companies we track.
How does runsonwhat know what Matrix Executions uses?
We read public traces only: Matrix Executions'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.