An ultra-light Tyn Captcha (1.5 KiB) for forms and a Rust server shield (1–3 µs) that stops scrapers, spam and ad click fraud right on your server, without handing traffic or SSL to third parties.
| Criterion | Tyn (tyn.com.ua) | Cloudflare (WAF / Turnstile) | Google reCAPTCHA / hCaptcha | Classic PHP anti-bots |
|---|---|---|---|---|
| DNS delegation and SSL exposure | Not needed (traffic goes straight to your server) | You hand over DNS and traffic is decrypted on a third-party proxy | Not needed | Not needed |
| Script weight on the page | 1.5 KiB (tyn.js), 0 trackers | ~25–60 KiB + provider telemetry | 150–400 KiB of scripts and frames, lower PageSpeed | A full interstitial page on every cold visit |
| What a shopper sees on a mobile network (CGNAT) | Thresholds ×3; at most a 1-second “Gate” | Frequent re-checks on shared mobile IPs | Picking traffic lights and hydrants for 15–30 seconds | A block or stub page for the whole carrier subnet |
| Keeping utm_referrer and gclid/fbclid | 100 % preserved for GA4 and CRM | Referrer may be lost on redirects | Does not protect GET visits from click fraud | Often overwrites the external Referer with an internal one |
| Load on the customer server | 1–3 µs in memory (Rust) | 0 on the server, but an extra network hop | A network request for every form | 5–40 ms of PHP interpreter start-up per hit |
| Data privacy (GDPR) | Form bodies and passwords are never read | All plain HTTP traffic passes through the provider | Behavioral tracking across sites | Depends on script settings |
Three steps: the stronger the suspicion, the costlier the check. Most people see nothing at all.
A quiet check of 12 non-invasive browser signals (no canvas, audio or font fingerprints) and a micro proof-of-work in the background. Page caching keeps working unchanged.
A person slides the latch (or presses Enter). While the motion lasts, the browser solves 8 SHA-256 chunks in WebCrypto. Released too early, the latch eases back, but the work already done is kept.
The server picks a kind at random inside a shared 280×96 frame: “Weave”, “Stake”, “Stile”. A wrong attempt gives a new picture, not an instant ban. For blind users there is a “Pass without an image” button.
A bot farm has to spend real CPU time on every attempt, and proof-of-work difficulty rises automatically for active subnets.
The token and the DOM never hold the right answer: the server derives the expected position and geometry from separate HMAC-SHA256 keys.
If bots learn one kind of task, it is updated or switched off on the server, with no code change on the customer site.
One widget per form or one binary in front of the whole site. If our server is unreachable, your site works as it did before.
<form method="post" action="/order">
<!-- Your form fields -->
<div data-tyn data-key="tyn_live_..." data-form="checkout" data-compact></div>
<button type="submit">Place order</button>
</form>
<script async src="https://tyn.com.ua/w/tyn.js"></script>With data-compact the widget is 0 px tall and appears only once the shopper touches the form. If the network does not answer within 4 s, the script writes tyn_token=unavailable, so your form never breaks.
Runs on the customer server with no DNS redirection and no TLS keys handed over. Each group expands into its list of towers.
For e-commerce owners and marketers.
An isolated guest session, no email and no password.
Four guarantees we build into the product, not into the slides.
If the cloud is unreachable or the monthly plan quota is exceeded, the local agent and the tyn.js widget never return 5xx — the site keeps taking orders.
Passwords, session cookies and POST bodies never leave your server; sensitive GET parameters are replaced with [REDACTED]; IP truncation (/24, /48, daily hash) and erasure on request are available.
Contrast from 4.5:1, full keyboard navigation, prefers-reduced-motion support, aria-live announcements and an honest path without an image.
Rule export and import in JSON and XML (AntiBot compatible), events sent to your own SIEM (JSONL / HMAC webhook).
If you exceed the request limit we never stop your site — we only notify you in the dashboard and on Telegram.
Blogs, landing pages, pet projects, a trial on a live form
Online shops, SaaS, active advertising on Google / Meta
Shop chains, large portals, web studios with clients
No. Your domain and certificate stay where they are.
tyn.js has a hard 4-second timer: the form is submitted normally with an “unavailable” mark. The local shield-agent keeps working from a policy snapshot in memory even fully offline.
No. POST webhooks never receive an HTML captcha; there are safe-path presets, X-Shield-Token machine tokens and a signed feed URL generator, all verified by a built-in checklist.
The .sgeo database recognises mobile carriers and automatically triples the thresholds (×3), and signed-in shoppers with an order history get session trust.
All URL parameters are kept in their exact order, and the external Referer is passed on in utm_referrer and sessionStorage.
Turn on Observe mode: the system holds nobody back but counts would_block / would_challenge and shows the real picture in the log before you switch to live mode.
Yes: in 2 minutes you can add just the tyn.js widget to forms or connect the single-file agent.php.