Kimi's tech stack
What does Kimi use?
Kimi (kimi.pro) uses at least 8 tools we can see from public records, including Discord for customer support, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Industry
- Management Consulting
- Size
- 11–50 employees
- Based in
- Johannesburg, South Africa
- Founded
- 2017
- Company page
- Tools found
- 8
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Kimi'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
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Ads & Pixels
Support & Docs
Kimi tech stack FAQ
What tools does Kimi use?
As of October 2026, runsonwhat has found 8 tools at Kimi (kimi.pro) in public records. Edge & Hosting: Cloudflare. Application: Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Discord. Last checked October 23, 2026.
What does Kimi use for customer support?
Kimi uses Discord for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found Discord through Discord code on kimi.pro. Discord is used by 5,985 companies runsonwhat tracks.
What analytics tools does Kimi use?
Kimi uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on kimi.pro. Google Analytics is used by 887,848 companies runsonwhat tracks.
Does Kimi use Cloudflare?
Yes. runsonwhat found Cloudflare at Kimi through a subdomain that points at Cloudflare. Cloudflare is a CDN & Edge tool used by 707,539 companies runsonwhat tracks.
How does runsonwhat know what Kimi uses?
runsonwhat reads public records only. Of the 8 tools at Kimi, 6 were found through code on kimi.pro, 1 through DNS records and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and kimi.pro about 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.