CARITAS's tech stack
What does CARITAS use?
CARITAS (caritas.ua) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Non-profit Organization Management
- Size
- 1,001–5,000 employees
- Based in
- Lviv, Ukraine
- Founded
- 1991
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
CARITAS'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
4 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Analytics
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
CARITAS tech stack FAQ
What tools does CARITAS use?
We've found 14 tools at CARITAS (caritas.ua). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Matomo. Go-to-market: WordPress, Meta Pixel and Yoast SEO. Company Ops: Microsoft 365, reCAPTCHA and Cloudflare Turnstile. Last checked October 7, 2026.
What email provider does CARITAS use?
CARITAS uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.
What analytics tools does CARITAS use?
CARITAS uses Google Analytics and Matomo for analytics. We found Google Analytics through website code.
What CMS does CARITAS use?
CARITAS uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does CARITAS use Microsoft 365?
Yes. We found Microsoft 365 at CARITAS through email records and website code. Microsoft 365 is used by 685,700 companies we track.
How does runsonwhat know what CARITAS uses?
We read public traces only: CARITAS'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.