F2B's tech stack
What does F2B use?
F2B (f2b.fr) uses at least 12 tools we can see from public records, including OVHcloud for hosting, Google Analytics for analytics, WordPress for its website and Brevo for marketing. Last checked .
“Spécialiste français du post-it personnalisé. BAT 24h gratuit, dès 50 ex.”
- Industry
- Proxy Server
- Based in
- Réaumont, France
- Founded
- 2014
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
F2B'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
2 tools, what the product is built with
Media & UI
Data & Observability
4 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
F2B tech stack FAQ
What tools does F2B use?
We've found 12 tools at F2B (f2b.fr). Edge & Hosting: OVHcloud. Application: Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, WordPress and Brevo. Company Ops: CookieYes. Last checked October 4, 2026.
What cloud does F2B run on?
F2B uses OVHcloud for hosting. We found OVHcloud through email records and DNS records.
What analytics tools does F2B use?
F2B 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 F2B use?
F2B uses WordPress for its website. We found WordPress through website code.
What marketing software does F2B use?
F2B uses Brevo for marketing. We found Brevo through DNS verification records.
Does F2B use Google Analytics?
Yes. We found Google Analytics at F2B through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what F2B uses?
We read public traces only: F2B'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.