For hosting providers and agencies
Offer your clients bot protection.
Earn a share of their payments
Strazh runs next to the web server on the client server and decides on every request: let through, check, or refuse. The client starts with a pilot in observe mode and sees a bot report before paying anything.
We discuss terms in person. We promise no specific figures upfront: we set them together with the first partners.
How Strazh fits into the stack
What has to be done on the client side, and what does not.
A web server subrequest
On every request the web server makes an auth_request to Strazh. 204 means let through, 401 means the check page, 403 means refuse. Site code and CMS stay untouched.
Runs on the client host
A separate lightweight process next to the web server, decisions in milliseconds. Rules and settings arrive as a snapshot from the central service.
Does not take the site down
The web server timeout is 300 ms: if Strazh is down or too slow, the visitor goes through. A slow history database does not block anything: the decision falls back to request signals.
Observe and enforce modes
In observe Strazh lets everyone through and logs “would have shown”. In enforce decisions are applied. A client pilot always starts in observe mode.
Signals
JA4 and TLS parameters, ASN and country, headers versus User‑Agent, address history, a browser probe on the check page. Signals add up to a score with configurable thresholds.
Search engines and IPv6
Crawler passes are set in the rules; usually Google, Yandex and Bing are let through without limits, and authenticity is checked by reverse DNS. IPv6 is fully supported: rules, crawler verification, passes.
Client dashboard
A log of decisions for every request, allow and block lists by address, network, country and JA4. Clients edit them themselves.
Check page
An “I am not a robot” button or Yandex SmartCaptcha. A signed one time challenge; the pass cookie is bound to the site and the address (for IPv6, to the /64 subnet).
What the partner gets
The model is a percentage of payments from the clients you bring. The size of the percentage, its duration and the rules for counting whose client it is are set based on the first requests, together with you.
If you are a hosting provider or an agency and your clients have bots, write to us. We will discuss how this could work for you.
The client sees the bots on their site
before paying for protection.
How to start
We discuss the partnership
Who your clients are, what their sites run on, how server access is organized.
A pilot with one client
We connect Strazh in observe mode; in 1–2 weeks the client gets a bot report.
We agree on terms
Based on the first connections, we fix the percentage, the accounting and the duration.
Discuss partnership
Leave your company website and a contact. We will write to you and set up a call.
- A percentage of payments from the clients you bring
- A pilot in observe mode for the client
- Terms set based on the first requests