runsonwhat

Averoft's tech stack

What does Averoft use?

Averoft (averoft.com) uses at least 18 tools we can see from public records, including Yandex 360 for email and documents, Google Analytics for analytics, WordPress for its website and Brevo for marketing. Last checked .

Industry
Software
Size
51–200 employees
Based in
Sydney, Australia
Founded
2012
LinkedIn
Company page
Tools found
18
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Averoft'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

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Averoft tech stack FAQ

What tools does Averoft use?

We've found 18 tools at Averoft (averoft.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics. Go-to-market: WordPress, Meta Pixel and Brevo. Company Ops: Amazon SES and Yandex 360. Last checked October 6, 2026.

What email provider does Averoft use?

Averoft uses Yandex 360 for email and documents. We found Yandex 360 through email records.

What analytics tools does Averoft use?

Averoft uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Averoft use?

Averoft uses WordPress, WooCommerce and Rank Math for its website. We found WordPress through website code.

What marketing software does Averoft use?

Averoft uses Brevo, LinkedIn and SendPulse for marketing, among 4 tools in this category. We found Brevo through DNS verification records.

Does Averoft use jQuery?

Yes. We found jQuery at Averoft through website code. jQuery is used by 579,229 companies we track.

How does runsonwhat know what Averoft uses?

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