Familius's tech stack
What does Familius use?
Familius (familius.com) uses at least 14 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Publishing
- Size
- 1–10 employees
- Based in
- Sanger, United States
- Founded
- 2012
- Company page
- Tools found
- 14
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
Familius'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
CDN & Edge
Application
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Familius tech stack FAQ
What tools does Familius use?
We've found 14 tools at Familius (familius.com). Edge & Hosting: Cloudflare and GoDaddy. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: Meta Pixel, WordPress and Yoast SEO. Company Ops: Google Workspace and SendGrid. Last checked October 4, 2026.
What email provider does Familius use?
Familius uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Familius use?
Familius uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Familius use?
Familius uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.
Does Familius use Cloudflare?
Yes. We found Cloudflare at Familius through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Familius uses?
We read public traces only: Familius'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.