ルビコン株式会社's tech stack
What does ルビコン株式会社 use?
ルビコン株式会社 (rubycon.co.jp) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Seculio for security. Last checked .
- Industry
- Electronics
- Size
- 201–1,000 employees
- Based in
- ルビコン 株式会社, Japan
- Founded
- 1952
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 4 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.
Application
3 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
ルビコン株式会社 tech stack FAQ
What tools does ルビコン株式会社 use?
We've found 11 tools at ルビコン株式会社 (rubycon.co.jp). Application: jQuery, Google Fonts and Anthropic. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Microsoft 365 and Seculio. Last checked October 2, 2026.
What email provider does ルビコン株式会社 use?
ルビコン株式会社 uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does ルビコン株式会社 use?
ルビコン株式会社 uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does ルビコン株式会社 use?
ルビコン株式会社 uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does ルビコン株式会社 use Microsoft 365?
Yes. We found Microsoft 365 at ルビコン株式会社 through DNS verification records, email records and website code. Microsoft 365 is used by 685,126 companies we track.
How does runsonwhat know what ルビコン株式会社 uses?
We read public traces only: ルビコン株式会社'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.