runsonwhat

sweetFrog's tech stack

What does sweetFrog use?

sweetFrog (sweetfrog.com) uses at least 27 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, SendGrid for email delivery and Cookiebot for security. Last checked .

Industry
Retail Chain
Size
201–1,000 employees
Based in
Richmond, United States
Founded
2009
LinkedIn
Company page
Tools found
27
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

Application

6 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Security & Compliance

sweetFrog tech stack FAQ

What tools does sweetFrog use?

We've found 27 tools at sweetFrog (sweetfrog.com). Edge & Hosting: Amazon Route 53. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 3, 2026.

What email provider does sweetFrog use?

sweetFrog uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does sweetFrog use?

sweetFrog uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does sweetFrog use Microsoft 365?

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

How does runsonwhat know what sweetFrog uses?

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