runsonwhat

織本構造設計's tech stack

What does 織本構造設計 use?

織本構造設計 (orimoto.co.jp) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Based in
Japan
Tools found
10
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

2 tools, where the bytes are served from

Application

2 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

織本構造設計 tech stack FAQ

What tools does 織本構造設計 use?

We've found 10 tools at 織本構造設計 (orimoto.co.jp). Edge & Hosting: Amazon Web Services and Amazon Route 53. Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and All in One SEO. Company Ops: Microsoft 365. Last checked October 4, 2026.

What cloud does 織本構造設計 run on?

織本構造設計 uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

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 and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does 織本構造設計 use?

織本構造設計 uses WordPress and All in One SEO for its website. We found WordPress through website code.

Does 織本構造設計 use Microsoft 365?

Yes. We found Microsoft 365 at 織本構造設計 through DNS verification records and email records. Microsoft 365 is used by 319,377 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.