Zyre installs by changing your DNS, with no dependency on your framework or host. Every technology gets dedicated WAF rules, maintained by our team.
WordPress
Dedicated WAF rules
Drupal
Dedicated WAF rules
Joomla
Dedicated WAF rules
Shopify
Dedicated WAF rules
WooCommerce
Dedicated WAF rules
PrestaShop
Dedicated WAF rules
Magento
Dedicated WAF rules
OpenCart
Dedicated WAF rules
Laravel
Dedicated WAF rules
Symfony
Dedicated WAF rules
Next.js
Dedicated WAF rules
Django
Dedicated WAF rules
Strapi
Dedicated WAF rules
Webflow
Dedicated WAF rules
Framer
Dedicated WAF rules
Wix
Dedicated WAF rules
SQL injection looks the same everywhere, but sites are not attacked at random. A scanner targeting WordPress asks for /wp-login.php and /wp-content/debug.log; one targeting Laravel asks for /.env and /telescope; one targeting Magento goes for /downloader and the API entry points. A single rule set therefore has to either accept everything or refuse everything — and either way it is wrong for most sites.
Each technology has its own rule file, merged with the shared set the moment your site is identified. There is nothing to choose: the technology is detected, the matching rules apply, and the ones that have nothing to do with your stack are never even evaluated. It is also what makes a block explainable — every rule carries an identifier, and that identifier appears in your threat centre next to the request that triggered it.
It is protected all the same. The shared rule set depends on no framework: it inspects the path, the query string, the body and the headers of an HTTP request — which every web application produces, whatever the language. A custom site in Go, Rust or hand-written PHP gets the same inspection; what it does not get are the rules aimed at the paths of software it does not run, which is exactly what it does not need.
Protection is switched on with a DNS change. No plugin, no extension, no module, no configuration file to touch, and your site stays hosted exactly where it is today. That is what makes it possible to cover technologies with no plugin ecosystem at all — a Next.js front end or a Webflow site has nowhere to install a firewall in the first place.
After the cutover, every request reaches your server from our addresses. A module that counts login attempts per IP address then sees a single IP for all your visitors, and may ban ours — cutting off all your traffic at once. It has to be configured to read the X-Forwarded-For header, or its limiter turned off. This is the only setting the cutover forces on your hosting side, and it is documented step by step.
Join the companies that chose to stop taking the hit.
Set up in 10 minutes · Cancel anytime · Hosted in Switzerland
ZyreEnterprise-grade SaaS protection for your sites and infrastructure.
© 2026 Zyre · All rights reserved