runsonwhat

JPServis's tech stack

What does JPServis use?

JPServis (jpservis.com) 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 ActiveCampaign for marketing. Last checked .

Industry
Retail
Size
1–10 employees
Based in
Chodov, Czechia
Founded
2001
LinkedIn
Company page
Tools found
14
Categories
9
Layers
4 of 5
Last checked
Oct 2026

JPServis'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

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Email Delivery

JPServis tech stack FAQ

What tools does JPServis use?

We've found 14 tools at JPServis (jpservis.com). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: Meta Pixel, WordPress and Yoast SEO. Company Ops: Microsoft 365, reCAPTCHA and SparkPost. Last checked October 3, 2026.

What email provider does JPServis use?

JPServis uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does JPServis use?

JPServis uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does JPServis use?

JPServis uses WordPress and Yoast SEO for its website. We found WordPress through website code.

What marketing software does JPServis use?

JPServis uses ActiveCampaign for marketing. We found ActiveCampaign through website code.

Does JPServis use Microsoft 365?

Yes. We found Microsoft 365 at JPServis through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what JPServis uses?

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