Wikimedia Enterprise's tech stack
What does Wikimedia Enterprise use?
Wikimedia Enterprise (wikimedia.com) uses at least 8 tools we can see from public records, including Zendesk for customer support, Fathom for analytics, Amazon CloudFront for content delivery and Amazon SES for email delivery. Last checked .
“Wikimedia Enterprise provides fast, reliable access to Wikimedia data through APIs built for business.”
- Industry
- Marketing and Advertising
- Size
- 11–50 employees
- Based in
- United States
- Founded
- 2020
- Company page
- Tools found
- 8
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Wikimedia Enterprise'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
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
1 tool, what the team runs on day to day
Email Delivery
Wikimedia Enterprise tech stack FAQ
What tools does Wikimedia Enterprise use?
We've found 8 tools at Wikimedia Enterprise (wikimedia.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Astro. Data & Observability: Fathom. Go-to-market: Zendesk. Company Ops: Amazon SES. Last checked October 3, 2026.
What does Wikimedia Enterprise use for customer support?
Wikimedia Enterprise uses Zendesk for customer support. We found Zendesk through email records.
What analytics tools does Wikimedia Enterprise use?
Wikimedia Enterprise uses Fathom for analytics. We found Fathom through website code.
Does Wikimedia Enterprise use Amazon Route 53?
Yes. We found Amazon Route 53 at Wikimedia Enterprise through DNS records. Amazon Route 53 is used by 37,434 companies we track.
How does runsonwhat know what Wikimedia Enterprise uses?
We read public traces only: Wikimedia Enterprise'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.