Choose the rollout lane that fits your stack.
Each platform page explains the buying flow, install path, hostname checks, and testing expectations, so teams can move from trial to production without guesswork.
Shared consent runtime, platform-aware rollout paths, customer downloads, and verification paths from one product core.
Cookie banner preview
Lightweight. Fast. Clear by default.
Cookie consent. Done easy.
Lightweight consent that keeps your site fast and your data intact.
Every supported rollout path in one place
Choose the platform you want to deploy on and open its dedicated landing page. Each path reflects the current package structure, hostname registration flow, and runtime verification model.
Same runtime rules. Different install lanes.
Every platform page leads into the same production-safe sequence: choose the right package, register the hostname, install the package, then test consent plus verification before launch.
- • Open the platform page for a simple buying and install overview.
- • Use Developers docs for the exact technical steps after purchase.
- • Use Customer docs after billing to move through downloads, billing, and verification.
- • Expect non-compliant installs to fall back to necessary-only restricted mode until billing and hostname checks are healthy.
Common questions before teams choose a platform path
Short, structured answers make it easier to compare platforms and understand how Cookiezy behaves across different stacks.
Does Cookiezy use the same consent model across platforms?
Yes. Cookiezy is built around a shared core consent model, even when the install path differs between WordPress, Shopify, Webflow, Wix, headless frontends, or Strapi-driven setups.
Which platforms have the most mature rollout path today?
WordPress, Shopify, Webflow, Wix, headless, React, and Next.js currently have the clearest production rollout paths. Strapi is positioned as a headless CMS bridge with plugin-oriented configuration support.
Do all platforms support hostname verification and restricted mode?
That is the intended rollout model. Supported platforms are designed to verify the active hostname and fall back to necessary-only restricted mode if billing, licensing, or hostname checks are not healthy.
Where should a new team start?
Start with the platform page for the target stack, then open the setup guide in Developers docs, complete billing and hostname setup, and finally generate the issued package from customer downloads.