runsonwhat

Fabrik's tech stack

What does Fabrik use?

Fabrik (fabrik.so) uses at least 11 tools we can see from public records, including Vercel for hosting, Google Analytics for analytics, web-vitals for monitoring and Resend for email delivery. Last checked .

“Logiciel SaaS français de création de plans d'évacuation en ligne conformes ISO 7010, ISO 23601, NF X08-070 et APSAD R4. Utilisé par 250+ professionnels de la sécurité incendie.”

Industry
Software
Size
1–10 employees
Based in
Cousances-lès-Triconville, France
Founded
2024
LinkedIn
Company page
Tools found
11
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

2 tools, where the bytes are served from

Hosting & Cloud

Application

3 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Email Delivery

Fabrik tech stack FAQ

What tools does Fabrik use?

We've found 11 tools at Fabrik (fabrik.so). Edge & Hosting: Vercel and Namecheap. Application: Next.js and Tailwind CSS. Data & Observability: Google Analytics, web-vitals and PostHog. Go-to-market: Google Ads. Company Ops: Resend. Last checked October 4, 2026.

What cloud does Fabrik run on?

Fabrik uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.

What analytics tools does Fabrik use?

Fabrik uses Google Analytics and PostHog for analytics. We found Google Analytics through website code.

Does Fabrik use Google Analytics?

Yes. We found Google Analytics at Fabrik through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what Fabrik uses?

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