runsonwhat

La Folie Douce's tech stack

What does La Folie Douce use?

La Folie Douce (lafoliedouce.com) uses at least 8 tools we can see from public records, including OVHcloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and GlobalSign for security. Last checked .

Industry
Restaurants
Size
51–200 employees
Based in
Val-D’isère, France
Founded
1969
LinkedIn
Company page
Tools found
8
Categories
7
Layers
5 of 5
Last checked
Oct 2026

La Folie Douce'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

3 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

La Folie Douce tech stack FAQ

What tools does La Folie Douce use?

We've found 8 tools at La Folie Douce (lafoliedouce.com). Edge & Hosting: OVHcloud. Application: jQuery, Font Awesome and Vimeo. Data & Observability: Google Analytics. Company Ops: Microsoft 365 and GlobalSign. Last checked October 8, 2026.

What cloud does La Folie Douce run on?

La Folie Douce uses OVHcloud for hosting. We found OVHcloud through email records, DNS records and website code.

What email provider does La Folie Douce use?

La Folie Douce uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does La Folie Douce use?

La Folie Douce uses Google Analytics for analytics. We found Google Analytics through website code.

Does La Folie Douce use jQuery?

Yes. We found jQuery at La Folie Douce through website code. jQuery is used by 761,988 companies we track.

How does runsonwhat know what La Folie Douce uses?

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