MarkSupply's tech stack
What does MarkSupply use?
MarkSupply (creativemarket.com) uses at least 13 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Apollo.io for sales and Zendesk for customer support. Last checked .
“Marketplace for graphic design assets”
- Industry
- Digital Distribution
- Based in
- San Francisco, Germany
- Founded
- 2020
- Tools found
- 13
- Categories
- 8
- Layers
- 3 of 5
- Last checked
- Oct 2026
MarkSupply'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
4 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Go-to-market
3 tools, how they find and keep customers
Company Ops
6 tools, what the team runs on day to day
Email Delivery
Security & Compliance
MarkSupply tech stack FAQ
What tools does MarkSupply use?
We've found 13 tools at MarkSupply (creativemarket.com). Edge & Hosting: Cloudflare, Amazon CloudFront and Amazon Web Services. Go-to-market: Zendesk and Apollo.io. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 2, 2026.
What cloud does MarkSupply run on?
MarkSupply uses Amazon Web Services and Kinsta for hosting. We found Amazon Web Services through custom domain.
What CRM does MarkSupply use?
MarkSupply uses Apollo.io for sales and CRM. We found Apollo.io through custom domain.
What email provider does MarkSupply use?
MarkSupply uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What does MarkSupply use for customer support?
MarkSupply uses Zendesk for customer support. We found Zendesk through email records.
Does MarkSupply use Microsoft 365?
Yes. We found Microsoft 365 at MarkSupply through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what MarkSupply uses?
We read public traces only: MarkSupply'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.