runsonwhat

$floki's tech stack

What does $floki use?

$floki (floki.com) uses at least 11 tools we can see from public records, including Google Workspace for email and documents, Discord for customer support, Google Analytics for analytics and Webflow for its website. Last checked .

Industry
Marketing and Advertising
Size
201–1,000 employees
Based in
Valhalla, United States
Founded
2021
LinkedIn
Company page
Tools found
11
Categories
10
Layers
5 of 5
Last checked
Oct 2026

$floki'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

2 tools, what the product is built with

Data & Observability

1 tool, 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

$floki tech stack FAQ

What tools does $floki use?

We've found 11 tools at $floki (floki.com). Edge & Hosting: Cloudflare and NS1. Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: Google Ads, Webflow and Discord. Company Ops: Google Workspace. Last checked October 5, 2026.

What email provider does $floki use?

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

What does $floki use for customer support?

$floki uses Discord and GitBook for customer support. We found Discord through website code.

What analytics tools does $floki use?

$floki uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does $floki use?

$floki uses Webflow for its website. We found Webflow through custom domain and website code.

Does $floki use jQuery?

Yes. We found jQuery at $floki through website code. jQuery is used by 583,843 companies we track.

How does runsonwhat know what $floki uses?

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