runsonwhat

Concord Summer School's tech stack

What does Concord Summer School use?

Concord Summer School (concordsummer.com) uses at least 14 tools we can see from public records, including Google Analytics for analytics, WordPress for its website, Cloudflare for content delivery and Cookiebot for security. Last checked .

“Concord College's Summer School Program”

Industry
Education Management
Size
51–200 employees
Based in
Acton Burnell, United Kingdom
Founded
1949
LinkedIn
Company page
Tools found
14
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Concord Summer School'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

5 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Concord Summer School tech stack FAQ

What tools does Concord Summer School use?

We've found 14 tools at Concord Summer School (concordsummer.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Matomo. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: Cookiebot. Last checked October 6, 2026.

What analytics tools does Concord Summer School use?

Concord Summer School uses Google Analytics, Google Tag Manager and Matomo for analytics. We found Google Analytics through website code.

What CMS does Concord Summer School use?

Concord Summer School uses WordPress for its website. We found WordPress through website code.

Does Concord Summer School use jQuery?

Yes. We found jQuery at Concord Summer School through website code. jQuery is used by 577,729 companies we track.

How does runsonwhat know what Concord Summer School uses?

We read public traces only: Concord Summer School'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.