runsonwhat

建築に、温度を。 | 梓設計's tech stack

What does 建築に、温度を。 | 梓設計 use?

建築に、温度を。 | 梓設計 (azusasekkei.co.jp) uses at least 6 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents and Microsoft Clarity for analytics. Last checked .

Industry
Facilities Services
Size
1–10 employees
Based in
Setagaya, Japan
Founded
1946
LinkedIn
Company page
Tools found
6
Categories
6
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.

Edge & Hosting

1 tool, where the bytes are served from

Hosting & Cloud

Application

3 tools, what the product is built with

Frontend

Backend & Database

Data & Observability

1 tool, what they measure and store

Company Ops

1 tool, what the team runs on day to day

建築に、温度を。 | 梓設計 tech stack FAQ

What tools does 建築に、温度を。 | 梓設計 use?

We've found 6 tools at 建築に、温度を。 | 梓設計 (azusasekkei.co.jp). Edge & Hosting: Google Cloud. Application: Google Fonts, Firebase and Nuxt. Data & Observability: Microsoft Clarity. Company Ops: Google Workspace. Last checked October 3, 2026.

What cloud does 建築に、温度を。 | 梓設計 run on?

建築に、温度を。 | 梓設計 uses Google Cloud for hosting. We found Google Cloud through website code.

What email provider does 建築に、温度を。 | 梓設計 use?

建築に、温度を。 | 梓設計 uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does 建築に、温度を。 | 梓設計 use?

建築に、温度を。 | 梓設計 uses Microsoft Clarity for analytics. We found Microsoft Clarity through website code.

Does 建築に、温度を。 | 梓設計 use Google Workspace?

Yes. We found Google Workspace at 建築に、温度を。 | 梓設計 through email records. Google Workspace is used by 126,364 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.