South Orange & Maplewood School District's tech stack
What does South Orange & Maplewood School District use?
South Orange & Maplewood School District (somsdk12.org) uses at least 8 tools we can see from public records, including Google Analytics for analytics, Cloudflare for content delivery and Termly for security. Last checked .
- Industry
- Education Management
- Size
- 1,001–5,000 employees
- Based in
- Maplewood, United States
- Founded
- 1814
- Company page
- Tools found
- 8
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
South Orange & Maplewood School District'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
2 tools, what the product is built with
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
South Orange & Maplewood School District tech stack FAQ
What tools does South Orange & Maplewood School District use?
We've found 8 tools at South Orange & Maplewood School District (somsdk12.org). Edge & Hosting: Cloudflare. Application: Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Termly. Last checked October 3, 2026.
What analytics tools does South Orange & Maplewood School District use?
South Orange & Maplewood School District uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does South Orange & Maplewood School District use Cloudflare?
Yes. We found Cloudflare at South Orange & Maplewood School District through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what South Orange & Maplewood School District uses?
We read public traces only: South Orange & Maplewood School District'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.