runsonwhat

Fraser Cars Ltd's tech stack

What does Fraser Cars Ltd use?

Fraser Cars Ltd (fraser.co.nz) uses at least 12 tools we can see from public records, including Fly.io for hosting, Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Based in
New Zealand
Founded
1988
Tools found
12
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Fraser Cars Ltd'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

3 tools, where the bytes are served from

Hosting & Cloud

Application

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Fraser Cars Ltd tech stack FAQ

What tools does Fraser Cars Ltd use?

We've found 12 tools at Fraser Cars Ltd (fraser.co.nz). Edge & Hosting: Cloudflare, Fastly and Fly.io. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Google Workspace. Last checked October 3, 2026.

What cloud does Fraser Cars Ltd run on?

Fraser Cars Ltd uses Fly.io for hosting. We found Fly.io through website code.

What email provider does Fraser Cars Ltd use?

Fraser Cars Ltd uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Fraser Cars Ltd use?

Fraser Cars Ltd uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Fraser Cars Ltd use?

Fraser Cars Ltd uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Fraser Cars Ltd use Cloudflare?

Yes. We found Cloudflare at Fraser Cars Ltd through DNS records. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Fraser Cars Ltd uses?

We read public traces only: Fraser Cars Ltd'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.