runsonwhat

Fimlab's tech stack

What does Fimlab use?

Fimlab (fimlab.fi) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Tag Manager for analytics, WordPress for its website and Brevo for marketing. Last checked .

Industry
Laboratory
Based in
Finland
Founded
2011
LinkedIn
Company page
Tools found
14
Categories
9
Layers
4 of 5
Last checked
Oct 2026

Fimlab'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.

Application

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

6 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Email Delivery

Dev Tools

Security & Compliance

Fimlab tech stack FAQ

What tools does Fimlab use?

We've found 14 tools at Fimlab (fimlab.fi). Application: jQuery and Google Fonts. Data & Observability: Google Tag Manager. Go-to-market: WordPress, Yoast SEO and Brevo. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 3, 2026.

What email provider does Fimlab use?

Fimlab uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Fimlab use?

Fimlab uses Google Tag Manager for analytics. We found Google Tag Manager through website code.

What CMS does Fimlab use?

Fimlab uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.

What marketing software does Fimlab use?

Fimlab uses Brevo and LianaMailer for marketing. We found Brevo through DNS verification records.

Does Fimlab use Microsoft 365?

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

How does runsonwhat know what Fimlab uses?

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