runsonwhat

The Cultural Institutions Retirement System (CIRS)'s tech stack

What does The Cultural Institutions Retirement System (CIRS) use?

The Cultural Institutions Retirement System (CIRS) (cirsplans.org) uses at least 16 tools we can see from public records, including WP Engine for hosting, Calendly for sales, KnowBe4 for security and Microsoft 365 for email and documents. Last checked .

Industry
Civic & Social Organization
Size
11–50 employees
Based in
New York, United States
Founded
1962
LinkedIn
Company page
Tools found
16
Categories
9
Layers
5 of 5
Last checked
Nov 2026

The Cultural Institutions Retirement System (CIRS)'s stack, layer by layer

Of 16 tools, 12 came from website code, 3 from email records and 1 from DNS verification records. 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

Hosting & Cloud

Application

6 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Email Delivery

The Cultural Institutions Retirement System (CIRS) tech stack FAQ

What tools does The Cultural Institutions Retirement System (CIRS) use?

As of November 2026, runsonwhat has found 16 tools at The Cultural Institutions Retirement System (CIRS) (cirsplans.org) in public records. Edge & Hosting: WP Engine. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress, Yoast SEO and Calendly. Company Ops: Microsoft 365, reCAPTCHA and SendGrid. Last checked November 14, 2026.

What cloud does The Cultural Institutions Retirement System (CIRS) run on?

The Cultural Institutions Retirement System (CIRS) uses WP Engine for hosting and cloud infrastructure, according to runsonwhat (November 2026). runsonwhat found WP Engine through WP Engine code on cirsplans.org. WP Engine is used by 52,526 companies runsonwhat tracks.

What sales tools does The Cultural Institutions Retirement System (CIRS) use?

The sales tools runsonwhat has found at The Cultural Institutions Retirement System (CIRS) are Calendly (November 2026); no CRM shows up in The Cultural Institutions Retirement System (CIRS)'s public records. runsonwhat found Calendly through Calendly code on cirsplans.org. Calendly is used by 31,576 companies runsonwhat tracks.

What email provider does The Cultural Institutions Retirement System (CIRS) use?

The Cultural Institutions Retirement System (CIRS) uses Microsoft 365 for email and office software, according to runsonwhat (November 2026). runsonwhat found Microsoft 365 through email records that authorize Microsoft 365 and a DNS verification record. Microsoft 365 is used by 741,605 companies runsonwhat tracks.

What analytics tools does The Cultural Institutions Retirement System (CIRS) use?

The Cultural Institutions Retirement System (CIRS) uses Google Analytics for analytics, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on cirsplans.org. Google Analytics is used by 903,946 companies runsonwhat tracks.

What is The Cultural Institutions Retirement System (CIRS)'s website built with?

The Cultural Institutions Retirement System (CIRS) uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (November 2026). runsonwhat found WordPress through WordPress code on cirsplans.org. WordPress is used by 607,527 companies runsonwhat tracks.

Does The Cultural Institutions Retirement System (CIRS) use jQuery?

Yes. runsonwhat found jQuery at The Cultural Institutions Retirement System (CIRS) through jQuery code on cirsplans.org. jQuery is a Frontend tool used by 925,580 companies runsonwhat tracks.

How does runsonwhat know what The Cultural Institutions Retirement System (CIRS) uses?

runsonwhat reads public records only. Of the 16 tools at The Cultural Institutions Retirement System (CIRS), 12 were found through code on cirsplans.org, 3 through email records and 1 through DNS records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and cirsplans.org about 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.