runsonwhat

リージョンズ株式会社's tech stack

What does リージョンズ株式会社 use?

リージョンズ株式会社 (regions.co.jp) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, HubSpot for sales, Google Analytics for analytics and reCAPTCHA for security. Last checked .

Industry
Staffing and Recruiting
Size
11–50 employees
Based in
Kita1-Jonishi, Japan
Founded
2008
LinkedIn
Company page
Tools found
12
Categories
7
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.

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

6 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 リージョンズ株式会社 (regions.co.jp). Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and HubSpot. Company Ops: Google Workspace and reCAPTCHA. Last checked October 3, 2026.

What CRM does リージョンズ株式会社 use?

リージョンズ株式会社 uses HubSpot for sales and CRM. We found HubSpot through email records and 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 Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics 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.