淀川キリスト教病院's tech stack
What does 淀川キリスト教病院 use?
淀川キリスト教病院 (ych.or.jp) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Akamai for content delivery. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Kunijima, Japan
- Founded
- 1955
- Company page
- Tools found
- 8
- Categories
- 7
- 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
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
淀川キリスト教病院 tech stack FAQ
What tools does 淀川キリスト教病院 use?
We've found 8 tools at 淀川キリスト教病院 (ych.or.jp). Edge & Hosting: Akamai. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Google Workspace. Last checked October 3, 2026.
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 Google Analytics for analytics. We found Google Analytics through website code.
What CMS does 淀川キリスト教病院 use?
淀川キリスト教病院 uses WordPress for its website. We found WordPress 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.