Chilli Fruit's tech stack
What does Chilli Fruit use?
Chilli Fruit (chillifruit.com) uses at least 10 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
- Internet
- Size
- 1–10 employees
- Based in
- London, United Kingdom
- Founded
- 2013
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Chilli Fruit'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
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Chilli Fruit tech stack FAQ
What tools does Chilli Fruit use?
We've found 10 tools at Chilli Fruit (chillifruit.com). Edge & Hosting: Cloudflare. Application: jQuery, Vimeo and Lottie. Data & Observability: Google Analytics. Go-to-market: WordPress and Rank Math. Company Ops: Google Workspace and CookieYes. Last checked October 4, 2026.
What email provider does Chilli Fruit use?
Chilli Fruit uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Chilli Fruit use?
Chilli Fruit uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Chilli Fruit use?
Chilli Fruit uses WordPress and Rank Math for its website. We found WordPress through website code.
Does Chilli Fruit use Cloudflare?
Yes. We found Cloudflare at Chilli Fruit through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Chilli Fruit uses?
We read public traces only: Chilli Fruit'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.