Why we built a captcha service from scratch — and why privacy wasn't optional.
We were building forms. Adding reCAPTCHA meant adding Google tracking to every page. Switching to hCaptcha was better — but still required cookie banners, still sent data outside the EU, and still made users click fire hydrants.
There had to be a better way. And there was: Proof of Work. Instead of asking users to identify blurry images to train AI models, the browser simply solves a small cryptographic puzzle. It takes milliseconds for a real device. It's computationally expensive for a bot running thousands of requests in parallel.
No images to click. No cookies to set. No personal data to collect. No consent banners. Just protection that's invisible to real users and painful for bots.
Zhylon Captcha is part of the Zhylon ecosystem — a collection of independent developer tools built by developers, for developers, hosted entirely in the EU.
{{ item.d }}
Privacy isn't a feature you add later. It's a constraint we design within from day one.
{{ f.d }}
{{ f.d }}
{{ v.d }}
Zhylon Captcha is in open beta. The core PoW engine is live and processing real verifications. Here's our honest status and what comes next.
Zhylon is not a corporation. It's a community of developers building the tools they wish existed.
Software developer with a focus on Laravel, Vue and modern web infrastructure. Started Zhylon as a collection of tools he kept rebuilding for different clients. Zhylon Captcha was born after one too many GDPR headaches with existing captcha providers.
We welcome contributions — whether that's code, documentation, bug reports, or just spreading the word. Every bit helps.
Zhylon Captcha is one piece of the Zhylon ecosystem — a growing suite of EU-hosted developer tools.
Zhylon is not a corporation. It's a community of developers building the tools they wish existed.
Software developer with a focus on Laravel, Vue and modern web infrastructure. Started Zhylon as a collection of tools he kept rebuilding for different clients. Zhylon Captcha was born after one too many GDPR headaches with existing captcha providers.
We welcome contributions — whether that's code, documentation, bug reports, or just spreading the word. Every bit helps.
Start free. Support us when it clicks. Shape the product before launch.