runsonwhat

Liepājas Enerģija's tech stack

What does Liepājas Enerģija use?

Liepājas Enerģija (liepajasenergija.lv) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

Industry
Steam and Air Conditioning Supply
Size
51–200 employees
Based in
Latvia
Founded
2005
Tools found
8
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Liepājas Enerģija'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

1 tool, 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

Liepājas Enerģija tech stack FAQ

What tools does Liepājas Enerģija use?

We've found 8 tools at Liepājas Enerģija (liepajasenergija.lv). Edge & Hosting: Cloudflare. Application: jQuery. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Google Workspace and Cloudflare Turnstile. Last checked October 3, 2026.

What email provider does Liepājas Enerģija use?

Liepājas Enerģija uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Liepājas Enerģija use?

Liepājas Enerģija uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Liepājas Enerģija use?

Liepājas Enerģija uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Liepājas Enerģija use Cloudflare?

Yes. We found Cloudflare at Liepājas Enerģija through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Liepājas Enerģija uses?

We read public traces only: Liepājas Enerģija'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.