Cookifi, cheap to start and metered after that
Cookifi (at cooki.fi, not the .com) is one of the lower-priced ways to get a consent banner running. Its public pricing shows a €10 a month base plan, with a €15 a month plan also listed, and the usage rates are stated openly: the first 5 units — 10,000 events — are free each billing cycle, the next 250 units are €0.02 per unit, and anything above that is €0.01 per unit. There is a 14-day trial with no card required, Google Consent Mode v2 is supported, and Google's own Tag Manager documentation includes a Cookifi template, which makes the install path clear if you already run GTM. For a small site, that is a low-friction start.
Two things make it harder to compare than the headline suggests. The first is the meter. Your bill is a function of events, and "events" is not the same as pageviews or visitors, so forecasting next quarter's invoice means first working out how many events your traffic generates — a number most marketing teams do not have to hand. The second is what the public record doesn't say. Cookifi's published material does not state which IAB TCF version it supports, where customer data is hosted, or whether the platform can be self-hosted. For a tool whose whole job is documenting consent, those are reasonable things to want in writing before you commit, and right now you would have to ask.
Conzent vs Cookifi at a glance
| Conzent | Cookifi | |
|---|---|---|
| Pricing model | Per site, not per event — from a few euros per site per month, and the price drops as you add sites. See current tiers | A €10/mo base plan plus usage fees, with a €15/mo plan also listed; usage is billed in units of events |
| What happens when you grow | Nothing — there is no usage allowance to exceed and no per-event rate | The meter runs — first 5 units (10,000 events) free each cycle, then €0.02 per unit for the next 250, then €0.01 per unit |
| GDPR / IAB TCF / Consent Mode v2 | ✓ GDPR, CCPA & 25+ regional laws ✓ IAB TCF v2.4 ✓ Consent Mode v2 (Basic & Advanced) — all included, every plan | Consent Mode v2 supported and documented · IAB TCF version not published — if you need TCF for ad-tech vendors, confirm it directly before you buy |
| CMS & platform integrations | 6 native integrations: WordPress, Wix, Joomla, Drupal, TYPO3, Umbraco — plus a universal script tag for anything else | Google Tag Manager is the clearly documented path, with a template in Google's own help pages; no published CMS-by-CMS integration list |
| Self-hosted / open source | ✓ Yes — OCI, Apache 2.0, one-line installer, unlimited sites and pageviews | ✗ Not offered publicly — no open-source repository or self-hosted edition is published |
| EU data residency | ✓ Yes — managed cloud data hosted in Germany; self-host it and it never leaves your own server | The hosting region is not published — worth asking for in writing |
| Free tier | ✓ Free forever if self-hosted; free trial on managed cloud | A free usage allowance of 10,000 events per cycle sits inside the paid plan, plus a 14-day trial with no card |
Cookifi figures are taken from its public pricing page and documentation, current in 2026; VAT may apply on top. Pricing changes — confirm the numbers with Cookifi before you switch. See Conzent's current plans.
Switching from Cookifi? Here's what to expect
Moving CMPs follows the same shape whichever vendor you leave: install the new script alongside the old one for a short test window, run a fresh scan to rebuild your cookie categories, configure and preview the banner, then switch the live script and remove the old one. If you installed Cookifi through Google Tag Manager, the change is mostly a container edit — swap the template for the new script and republish, and keep the old tag paused rather than deleted until you have confirmed the new banner sets consent correctly. Historical consent records stay with the vendor that collected them and don't transfer, which is normal for any CMP migration, so plan to start your consent log fresh.
Why teams switch from Cookifi to Conzent
A bill you can forecast
Usage billing means you cannot budget without first predicting your event volume. Conzent charges for the number of sites you run, so the cost of your consent banner is the same in a quiet month and a record one.
The details are written down
Conzent publishes the TCF version it runs — v2.4 — and says where managed cloud data lives, which is Germany. When a compliance colleague asks, you can send a link instead of opening a support ticket.
An exit that doesn't cost anything
Conzent's core is open source under Apache 2.0. If the commercial relationship ever stops working for you, you can run the same platform on your own server for free instead of starting a vendor search.
Frequently asked questions
How much does Cookifi cost?
Its published pricing shows a €10 a month base plan, with a €15 a month plan also listed, plus usage fees. The first 5 units — 10,000 events — are free each billing cycle, the next 250 units are €0.02 per unit, and beyond that it is €0.01 per unit. VAT may apply on top.
Which IAB TCF version does Cookifi support?
That isn't stated in its public material, so we won't guess at it. If TCF matters for your ad-tech vendors, ask Cookifi to confirm the version in writing. Conzent runs TCF v2.4 on every plan, including self-hosted.
Can I self-host Cookifi?
No self-hosted edition or open-source repository is published. Conzent's core is Apache 2.0, runs as an OCI image with a one-line installer, and self-hosted data never leaves your own server.
What's the best alternative to Cookifi?
If the event meter is the problem, look for pricing set by site count instead. Conzent is built that way, publishes its TCF version and hosting region, includes Consent Mode v2 on every plan, and can be self-hosted at no cost if you'd rather own the whole thing.