株式会社リグア's tech stack
What does 株式会社リグア use?
株式会社リグア (ligua.jp) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, Google Tag Manager for analytics, WordPress for its website and Pardot for marketing. Last checked .
- Industry
- Consumer Services
- Size
- 51–200 employees
- Based in
- 大阪府立大学 りんくうキャンパス, Japan
- Founded
- 2004
- Company page
- Tools found
- 9
- 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
1 tool, where the bytes are served from
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
2 tools, what the team runs on day to day
Email Delivery
Workspace
株式会社リグア tech stack FAQ
What tools does 株式会社リグア use?
We've found 9 tools at 株式会社リグア (ligua.jp). Edge & Hosting: Amazon Route 53. Application: jQuery, Google Fonts and GSAP. Data & Observability: Google Tag Manager. Go-to-market: WordPress and Pardot. Company Ops: Google Workspace and Amazon SES. 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 Tag Manager for analytics. We found Google Tag Manager through website code.
What CMS does 株式会社リグア use?
株式会社リグア uses WordPress for its website. We found WordPress through website code.
What marketing software does 株式会社リグア use?
株式会社リグア uses Pardot for marketing. We found Pardot through email records.
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.