runsonwhat

リンレイ's tech stack

What does リンレイ use?

リンレイ (rinrei.co.jp) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Pardot for marketing. Last checked .

Based in
Japan
Founded
1944
Tools found
12
Categories
8
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.

Edge & Hosting

1 tool, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

リンレイ tech stack FAQ

What tools does リンレイ use?

We've found 12 tools at リンレイ (rinrei.co.jp). Edge & Hosting: Cloudflare. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: Microsoft 365 and GlobalSign. Last checked October 3, 2026.

What email provider does リンレイ use?

リンレイ uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does リンレイ use?

リンレイ uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What CMS does リンレイ use?

リンレイ uses WordPress for its website. We found WordPress through website code.

What marketing software does リンレイ use?

リンレイ uses Pardot for marketing. We found Pardot through DNS verification records, email records and website code.

Does リンレイ use Microsoft 365?

Yes. We found Microsoft 365 at リンレイ through DNS verification records and email records. Microsoft 365 is used by 320,201 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.