A fast site that stays up, even when everyone turns up at once
A slow page loses visitors, and a site that’s down sells nothing, often on the very day it should sell the most. Klacos sits in front of your server and analyses traffic before it gets there: it turns away bots that load your server for nothing, serves from the cache whatever it can, covers for your server when it falters, and queues a rush instead of letting it fall over. Your server and your hosting provider stay exactly as they are.
One server, and everyone knocking at its door
Your server rebuilds every page for every visitor. Customers, search engines and bots all share the same machine: one scraper working through your pages slows everyone down, and on a sale day the rush alone can bring it to its knees.
The cost isn’t just on the hosting bill. It’s pages that load late, abandoned baskets, a payment that fails at the worst moment, a site that disappears during an update. Adding servers in a hurry is expensive, and usually lands after the peak.
None of this means changing hosting provider. What you need is something in between: something that serves what it can without touching your server, covers for it when it struggles, and lets visitors in at the pace it can handle.
The traffic analysis that protects your site also makes it faster
Caching, compression and failover are familiar tools. What’s different with Klacos is that they work alongside the per-visit analysis that already drives your site’s security.
Fewer wasted requests
A scraper working through your pages is slowed down, then stopped, before it reaches your server. The capacity it was using goes back to your visitors.
A queue kept for real buyers
On a sale day, bots don’t get a place in the waiting room. Whatever throughput your server can handle goes to actual people.
An origin with room to breathe
Pages that can come from the cache never reach your server. It keeps its capacity for the work that has to be computed: a basket, a payment, a search.
Your current server stays where it is
You keep your hosting and your software. Klacos goes in front of whatever serves your site today: nginx, Apache, object storage, a hosted CMS. Your server becomes the origin, and Klacos receives your visitors.
Protection and caching add no script to your pages: they work on requests, before they reach your server.
Pages served without making your server work
Caching keeps your pages in memory or on disk and serves them without calling on your server. You write the rules that suit your site, and you clear exactly what changed when you publish: one page, a folder, a tag. Visitors see the new version, and the rest of the cache keeps serving.
Compression and modern protocols make every response lighter, with Gzip, Brotli or Zstandard, over HTTP/2 or HTTP/3. And rules and redirects change safely: each rule can be tested against a request and run in observation before it applies, and every version stays available.
Your site stays up when your server falters
Service continuity serves the last copy of your pages if your server goes down, tells visitors quickly instead of leaving them waiting, and applies a new configuration without dropping the connections in progress.
With several servers, load balancing checks their health and fails over to a standby server on its own. On the day of a sale or a ticket release, the virtual waiting room queues the rush in order, and bots don’t get a place in the line.
What serves your pages, in one place
Caching and purge
Rules and redirects
Compression and HTTP/3
Service continuity
Load balancing
Waiting room
As a managed service, or on your own machines
The managed service
Run in the European Union, with early access opening in early 2027. Nothing to install.
On your own servers
A Debian package with its systemd service, or a Docker image. It runs on its own, then connects to the console with a token, with nothing to reinstall.
Running it on your own servers can include the console too, if you want everything to stay in-house. Klacos is already running on live sites. If you’re comparing it with the service in front of your site today, our guide on what to ask before switching will help you weigh things up.
Questions about performance and availability
Do I need to replace my web server?
No. Klacos sits in front of it: your server keeps its configuration and becomes the origin. For a static site, files can also be served directly.
Do my current certificates still work?
Yes, if you want to keep them: you can import your own. Otherwise, certificates are issued and renewed automatically.
Is there a global network?
No. It runs in the European Union, in front of your server. For a site whose visitors are mostly in Europe, that’s rarely a limit; if a large share of your audience is on other continents, talk to us.
Which protocols are supported?
HTTP/1.1, HTTP/2 and HTTP/3, over TLS 1.2 and 1.3, as well as WebSocket.
Start by seeing what bots ask of your server
With early access, Klacos starts in observation in front of your site: it blocks nothing and shows you who is using your resources. Request access, or talk to us about running it on your own servers.