A light Tyn Captcha for forms (≈2 KiB loader) and a Rust server shield 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 | tyn.js ≈2 KiB gzip; the widget card in an iframe up to 14 KiB gzip | ~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; for most people a single “I am not a robot” tick | 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 | URL parameters are kept, the external Referer is passed in utm_referrer | 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), an estimate for a clean request | 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) | Passwords and form field contents are never read; no third-party trackers | All plain HTTP traffic passes through the provider | Behavioral tracking across sites | Depends on script settings |
In a form it is an “I am not a robot” card with the Tyn mark. The stronger the suspicion, the costlier the check: a tick, then a picture task or a longer path without an image. In front of a whole site the shield shows the “Gate” page: a latch and 8 SHA-256 chunks in the browser.
A 65 px card in your form, light or dark. One click, tap or Space: while the square spins, the server scores the risk and issues a single-use token.
The card expands into a task in a 280×96 window. The server picks the kind: “Weave”, “Stake”, “Stile”. Release when it lines up and the check runs by itself. A wrong attempt gives a new picture, not a block.
For people who cannot see the picture: a longer 10–15 s check while the browser does a proof of work. Progress is announced through aria-live and everything works from the keyboard.
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="/contact">
<!-- your fields -->
<div data-tyn data-key="YOUR_SITE_KEY" data-form="contact" data-lang="en"></div>
<button type="submit">Send</button>
</form>
<script async src="https://c.tyn.com.ua/w/tyn.js"></script>The script adds a hidden tyn_token field to the form. Optional attributes: data-form (login, register, callback, subscribe, contact, review, other), data-lang (uk, en), data-theme (light, dark), data-compact. If the service does not answer within 4 s the field holds unavailable and the form is sent as usual.
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 and form field contents are never read. If the t.js analytics collector is enabled, it sets its own tyn_cid cookie to recognise returning visitors. IPs can be stored in full, truncated or as a daily hash; form contacts only if you switch that on yourself; data is erased on request.
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.