Berkshire Healthcare's tech stack
What does Berkshire Healthcare use?
Berkshire Healthcare (berkshirehealthcare.org) uses at least 12 tools we can see from public records, including WP Engine for hosting, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Pittsfield, United States
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Berkshire Healthcare'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
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
7 tools, how they find and keep customers
Website & CMS
Marketing
Berkshire Healthcare tech stack FAQ
What tools does Berkshire Healthcare use?
We've found 12 tools at Berkshire Healthcare (berkshirehealthcare.org). Edge & Hosting: Cloudflare and WP Engine. Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Last checked October 3, 2026.
What cloud does Berkshire Healthcare run on?
Berkshire Healthcare uses WP Engine for hosting. We found WP Engine through website code.
What analytics tools does Berkshire Healthcare use?
Berkshire Healthcare uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Berkshire Healthcare use?
Berkshire Healthcare uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Berkshire Healthcare use Cloudflare?
Yes. We found Cloudflare at Berkshire Healthcare through DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Berkshire Healthcare uses?
We read public traces only: Berkshire Healthcare'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.