runsonwhat

Big Fernand's tech stack

What does Big Fernand use?

Big Fernand (bigfernand.com) uses at least 19 tools we can see from public records, including OVHcloud for hosting, Google Analytics for analytics, WordPress for its website and Mailjet for email delivery. Last checked .

Based in
France
Founded
2011
Tools found
19
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Big Fernand'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

Hosting & Cloud

Application

6 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Big Fernand tech stack FAQ

What tools does Big Fernand use?

We've found 19 tools at Big Fernand (bigfernand.com). Edge & Hosting: OVHcloud. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: reCAPTCHA, Mailjet and Axeptio. Last checked October 3, 2026.

What cloud does Big Fernand run on?

Big Fernand uses OVHcloud for hosting. We found OVHcloud through custom domain, email records and DNS records.

What analytics tools does Big Fernand use?

Big Fernand uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 4 tools in this category. We found Google Analytics through website code.

What CMS does Big Fernand use?

Big Fernand uses WordPress and Rank Math for its website. We found WordPress through website code.

Does Big Fernand use jQuery?

Yes. We found jQuery at Big Fernand through website code. jQuery is used by 766,430 companies we track.

How does runsonwhat know what Big Fernand uses?

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