runsonwhat

Oiltanking's tech stack

What does Oiltanking use?

Oiltanking (oiltanking.com) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Matomo for analytics and Let's Encrypt for security. Last checked .

Industry
Oil & Gas
Size
1,001–5,000 employees
Based in
Hamburg, Denmark
Founded
1960
LinkedIn
Company page
Re-check liveVisit oiltanking.com
Tools found
10
Categories
6
Layers
3 of 5
Last checked
Oct 2026

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

1 tool, what the product is built with

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Company Ops

8 tools, what the team runs on day to day

Workspace

Collaboration

Finance & Legal

Security & Compliance

Companies like Oiltanking also use

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

Companies with a stack like Oiltanking's

Ranked by shared tools, with rare tools counting more.

More Oil & Gas companies

Other Oil & Gas companies we've checked.

Oiltanking tech stack FAQ

What tools does Oiltanking use?

We've found 10 tools at Oiltanking (oiltanking.com). Application: Google Fonts. Data & Observability: Matomo. Company Ops: Microsoft 365, Apple Business and Let's Encrypt. Last checked October 3, 2026.

What email provider does Oiltanking use?

Oiltanking uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Oiltanking use?

Oiltanking uses Matomo for analytics. We found Matomo through website code.

Does Oiltanking use Microsoft 365?

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

How does runsonwhat know what Oiltanking uses?

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