runsonwhat

Fleuristes et fleurs's tech stack

What does Fleuristes et fleurs use?

Fleuristes et fleurs (fleuristes-et-fleurs.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and reCAPTCHA for security. Last checked .

Industry
Floristry
Size
1–10 employees
Based in
Les Hauts-Saint-Jean, France
Founded
2009
LinkedIn
Company page
Tools found
11
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Fleuristes et fleurs'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

Application

2 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Fleuristes et fleurs tech stack FAQ

What tools does Fleuristes et fleurs use?

We've found 11 tools at Fleuristes et fleurs (fleuristes-et-fleurs.com). Edge & Hosting: Gandi. Application: jQuery and Google Maps. Data & Observability: Google Analytics and Matomo. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365 and reCAPTCHA. Last checked October 4, 2026.

What email provider does Fleuristes et fleurs use?

Fleuristes et fleurs uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Fleuristes et fleurs use?

Fleuristes et fleurs uses Google Analytics and Matomo for analytics. We found Google Analytics through website code.

Does Fleuristes et fleurs use Microsoft 365?

Yes. We found Microsoft 365 at Fleuristes et fleurs through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Fleuristes et fleurs uses?

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