runsonwhat

Ligula's tech stack

What does Ligula use?

Ligula (ligula.se) uses at least 16 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Based in
Sweden
LinkedIn
Company page
Tools found
16
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

Hosting & Cloud

Application

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

6 tools, what the team runs on day to day

Ligula tech stack FAQ

What tools does Ligula use?

We've found 16 tools at Ligula (ligula.se). Edge & Hosting: Microsoft Azure. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365, SendGrid and Amazon SES. Last checked October 3, 2026.

What cloud does Ligula run on?

Ligula uses Microsoft Azure for hosting. We found Microsoft Azure through DNS records.

What email provider does Ligula use?

Ligula uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Ligula use?

Ligula uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Ligula use?

Ligula uses WordPress for its website. We found WordPress through website code.

Does Ligula use Microsoft 365?

Yes. We found Microsoft 365 at Ligula through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Ligula uses?

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