runsonwhat

Ludoil Energy's tech stack

What does Ludoil Energy use?

Ludoil Energy (ludoil.it) uses at least 10 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Webflow for its website and Cloudflare for content delivery. Last checked .

Industry
Oil & Gas
Size
201–1,000 employees
Based in
Milan, Italy
Founded
1998
LinkedIn
Company page
Tools found
10
Categories
10
Layers
5 of 5
Last checked
Oct 2026

Ludoil Energy'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

Application

2 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

2 tools, what the team runs on day to day

Security & Compliance

Ludoil Energy tech stack FAQ

What tools does Ludoil Energy use?

We've found 10 tools at Ludoil Energy (ludoil.it). Edge & Hosting: Cloudflare and Amazon Route 53. Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: Google Ads and Webflow. Company Ops: Google Workspace and Usercentrics. Last checked October 4, 2026.

What email provider does Ludoil Energy use?

Ludoil Energy uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Ludoil Energy use?

Ludoil Energy uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Ludoil Energy use?

Ludoil Energy uses Webflow for its website. We found Webflow through custom domain and website code.

Does Ludoil Energy use Cloudflare?

Yes. We found Cloudflare at Ludoil Energy through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Ludoil Energy uses?

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