runsonwhat

造咖's tech stack

What does 造咖 use?

造咖 (cava.tw) uses at least 44 tools we can see from public records, including Amazon Web Services for hosting, Demandbase for sales, Google Analytics for analytics and Cloudflare for content delivery. Last checked .

Based in
Taiwan
Tools found
44
Categories
10
Layers
5 of 5
Last checked
Oct 2026

造咖'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.

造咖 tech stack FAQ

What tools does 造咖 use?

As of October 2026, runsonwhat has found 44 tools at 造咖 (cava.tw) in public records. Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics, Google Tag Manager and comScore. Go-to-market: Google Ads, Meta Pixel and LinkedIn Insight Tag. Company Ops: reCAPTCHA. Last checked October 20, 2026.

What cloud does 造咖 run on?

造咖 uses Amazon Web Services for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Amazon Web Services through Amazon Web Services code on cava.tw. Amazon Web Services is used by 146,164 companies runsonwhat tracks.

What sales tools does 造咖 use?

The sales tools runsonwhat has found at 造咖 are Demandbase (October 2026); no CRM shows up in 造咖's public records. runsonwhat found Demandbase through Demandbase code on cava.tw. Demandbase is used by 9,704 companies runsonwhat tracks.

What analytics tools does 造咖 use?

造咖 uses Google Analytics for analytics, alongside Google Tag Manager and comScore, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on cava.tw. Google Analytics is used by 895,479 companies runsonwhat tracks.

Does 造咖 use jQuery?

Yes. runsonwhat found jQuery at 造咖 through jQuery code on cava.tw. jQuery is a Frontend tool used by 923,756 companies runsonwhat tracks.

How does runsonwhat know what 造咖 uses?

runsonwhat reads public records only. Of the 44 tools at 造咖, 28 were found through code on cava.tw, 14 through website configuration files and 2 through DNS records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and cava.tw 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.