Merlot's tech stack
What does Merlot use?
Merlot (merlot.org) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Amazon SES for email delivery. Last checked .
- Industry
- E-learning
- Size
- 10,000+ employees
- Based in
- Long Beach, United States
- Founded
- 1997
- Company page
- Tools found
- 9
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Merlot'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
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Website & CMS
Company Ops
3 tools, what the team runs on day to day
Merlot tech stack FAQ
What tools does Merlot use?
We've found 9 tools at Merlot (merlot.org). Edge & Hosting: Amazon Route 53. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Microsoft 365, Amazon SES and Proofpoint. Last checked October 3, 2026.
What email provider does Merlot use?
Merlot uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Merlot use?
Merlot uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Merlot use?
Merlot uses WordPress for its website. We found WordPress through custom domain.
Does Merlot use Microsoft 365?
Yes. We found Microsoft 365 at Merlot through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Merlot uses?
We read public traces only: Merlot'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.