runsonwhat

LEKO's tech stack

What does LEKO use?

LEKO (lekolabs.com) uses at least 11 tools we can see from public records, including OVHcloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Contentful for its website. Last checked .

Industry
Building Materials
Size
11–50 employees
Based in
Luxembourg
Founded
2017
LinkedIn
Company page
Tools found
11
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

LEKO tech stack FAQ

What tools does LEKO use?

We've found 11 tools at LEKO (lekolabs.com). Edge & Hosting: OVHcloud. Application: YouTube, Google Maps and Nuxt. Data & Observability: Google Analytics. Go-to-market: Mailchimp and Contentful. Company Ops: Microsoft 365, Apple Business and Bitwarden. Last checked October 3, 2026.

What cloud does LEKO run on?

LEKO uses OVHcloud for hosting. We found OVHcloud through DNS records.

What email provider does LEKO use?

LEKO uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.

What analytics tools does LEKO use?

LEKO uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does LEKO use?

LEKO uses Contentful for its website. We found Contentful through website code.

What marketing software does LEKO use?

LEKO uses Mailchimp for marketing. We found Mailchimp through website code.

Does LEKO use Microsoft 365?

Yes. We found Microsoft 365 at LEKO through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what LEKO uses?

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