become.co.jp's tech stack
What does become.co.jp use?
become.co.jp (become.co.jp) uses at least 22 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Cloudflare for content delivery and Amazon SES for email delivery. Last checked .
- Based in
- Japan
- Founded
- 2005
- Tools found
- 22
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
become.co.jp'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
3 tools, what they measure and store
Go-to-market
11 tools, how they find and keep customers
Company Ops
6 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
become.co.jp tech stack FAQ
What tools does become.co.jp use?
We've found 22 tools at become.co.jp (become.co.jp). Edge & Hosting: Cloudflare. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Microsoft Ads and Google Ad Manager. Company Ops: Google Workspace, Amazon SES and Let's Encrypt. Last checked October 3, 2026.
What email provider does become.co.jp use?
become.co.jp uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does become.co.jp use?
become.co.jp uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does become.co.jp use Cloudflare?
Yes. We found Cloudflare at become.co.jp through email records, DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what become.co.jp uses?
We read public traces only: become.co.jp'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.