runsonwhat

Lamia's tech stack

What does Lamia use?

Lamia (lamia.fi) uses at least 9 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents and Zendesk for customer support. Last checked .

Industry
IT Services
Size
51–200 employees
Based in
Helsinki, Finland
Founded
2012
LinkedIn
Company page
Re-check liveVisit lamia.fi
Tools found
9
Categories
7
Layers
3 of 5
Last checked
Oct 2026

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

Go-to-market

3 tools, how they find and keep customers

Marketing

Ads & Pixels

Support & Docs

Company Ops

5 tools, what the team runs on day to day

Workspace

Collaboration

Dev Tools

Companies like Lamia also use

Tools common among companies with a similar stack that we haven't found at Lamia.

Companies with a stack like Lamia's

Ranked by shared tools, with rare tools counting more.

More IT Services companies

Other IT Services companies we've checked.

Lamia tech stack FAQ

What tools does Lamia use?

We've found 9 tools at Lamia (lamia.fi). Edge & Hosting: Google Cloud. Go-to-market: Meta Pixel and Zendesk. Company Ops: Microsoft 365, Google Workspace and Atlassian. Last checked October 5, 2026.

What cloud does Lamia run on?

Lamia uses Google Cloud for hosting. We found Google Cloud through DNS records.

What email provider does Lamia use?

Lamia uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What does Lamia use for customer support?

Lamia uses Zendesk for customer support. We found Zendesk through email records.

Does Lamia use Microsoft 365?

Yes. We found Microsoft 365 at Lamia through DNS verification records. Microsoft 365 is used by 332,974 companies we track.

How does runsonwhat know what Lamia uses?

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