runsonwhat

Kodi's tech stack

What does Kodi use?

Kodi (kodi.de) uses at least 10 tools we can see from public records, including Hetzner for hosting, Microsoft 365 for email and documents and WordPress for its website. Last checked .

Size
1,001–5,000 employees
Based in
Germany
Founded
1981
LinkedIn
Company page
Re-check liveVisit kodi.de
Tools found
10
Categories
7
Layers
4 of 5
Last checked
Oct 2026

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

Frontend

Media & UI

Go-to-market

2 tools, how they find and keep customers

Website & CMS

Marketing

Company Ops

3 tools, what the team runs on day to day

Workspace

Dev Tools

Companies like Kodi also use

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

Companies with a stack like Kodi's

Ranked by shared tools, with rare tools counting more.

Kodi tech stack FAQ

What tools does Kodi use?

We've found 10 tools at Kodi (kodi.de). Edge & Hosting: Hetzner. Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 2, 2026.

What cloud does Kodi run on?

Kodi uses Hetzner for hosting. We found Hetzner through DNS records.

What email provider does Kodi use?

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

What CMS does Kodi use?

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

Does Kodi use Microsoft 365?

Yes. We found Microsoft 365 at Kodi through email records and DNS verification records. Microsoft 365 is used by 284,338 companies we track.

How does runsonwhat know what Kodi uses?

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