runsonwhat

HelloSafe's tech stack

What does HelloSafe use?

HelloSafe (hellosafe.com) uses at least 16 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Stripe for payments and Cloudflare for content delivery. Last checked .

Industry
Insurance Intermediation
Based in
France
Founded
2020
LinkedIn
Company page
Tools found
16
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

5 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

HelloSafe tech stack FAQ

What tools does HelloSafe use?

We've found 16 tools at HelloSafe (hellosafe.com). Edge & Hosting: Cloudflare. Application: React, Tailwind CSS and Next.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Microsoft Ads and Awin. Company Ops: Google Workspace, Amazon SES and Mailjet. Last checked October 4, 2026.

What email provider does HelloSafe use?

HelloSafe uses Google Workspace for email and documents. We found Google Workspace through email records and website code.

What payment provider does HelloSafe use?

HelloSafe uses Stripe for payments. We found Stripe through DNS verification records and website code.

What analytics tools does HelloSafe use?

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

Does HelloSafe use Cloudflare?

Yes. We found Cloudflare at HelloSafe through DNS records and website code. Cloudflare is used by 464,890 companies we track.

How does runsonwhat know what HelloSafe uses?

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