runsonwhat

Lezar House's tech stack

What does Lezar House use?

Lezar House (lezar.io) uses at least 5 tools we can see from public records, including Webflow for its website and Cloudflare for content delivery. Lezar House started using YouTube in Nov 2026. Last checked .

Industry
Internet
Size
11–50 employees
Based in
Barcelona, Spain
LinkedIn
Company page
Tools found
5
Categories
5
Layers
3 of 5
Changes seen
1

Lezar House's stack, layer by layer

Of 5 tools, 3 came from website code, 1 from custom domain and 1 from email records. 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

Application

2 tools, what the product is built with

Media & UI

Go-to-market

1 tool, how they find and keep customers

Website & CMS

What changed at Lezar House

Recent starts and stops

  1. StartedYouTube

Lezar House tech stack FAQ

What tools does Lezar House use?

As of November 2026, runsonwhat has found 5 tools at Lezar House (lezar.io) in public records. Edge & Hosting: Cloudflare and Gandi. Application: jQuery and YouTube. Go-to-market: Webflow. Last checked November 19, 2026.

What is Lezar House's website built with?

Lezar House uses Webflow for its website, according to runsonwhat (November 2026). runsonwhat found Webflow through a subdomain that points at Webflow and code on lezar.io. Webflow is used by 36,681 companies runsonwhat tracks.

Does Lezar House use jQuery?

Yes. runsonwhat found jQuery at Lezar House through jQuery code on lezar.io. jQuery is a Frontend tool used by 919,173 companies runsonwhat tracks.

Has Lezar House changed tools recently?

Yes. On runsonwhat's rechecks, Lezar House started using YouTube (latest on November 19, 2026). A change counts only between two checks of lezar.io done the same way.

How does runsonwhat know what Lezar House uses?

runsonwhat reads public records only. Of the 5 tools at Lezar House, 3 were found through code on lezar.io, 1 through subdomains that point at the vendor and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and lezar.io about 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.