runsonwhat

Tokyo Financial Exchange's tech stack

What does Tokyo Financial Exchange use?

Tokyo Financial Exchange (tfx.co.jp) uses at least 4 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Akamai for content delivery. Last checked .

Industry
Financial Product Debt Underwriting Business
Size
11–50 employees
Based in
Marunochi Marunochipakubirudeingu(2, Japan
Founded
1989
LinkedIn
Company page
Tools found
4
Categories
4
Layers
4 of 5
Last checked
Oct 2026

Tokyo Financial Exchange'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

1 tool, what the product is built with

Data & Observability

1 tool, what they measure and store

Company Ops

1 tool, what the team runs on day to day

Tokyo Financial Exchange tech stack FAQ

What tools does Tokyo Financial Exchange use?

We've found 4 tools at Tokyo Financial Exchange (tfx.co.jp). Edge & Hosting: Akamai. Application: jQuery. Data & Observability: Google Analytics. Company Ops: Microsoft 365. Last checked October 3, 2026.

What email provider does Tokyo Financial Exchange use?

Tokyo Financial Exchange uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Tokyo Financial Exchange use?

Tokyo Financial Exchange uses Google Analytics for analytics. We found Google Analytics through website code.

Does Tokyo Financial Exchange use Microsoft 365?

Yes. We found Microsoft 365 at Tokyo Financial Exchange through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Tokyo Financial Exchange uses?

We read public traces only: Tokyo Financial Exchange'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.