runsonwhat

famyle's tech stack

What does famyle use?

famyle (famyle.com) uses at least 18 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Sentry for monitoring. Last checked .

Industry
Internet
Size
1–10 employees
Based in
São Carlos, Brazil
Founded
2020
LinkedIn
Company page
Tools found
18
Categories
12
Layers
5 of 5
Last checked
Oct 2026

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

Backend & Database

Media & UI

Data & Observability

5 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

famyle tech stack FAQ

What tools does famyle use?

We've found 18 tools at famyle (famyle.com). Edge & Hosting: Cloudflare and Fastly. Application: YouTube, Firebase and Angular. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Google Workspace and Mailchimp Transactional. Last checked October 4, 2026.

What email provider does famyle use?

famyle uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does famyle use?

famyle uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 4 tools in this category. We found Google Analytics through website code.

What CMS does famyle use?

famyle uses WordPress for its website. We found WordPress through website code.

Does famyle use Cloudflare?

Yes. We found Cloudflare at famyle through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what famyle uses?

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