Maple Leaf Schools's tech stack
What does Maple Leaf Schools use?
Maple Leaf Schools (mapleleafschools.com) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, web-vitals for monitoring and Cloudflare for content delivery. Last checked .
- Industry
- Primary/secondary Education
- Size
- 201–1,000 employees
- Based in
- Shenzhen, China
- Founded
- 1995
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Maple Leaf Schools'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
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
Maple Leaf Schools tech stack FAQ
What tools does Maple Leaf Schools use?
We've found 9 tools at Maple Leaf Schools (mapleleafschools.com). Edge & Hosting: Cloudflare. Application: Google Fonts, React and Tailwind CSS. Data & Observability: Google Analytics, web-vitals and Tinybird. Company Ops: Google Workspace. Last checked October 8, 2026.
What email provider does Maple Leaf Schools use?
Maple Leaf Schools uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What analytics tools does Maple Leaf Schools use?
Maple Leaf Schools uses Google Analytics and Tinybird for analytics. We found Google Analytics through website code.
Does Maple Leaf Schools use Google Analytics?
Yes. We found Google Analytics at Maple Leaf Schools through website code. Google Analytics is used by 729,031 companies we track.
How does runsonwhat know what Maple Leaf Schools uses?
We read public traces only: Maple Leaf Schools'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.