Bad Pyrmonter's tech stack
What does Bad Pyrmonter use?
Bad Pyrmonter (badpyrmonter.de) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and OpenAI for AI. Last checked .
- Size
- 1–10 employees
- Based in
- Bad Pyrmont, Germany
- Founded
- 1899
- Company page
- Tools found
- 10
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Bad Pyrmonter'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
2 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Bad Pyrmonter tech stack FAQ
What tools does Bad Pyrmonter use?
We've found 10 tools at Bad Pyrmonter (badpyrmonter.de). Application: jQuery and OpenAI. Data & Observability: Google Analytics and Plausible. Go-to-market: Google Ads, WordPress and Yoast SEO. Company Ops: Microsoft 365 and Apple Business. Last checked October 2, 2026.
What email provider does Bad Pyrmonter use?
Bad Pyrmonter uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records and DNS verification records.
What analytics tools does Bad Pyrmonter use?
Bad Pyrmonter uses Google Analytics and Plausible for analytics. We found Google Analytics through website code.
What CMS does Bad Pyrmonter use?
Bad Pyrmonter uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Bad Pyrmonter use Microsoft 365?
Yes. We found Microsoft 365 at Bad Pyrmonter through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Bad Pyrmonter uses?
We read public traces only: Bad Pyrmonter'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.