Invest in Klacos
Websites no longer get only visitors. Klacos sits in front of a site, analyses every visit before it reaches the server and decides what happens next: serve it, count it, slow it down or stop it. We’re meeting investors and partners who want to back the next stage of the project.
More than half of web traffic is not human
These figures come from Thales’s 2026 Bad Bot Report, the thirteenth edition of Imperva’s report, based on the traffic its services see. Every site pays for it: bandwidth and servers for visitors who will never buy, scraped content, fake sign-ups, ad tags that count bots, and analytics nobody can trust any more. All of that traffic ends up on the site’s infrastructure, mixed in with real customers.
AI crawlers have changed the question
The same report counts twelve and a half times more AI-assisted bot attacks than a year earlier. At the same time, the crawlers behind AI assistants and models read websites at scale, either to train or to answer their users.
Since 1 July 2025, Cloudflare blocks AI crawlers by default on new domains signing up with it. Knowing who visits a site, and deciding who may read it, is now a question every publisher asks, whatever their size.
One read of every visit, many decisions
See real traffic
The real share of bots, day after day, a human audience measured without cookies, and tags that don’t fire for bots.
Protect without friction
Detection visitors never see, with no CAPTCHA by default, a web application firewall, and decisions that explain themselves.
A fast site
Certificates, caching, purge, a waiting room and service continuity, with no downtime.
The service sits in front of the site without changing its hosting. It analyses every visit, establishes what it can (a person, a verified bot, an unwanted bot, or an unknown when the evidence isn’t there), then applies the customer’s policy: let it through, serve it from the cache, count it in the audience, slow it down, check it or block it. Details are on the pages about cookieless analytics, the tag manager, bot protection, the web application firewall, performance and availability and the waiting room.
Five families of players, and the space left between them
The market is split today between five families of tools, sold and installed separately.
| Family | Examples | What it brings | What it leaves aside |
|---|---|---|---|
| Global edge platforms | Cloudflare, Akamai, Fastly, AWS | A global network, a proxy in front of the site, security, bot management | Analytics is missing or sold separately; detailed bot traffic analysis sits in higher tiers, such as Cloudflare’s Bot Analytics, offered on Business and Enterprise plans |
| European platforms | Bunny.net, Gcore, Link11, Myra | A proxy and a firewall run in Europe, often self-service | They do not measure audiences, and bot filtering often relies on a visible challenge or proof of work |
| Bot protection specialists | DataDome, HUMAN, Kasada | Advanced detection, sold mainly to large accounts | They usually sit on top of existing infrastructure, and show the share of bots without measuring the human audience |
| Security software you run yourself | CrowdSec, BunkerWeb, HAProxy | A firewall and bot filtering on your own servers, often under a free software licence, with reputation shared between users | They protect without measuring audiences, and bot filtering often relies on a visible challenge |
| Privacy-friendly analytics | Matomo, Plausible, Fathom | Statistics without cookies, or with a cookie you can switch off, often hosted in Europe | They do not protect the site, mostly measure through a script, and remove bots without showing what share they make up |
Many sites also have basic protection already: their host’s firewall, or a security plugin in their CMS.
Klacos takes the space between these families: one service in front of the site that serves pages, judges each visit and measures the audience from the same data. It doesn’t try to rebuild a global network. It is meant for web professionals of every size, not just large accounts, it is run in the European Union, and it can also be installed on the customer’s own servers.
What others sell separately, or not at all
One read for protection and analytics
The real share of bots, next to the audience
Replay before enforcing
An explanation that reaches the visitor
The same product, in Europe or on the customer’s servers
Running it on the customer’s side is covered on the page about on-premise WAF and bot protection.
Klacos is already running on live sites
Early access opens in early 2027.
What we cover in person
This page describes the complete service. The rest we cover in meetings with people considering backing us:
- what already runs, what is left to build, and the timeline;
- the target market and how it splits, from independent sites to hosting providers;
- the business model we have in mind;
- the team, and our figures.
Let’s talk about what comes next
What we are looking for
Investors, and partners who want to support the project: hosting providers, integrators, website publishers ready to try it among the first.
What happens next
Your message reaches the team’s inbox. We’ll reply to arrange a conversation.