The Marketing Arm's tech stack
What does The Marketing Arm use?
The Marketing Arm (themarketingarm.com) uses at least 14 tools we can see from public records, including IBM Cloud for hosting, Microsoft 365 for email and documents, Emma for marketing and Greenhouse for hiring and HR. Last checked .
- Industry
- Marketing
- Founded
- 1992
- Tools found
- 14
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
The Marketing Arm'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
Hosting & Cloud
Application
1 tool, what the product is built with
Go-to-market
2 tools, how they find and keep customers
Marketing
Company Ops
10 tools, what the team runs on day to day
Email Delivery
Workspace
Collaboration
Dev Tools
People & HR
Security & Compliance
The Marketing Arm tech stack FAQ
What tools does The Marketing Arm use?
We've found 14 tools at The Marketing Arm (themarketingarm.com). Edge & Hosting: IBM Cloud. Application: OpenAI. Go-to-market: Emma. Company Ops: Microsoft 365, Atlassian and Mailgun. Last checked October 3, 2026.
What cloud does The Marketing Arm run on?
The Marketing Arm uses IBM Cloud for hosting. We found IBM Cloud through DNS verification records.
What email provider does The Marketing Arm use?
The Marketing Arm uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What marketing software does The Marketing Arm use?
The Marketing Arm uses Emma for marketing. We found Emma through email records.
What does The Marketing Arm use for hiring and HR?
The Marketing Arm uses Greenhouse for hiring and HR. We found Greenhouse through email records.
Does The Marketing Arm use Microsoft 365?
Yes. We found Microsoft 365 at The Marketing Arm through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what The Marketing Arm uses?
We read public traces only: The Marketing Arm'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.