Oregon Cusd 220's tech stack
What does Oregon Cusd 220 use?
Oregon Cusd 220 (ocusd.net) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, web-vitals for monitoring and Fastly for content delivery. Last checked .
- Industry
- Primary/secondary Education
- Size
- 51–200 employees
- Based in
- Oregon, United States
- Company page
- Tools found
- 14
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Oregon Cusd 220'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
6 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Oregon Cusd 220 tech stack FAQ
What tools does Oregon Cusd 220 use?
We've found 14 tools at Oregon Cusd 220 (ocusd.net). Edge & Hosting: Fastly. Application: Google Fonts, GSAP and Tailwind CSS. Data & Observability: Google Analytics and web-vitals. Company Ops: Microsoft 365, Google Workspace and reCAPTCHA. Last checked October 8, 2026.
What email provider does Oregon Cusd 220 use?
Oregon Cusd 220 uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Oregon Cusd 220 use?
Oregon Cusd 220 uses Google Analytics for analytics. We found Google Analytics through website code.
Does Oregon Cusd 220 use Google Analytics?
Yes. We found Google Analytics at Oregon Cusd 220 through website code. Google Analytics is used by 724,666 companies we track.
How does runsonwhat know what Oregon Cusd 220 uses?
We read public traces only: Oregon Cusd 220'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.