One service in front of your site, with wins specific to your business
An online shop loses sales when the site goes down on launch day. A publisher sees its articles copied and its audience inflated by bots. A SaaS product pays for password guessing and API abuse. An agency answers for every client site at once. Klacos analyses your traffic before it reaches your application, then uses what it learns to protect, speed up and measure your site, in the way your business needs.
Pick the situation closest to yours
Online shops
Price scrapers slowed then stopped, a capped login page, a sale that stays up, and conversions that count customers.
SaaS and APIs
An API shielded from abuse and injection, without breaking your customers’ integrations, and a reason for every refusal.
Media and publishers
Readers counted separately from bots, scrapers held back, and AI crawlers handled the way you decided.
Agencies and hosts
All your clients’ sites in one console, the right access for each person, and the whole platform on your own servers if you want it.
Each situation has its own page: ecommerce bot protection, API abuse protection for SaaS products, content scraping protection for publishers and website security for the sites you run for clients.
Four businesses, one way of working
Whatever your site, the starting point is the same. Klacos sits in front of it, with no change to your server or your hosting, and analyses every visit before it gets there. It tells your customers apart from search engines, AI crawlers, content scrapers and attacks. When it can’t tell, it doesn’t guess on your behalf: a visitor it knows nothing about isn’t blocked.
On day one, it observes and blocks nothing. You see your traffic as it really is, then choose what gets through, what slows down and what stops. You try a setting against your past traffic before it goes live, one step at a time.
And every decision keeps its reason. When a visitor is stopped, they see a reference; your team finds it in the console and unblocks them in one click if it was a mistake.
Right for you, or not: here is how to tell
You’ll get the most from it if
- you want to keep your current hosting and server;
- you don’t know how much of your traffic comes from people;
- bots are costing you server load, content, sign-ups or accurate numbers;
- you want to decide for yourself how AI crawlers are treated;
- you want cookieless analytics that don’t count bots;
- you want to see what a setting would do before it is enforced;
- you want the option to run everything on your own machines.
Look elsewhere if
- your priority is a global network of points of presence, close to every visitor;
- you need managed DNS or code running at the edge;
- you have to absorb volumetric attacks at network level;
- most of your visitors are on other continents and you don’t want to run anything yourself;
- you’re after payment fraud prevention, user sign-in or a paywall: those are different jobs, and they stay behind Klacos.
Klacos doesn’t try to cover everything: it focuses on your site’s traffic, to understand it, protect it and serve it. If a service already sits in front of your site, our feature-by-feature comparison shows what you keep and what you lose by switching.
Managed service, or on your own servers
The managed service
Run in the European Union. Point your domain at it, with nothing to install. Early access opens in early 2027.
On your servers
A Debian package or a Docker image, plus the console if you want it. A hosting provider can run each client as a separate account.
Running it on your own servers suits hosting providers, integrators and any team that wants to choose where its traffic is processed.
Start by seeing what your site actually receives
Request early access: your site starts in observation, and nothing is blocked until you decide. Or describe your situation, and we’ll tell you plainly whether Klacos is a fit.