runsonwhat

Amuse's tech stack

What does Amuse use?

Amuse (amuse.co.jp) uses at least 17 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .

Industry
Tertiary Sector of the Economy
Size
201–1,000 employees
Based in
Japan
Founded
1977
LinkedIn
Company page
Tools found
17
Categories
11
Layers
5 of 5
Last checked
Oct 2026

Amuse'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

3 tools, where the bytes are served from

Application

4 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Amuse tech stack FAQ

What tools does Amuse use?

We've found 17 tools at Amuse (amuse.co.jp). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: jQuery, GSAP and Adobe Fonts. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads. Company Ops: Google Workspace, SendGrid and Amazon SES. Last checked October 2, 2026.

What cloud does Amuse run on?

Amuse uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What email provider does Amuse use?

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

What analytics tools does Amuse use?

Amuse uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

Does Amuse use Cloudflare?

Yes. We found Cloudflare at Amuse through custom domain and website code. Cloudflare is used by 311,171 companies we track.

How does runsonwhat know what Amuse uses?

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