Liquigas's tech stack
What does Liquigas use?
Liquigas (liquigas.co.nz) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
“Supporting the NZ Gas Industry by providing our customers with safe, reliable, and efficient LPG infrastructure services”
- Based in
- New Plymouth, New Zealand
- Tools found
- 8
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Liquigas'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
2 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
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
Liquigas tech stack FAQ
What tools does Liquigas use?
We've found 8 tools at Liquigas (liquigas.co.nz). Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: WordPress and Rank Math. Company Ops: Microsoft 365, Apple Business and reCAPTCHA. Last checked October 4, 2026.
What email provider does Liquigas use?
Liquigas uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Liquigas use?
Liquigas uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Liquigas use?
Liquigas uses WordPress and Rank Math for its website. We found WordPress through website code.
Does Liquigas use Microsoft 365?
Yes. We found Microsoft 365 at Liquigas through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Liquigas uses?
We read public traces only: Liquigas'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.