runsonwhat

Oku's tech stack

What does Oku use?

Oku (oku.io) uses at least 10 tools we can see from public records, including Zoho for sales, Plausible for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

“Oku builds tools for information professionals and prosumers to manage their content feeds without noise or algorithmic interference.”

Founded
2026
Re-check liveVisit oku.io
Tools found
10
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

4 tools, what the product is built with

Frontend

AI

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

3 tools, how they find and keep customers

Website & CMS

Marketing

Sales & CRM

Company Ops

1 tool, what the team runs on day to day

Email Delivery

Companies like Oku also use

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

Companies with a stack like Oku's

Ranked by shared tools, with rare tools counting more.

Oku tech stack FAQ

What tools does Oku use?

We've found 10 tools at Oku (oku.io). Edge & Hosting: Cloudflare. Application: YouTube, Next.js and imgix. Data & Observability: Plausible. Go-to-market: WordPress and Zoho. Company Ops: Resend. Last checked October 2, 2026.

What CRM does Oku use?

Oku uses Zoho for sales and CRM. We found Zoho through email records.

What analytics tools does Oku use?

Oku uses Plausible for analytics. We found Plausible through website code.

What CMS does Oku use?

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

Does Oku use Cloudflare?

Yes. We found Cloudflare at Oku through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Oku uses?

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