Sawanotsuru's tech stack
What does Sawanotsuru use?
Sawanotsuru (sawanotsuru.co.jp) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and New Relic for monitoring. Last checked .
- Based in
- Japan
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Sawanotsuru'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
Sawanotsuru tech stack FAQ
What tools does Sawanotsuru use?
We've found 10 tools at Sawanotsuru (sawanotsuru.co.jp). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and New Relic. Go-to-market: WordPress and Google Ads. Company Ops: Microsoft 365. Last checked October 3, 2026.
What email provider does Sawanotsuru use?
Sawanotsuru uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Sawanotsuru use?
Sawanotsuru uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Sawanotsuru use?
Sawanotsuru uses WordPress for its website. We found WordPress through website code.
Does Sawanotsuru use Microsoft 365?
Yes. We found Microsoft 365 at Sawanotsuru through DNS verification records and email records. Microsoft 365 is used by 319,377 companies we track.
How does runsonwhat know what Sawanotsuru uses?
We read public traces only: Sawanotsuru'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.