runsonwhat

Flint's tech stack

What does Flint use?

Flint (flintbooks.co.uk) uses at least 12 tools we can see from public records, including Kinsta for hosting, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

Based in
United Kingdom
Founded
2020
Re-check liveVisit flintbooks.co.uk
Tools found
12
Categories
7
Layers
5 of 5
Last checked
Oct 2026

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

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Website & CMS

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Companies like Flint also use

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

Companies with a stack like Flint's

Ranked by shared tools, with rare tools counting more.

Flint tech stack FAQ

What tools does Flint use?

We've found 12 tools at Flint (flintbooks.co.uk). Edge & Hosting: Cloudflare and Kinsta. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: reCAPTCHA and Cookiebot. Last checked October 4, 2026.

What cloud does Flint run on?

Flint uses Kinsta for hosting. We found Kinsta through website code.

What analytics tools does Flint use?

Flint uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Flint use?

Flint uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Flint use Cloudflare?

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

How does runsonwhat know what Flint uses?

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