runsonwhat

Tkorp's tech stack

What does Tkorp use?

Tkorp (tkorp.com) uses at least 11 tools we can see from public records, including OVHcloud for hosting, Google Workspace for email and documents, Prismic for its website and Cloudflare for content delivery. Last checked .

Industry
Software
Size
11–50 employees
Based in
Neuilly-Sur-Seine, France
Founded
2016
LinkedIn
Company page
Re-check liveVisit tkorp.com
Tools found
11
Categories
8
Layers
4 of 5
Last checked
Oct 2026

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

2 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

5 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

2 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like Tkorp also use

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

Companies with a stack like Tkorp's

Ranked by shared tools, with rare tools counting more.

Tkorp tech stack FAQ

What tools does Tkorp use?

We've found 11 tools at Tkorp (tkorp.com). Edge & Hosting: Cloudflare and OVHcloud. Application: Google Fonts, YouTube and GSAP. Go-to-market: Prismic. Company Ops: Google Workspace and Mailjet. Last checked October 6, 2026.

What cloud does Tkorp run on?

Tkorp uses OVHcloud for hosting. We found OVHcloud through email records.

What email provider does Tkorp use?

Tkorp uses Google Workspace for email and documents. We found Google Workspace through email records.

What CMS does Tkorp use?

Tkorp uses Prismic for its website. We found Prismic through website code.

Does Tkorp use Cloudflare?

Yes. We found Cloudflare at Tkorp through DNS records and website code. Cloudflare is used by 568,114 companies we track.

How does runsonwhat know what Tkorp uses?

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