runsonwhat

BetaMed S.A.'s tech stack

What does BetaMed S.A. use?

BetaMed S.A. (betamed.pl) uses at least 16 tools we can see from public records, including tawk.to for customer support, Google Analytics for analytics, WordPress for its website and Sectigo for security. Last checked .

Industry
Healthcare
Size
1,001–5,000 employees
Based in
Chorzów, Poland
Founded
2001
LinkedIn
Company page
Tools found
16
Categories
7
Layers
4 of 5
Last checked
Oct 2026

BetaMed S.A.'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.

Application

6 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

BetaMed S.A. tech stack FAQ

What tools does BetaMed S.A. use?

We've found 16 tools at BetaMed S.A. (betamed.pl). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Sectigo and Cookiebot. Last checked October 3, 2026.

What does BetaMed S.A. use for customer support?

BetaMed S.A. uses tawk.to for customer support. We found tawk.to through website code.

What analytics tools does BetaMed S.A. use?

BetaMed S.A. uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

What CMS does BetaMed S.A. use?

BetaMed S.A. uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does BetaMed S.A. use Google Analytics?

Yes. We found Google Analytics at BetaMed S.A. through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what BetaMed S.A. uses?

We read public traces only: BetaMed S.A.'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.