runsonwhat

FrogData's tech stack

What does FrogData use?

FrogData (frogdata.com) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, tawk.to for customer support, Google Analytics for analytics and Cloudflare for content delivery. Last checked .

Industry
Software
Size
201–1,000 employees
Based in
San Francisco, United States
LinkedIn
Company page
Tools found
15
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

2 tools, where the bytes are served from

Application

4 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

1 tool, what the team runs on day to day

FrogData tech stack FAQ

What tools does FrogData use?

We've found 15 tools at FrogData (frogdata.com). Edge & Hosting: Cloudflare and GoDaddy. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Meta Pixel and LinkedIn Insight Tag. Company Ops: Microsoft 365. Last checked October 7, 2026.

What email provider does FrogData use?

FrogData uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.

What does FrogData use for customer support?

FrogData uses tawk.to for customer support. We found tawk.to through website code.

What analytics tools does FrogData use?

FrogData uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

Does FrogData use jQuery?

Yes. We found jQuery at FrogData through website code. jQuery is used by 761,706 companies we track.

How does runsonwhat know what FrogData uses?

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