Lecta's tech stack
What does Lecta use?
Lecta (lecta.com) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Microsoft SharePoint for its website and Cloudflare for content delivery. Last checked .
- Industry
- Paper & Forest Products
- Size
- 1,001–5,000 employees
- Based in
- Barcelona, Spain
- Company page
- Tools found
- 15
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Lecta'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
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
6 tools, what the team runs on day to day
Workspace
Collaboration
Security & Compliance
Lecta tech stack FAQ
What tools does Lecta use?
We've found 15 tools at Lecta (lecta.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: LinkedIn Insight Tag and Microsoft SharePoint. Company Ops: Microsoft 365, reCAPTCHA and Sectigo. Last checked October 3, 2026.
What email provider does Lecta use?
Lecta uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does Lecta use?
Lecta uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Lecta use?
Lecta uses Microsoft SharePoint for its website. We found Microsoft SharePoint through website code.
Does Lecta use jQuery?
Yes. We found jQuery at Lecta through website code. jQuery is used by 760,840 companies we track.
How does runsonwhat know what Lecta uses?
We read public traces only: Lecta'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.