runsonwhat

Lectura's tech stack

What does Lectura use?

Lectura (lecturas.com) uses at least 12 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Akamai for content delivery. Last checked .

Industry
Retail
Size
1–10 employees
Based in
Turnhout, Belgium
LinkedIn
Company page
Tools found
12
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

3 tools, what the product is built with

Data & Observability

2 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

Lectura tech stack FAQ

What tools does Lectura use?

We've found 12 tools at Lectura (lecturas.com). Edge & Hosting: Microsoft Azure and Akamai. Application: Google Fonts, TollBit and Dailymotion. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365. Last checked October 1, 2026.

What cloud does Lectura run on?

Lectura uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain and DNS records.

What email provider does Lectura use?

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

What analytics tools does Lectura use?

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

Does Lectura use Microsoft 365?

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

How does runsonwhat know what Lectura uses?

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