runsonwhat

LEKI's tech stack

What does LEKI use?

LEKI (leki.de) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Sentry for monitoring and Cloudflare for content delivery. Last checked .

Based in
Germany
Founded
1948
Re-check liveVisit leki.de
Tools found
11
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

3 tools, what the product is built with

AI

Media & UI

Data & Observability

3 tools, what they measure and store

Monitoring

Analytics

Go-to-market

2 tools, how they find and keep customers

Ads & Pixels

Company Ops

2 tools, what the team runs on day to day

Workspace

Dev Tools

Companies like LEKI also use

Tools common among companies with a similar stack that we haven't found at LEKI.

Companies with a stack like LEKI's

Ranked by shared tools, with rare tools counting more.

LEKI tech stack FAQ

What tools does LEKI use?

We've found 11 tools at LEKI (leki.de). Edge & Hosting: Cloudflare. Application: Three.js, Cloudinary and Langdock. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365 and Atlassian. Last checked October 2, 2026.

What email provider does LEKI use?

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

What analytics tools does LEKI use?

LEKI uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does LEKI use Microsoft 365?

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

How does runsonwhat know what LEKI uses?

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