runsonwhat

Dinamo (Norway)'s tech stack

What does Dinamo (Norway) use?

Dinamo (Norway) (dinamo.no) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Plausible for analytics, WordPress for its website and Mailgun for email delivery. Last checked .

Industry
Public Relations and Communications
Size
11–50 employees
Based in
Oslo, Norway
Founded
1996
LinkedIn
Company page
Tools found
10
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Dinamo (Norway)'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.

Application

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Collaboration

Dinamo (Norway) tech stack FAQ

What tools does Dinamo (Norway) use?

We've found 10 tools at Dinamo (Norway) (dinamo.no). Application: jQuery, Google Fonts and YouTube. Data & Observability: Plausible. Go-to-market: WordPress. Company Ops: Microsoft 365, Mailgun and Dropbox. Last checked October 3, 2026.

What email provider does Dinamo (Norway) use?

Dinamo (Norway) uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and DNS verification records.

What analytics tools does Dinamo (Norway) use?

Dinamo (Norway) uses Plausible for analytics. We found Plausible through website code.

What CMS does Dinamo (Norway) use?

Dinamo (Norway) uses WordPress for its website. We found WordPress through website code.

Does Dinamo (Norway) use Microsoft 365?

Yes. We found Microsoft 365 at Dinamo (Norway) through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Dinamo (Norway) uses?

We read public traces only: Dinamo (Norway)'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.