Varify.io
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Varify Software GmbH · varify.io
Compare with VWO → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Varify.io at a glance
- Vendor
- Varify Software GmbH
- Headquarters
- Incorporated in Germany source, captured 16 Nov 2026
- Data hosting
- In the EU by default; pages mention Germany source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Starting price
- “Cookie-loses A/B Testing ab 199€/Monat. Kein Consent Banner nötig.” (vendor’s words) source, captured 1 Oct 2026
- Panel verdict
- The AI panel rates Varify.io 3/5, the mean of 6 judges. Varify.io, a client-side A/B testing platform from Varify Software GmbH of Grünwald, Germany, is strongest where results are verified in the buyer's own stack: data and integrations scored 6 to 8, led by a BigQuery integration that delivers raw, unsampled, line-by-line experiment data into the customer's own project, and consent and tracking scored 6 to 7 on a cookieless design that assigns variants in localStorage while tracking fires only after consent. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Varify.io, a client-side A/B testing platform from Varify Software GmbH of Grünwald, Germany, is strongest where results are verified in the buyer's own stack: data and integrations scored 6 to 8, led by a BigQuery integration that delivers raw, unsampled, line-by-line experiment data into the customer's own project, and consent and tracking scored 6 to 7 on a cookieless design that assigns variants in localStorage while tracking fires only after consent. Pricing transparency scored 6 to 7 — Growth and Pro are fully priced in both billing periods with unlimited traffic — though Enterprise is a from-price and the captured pages give different entry figures. Statistical rigour sits at 5, minimum and maximum alike: methods are named, but the judges found no public information on sequential testing, multiple-comparison correction or sample ratio mismatch detection. Sovereignty scored 4 to 5 — the application is hosted on AWS in Frankfurt, yet snippet delivery runs through Cloudflare, Inc. of San Francisco and the data processing agreement was not confirmed on the captured pages. The judges produced no flagged disagreement.
Speaks for it
- Cookieless variant assignment in localStorage, with tracking fired only after consent via Consent Mode V1/V2, a consent tool or an activation event
- BigQuery integration puts raw, unsampled, line-by-line experiment data into the customer's own project, with BigQuery events importable as goals
- Growth and Pro are fully priced in both billing periods with stated limits and unlimited traffic, and the vendor states there is no traffic-based billing
- A 15-day full-product trial requires no credit card
- Concrete result-reading guidance of at least ten days, at least 500 conversions per variation and at most three metrics, with A/A test support
Held against it
- Server-side A/B testing appears only as a listed expert function, and we found no public information on SDKs, feature flags or holdouts
- We found no public information on sequential testing, multiple-comparison correction, sample ratio mismatch detection, or confidence and credible intervals per variant
- Snippet delivery runs through Cloudflare, Inc., a US-incorporated provider, and the data processing agreement was not confirmed on the vendor's captured pages
- AI credit prices, seats, minimum term and VAT treatment are unstated, and Enterprise is published only as from 799 € per month billed annually (starting from 9,588 € per year)
- The captured pages give different figures for the entry price (€119 per month on one homepage capture, from 199 € per month on the plans pages), for the controller's name, and for where the A/B testing provider processes data
Best for
- You run client-side A/B, multi-variation, split-URL or full-factorial multivariate tests and want results verifiable in your own BigQuery project
- You operate a consent-heavy European site and need variants served before consent with measurement fired only after it
- You want flat pricing with unlimited traffic and no traffic-based billing on the self-serve tiers (Growth: one domain, five active experiments; Pro: unlimited experiments)
- You evaluate experiments in an existing analytics stack — GA4, Adobe Analytics, Matomo, Piwik Pro, etracker, econda or PostHog — with the vendor stating it refrains from its own tracking
Avoid if
- You need server-side testing, language SDKs, feature flags or holdouts — the captured documentation lists server-side A/B testing only as an expert function and shows no implementation path
- Your programme depends on tool-enforced statistical safeguards, since the anti-peeking and uneven-allocation protections the judges found are guidance rather than sequential testing or automated detection
- Your data protection review cannot accept snippet delivery through Cloudflare, Inc. of San Francisco or transfer bases of standard contractual clauses
- You run flicker-sensitive pages where Core Web Vitals are contractual, given the vendor's own warning that the optional anti-flicker script may negatively affect Core Web Vitals and SEO
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 3 of 5 |
| Statistical method & guardrails | 2.5 of 5 |
| Consent & visitor tracking | 3.5 of 5 |
| Snippet performance & flicker | 3 of 5 |
| Analytics, data export & integrations | 3.5 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
The documented surface is what my team actually uses: a visual editor with content, style and split-URL changes, full-factorial multivariate tests with auto-generated combinations, multi-page experiments, audience and page targeting, configurable traffic distribution and mutual exclusion of experiments. Server-side testing appears only as a line in the expert functions list, and I found no public information on SDKs, feature flags or holdouts, so it stops short of an enterprise-grade programme. 12 1 11 5 6
The E-Commerce Manager
The documentation shows A/B, multi-variation, split-URL and full-factorial multivariate tests through a visual and code editor, with audience targeting, multi-page experiments and mutual exclusion of experiments — enough to structure a real programme on my product pages. Personalisation appears as a test type and server-side testing is listed as an expert function, but we found no public information on documented server-side SDKs, feature flags, holdouts, or personalisation measured against its own control group. 1 5 5 6 11
The Product Engineer
The visual and code editors cover A/B, multi-variation, split-URL and full-factorial multivariate tests, with multi-page experiments, audience targeting, configurable traffic distribution and mutual exclusion all documented. Server-side A/B testing and an Experiment API appear only as named expert functions, and we found no public information on SDKs for specific languages, feature-flag experiments or holdouts — for anything beyond the browser, the documentation does not show the how. 1 5 11 13
The CRO Consultant
The visual and code editors cover client-side A/B, multi-variation, split-URL, full-factorial multivariate and personalisation, with page and audience targeting, mutual exclusion of experiments, multi-page experiments and a QA mode documented in the setup flow. Server-side A/B testing appears only as a named expert function, and we found no public information on SDKs for common languages, feature-flag experiments or holdouts. 5 11 1 5 6
The Data Protection Officer
The documentation shows A/B, multi-variation, split-URL and personalisation tests through a detailed visual and code editor, full-factorial multivariate tests with automatically generated combinations, multi-page experiments, mutual exclusion and audience targeting. Server-side testing appears only as a line under expert functions, with no SDK for any language, no feature-flag model and no holdouts documented anywhere I read. 1 6 12 5 11
The Skeptic
A/B, multi-variation, split-URL and full-factorial multivariate tests run through a visual editor and a code editor, with multi-page experiments, mutual exclusion of experiments, audience and page targeting, a configurable traffic split, personalisation and a documented setup flow with preview and QA mode. The server-side option appears only as a listed expert function, and we found no public documentation of SDKs, holdouts or feature-flag experiments. That is a broad client-side programme that stops short of a server-inclusive one. 5 6 13 11 5
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
The methods are named and honest — a frequentist default (one-sided chi-square for rates, one-sided t-test for value metrics), a two-tailed option and Bayesian probability-to-beat in Pro, set once at account level — with a significance calculator, a runtime forecast toward 95 % significance, and stated reading guidance of at least ten days and 500 conversions per variation with interim results to be ignored. I found no public information on confidence or credible intervals per variant, sequential testing, a correction for multiple metrics beyond the alpha-error warning, or automated sample ratio mismatch detection — the uneven-traffic caveat is guidance, not detection. 7 8 7 7 8
The E-Commerce Manager
The method is named and explained: a one-sided frequentist test by default (chi-square for rates, t-test for order values), a Bayesian option with probability-to-beat and a runtime forecast, and significance read at 95%. The guidance on reading results is genuinely useful — ignore interim values, at least ten days and 500 conversions per variation, an A/A test to validate tracking, and a warning that each extra metric raises the false-positive risk. We found no public information on confidence intervals per variant, sequential testing, sample-ratio-mismatch detection, or corrections for multiple comparisons. 7 8 7
The Product Engineer
The statistics are named precisely — a one-sided chi-square test for binomial targets and a one-sided t-test for value metrics by default, with a two-tailed option and a Bayesian method plus a runtime forecast to 95 percent significance in the Pro plan — alongside an A/A test mode and concrete run guidance of at least 10 days, 500 conversions per variation and at most 3 metrics. We found no public information on confidence or credible intervals per variant, or on sequential testing, multiple-comparison correction, sample ratio mismatch detection or variance reduction. 7 7 8
The CRO Consultant
Three named methods are documented — a one-sided chi-square and t-test default, a two-tailed option on Pro, and a Bayesian mode giving the probability a variant beats the original — with a significance calculator and unusually concrete guidance on when a result may be read (ten days minimum, 500 conversions per variation, at most three metrics, interim results ignored). We found no public information on confidence or credible intervals per variant, sequential testing, multiple-comparison correction, sample ratio mismatch detection, variance reduction or guardrail metrics. 7 8 7 7 8
The Data Protection Officer
The method is named precisely: a one-sided chi-square for binomial metrics and a one-sided t-test for value metrics by default, with two-tailed frequentist and Bayesian options on the Pro plan, a significance calculator, a Bayesian runtime forecast toward 95 % significance, and firm guidance to run at least ten days with 500 conversions per variation and ignore interim results. We found no public information on confidence or credible intervals per variant, multiple-comparison correction, sample-ratio-mismatch detection or variance reduction. 7 7 7 8 8
The Skeptic
To their credit the methods are named: a one-sided chi-square test for binomial metrics and a one-sided Student t-test for value metrics by default, a two-tailed frequentist option and a Bayesian method in the Pro plan, the latter reported as a probability that a variant beats the original with a runtime forecast. Guidance on when a result may be read is unusually concrete — at least ten days, at least 500 conversions per variation, at most three metrics, only the final result meaningful — with A/A test support and warnings about uneven allocation. But the protection against peeking is advice rather than sequential testing, we found no documented correction for multiple comparisons, no sample ratio mismatch detection, and no published confidence or credible intervals per variant. 7 7 8 7 8
Consent & visitor tracking
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
This is documented the way a German team needs it: the snippet sets no cookies, assigns variants in localStorage, and can load without consent while measurement fires only after consent — via Google Consent Mode V1/V2, the customer's own consent tool, or a tracking activation event — with pre-consent visitors kept in their variation via session storage. The vendor states that whether a consent option is needed "is decided by your legal review" under the ePrivacy reading that strictly necessary localStorage requires no banner; I found no public information on IP anonymisation or a written mapping to §25 TDDDG. 9 9 10 13 10
The E-Commerce Manager
The architecture is documented end to end: no cookies, variant assignment in local storage, and the snippet can serve variants before consent while tracking fires only after it — via Google Tag Manager consent modes, a consent tool, or a setTracking call — with a session-storage fallback so untracked visitors still see one consistent variant. The vendor publishes its legal position that strictly necessary local storage needs no consent banner and leaves the final call to my legal review. We found no public information on IP anonymisation or stated retention periods for the visitor data the product itself records. 9 9 10
The Product Engineer
This is a consent-aware architecture: variant assignment sits in localStorage with no cookies, and experiment playout is documented as separate from tracking, so variants are served while tracking waits for consent or a Consent Mode signal, with a built-in consent option, consent-tool integration and a session-storage fallback for untracked visitors. The disclosure around it is thinner: no published list of the exact storage keys and their lifetimes, no IP anonymisation or retention statement for customer experiment data, and the ePrivacy legal-basis argument is explicitly left to the buyer's own legal review. 9 10 10 9
The CRO Consultant
This is the strongest position I could put in front of a client DPO: no cookies, variant assignment in local storage, and a documented architecture in which the snippet serves variants while tracking fires only after consent via Consent Mode V1 or V2, a consent tool or an activation event, with the vendor publishing its reading that strictly necessary local storage needs no consent and leaving the final call to the customer's legal review. The privacy statement names the local storage objects used for A/B testing, but we found no public information on storage lifetimes or IP anonymisation. 9 10 9 9 2 10
The Data Protection Officer
The vendor does answer the timing question: the snippet can be integrated without consent, variant play-out and assignment run before and separately from tracking, and only the tracking is held until consent via Google Consent Mode V1/V2, a consent tool, or an activation event — while stating plainly that whether to load the snippet without consent is for the customer's own legal review to decide, on the legal position that localStorage variant assignment needs no consent under ePrivacy. What is missing for a higher score: no published list of the individual storage keys with their lifetimes, no statement on IP anonymisation or visitor-data retention from the script, and §25 TDDDG is never named on any captured page. 9 9 9 10 2
The Skeptic
The split between playout and tracking is documented end to end: the snippet loads and assigns variants from localStorage without cookies, experiments run before consent, and tracking fires only after consent via Google Tag Manager Consent Mode V1/V2, a consent tool, or an activation event, with 14-day log deletion and a published ePrivacy position on strictly necessary localStorage. We found no public list of storage keys with their lifetimes, no IP anonymisation statement, and the legal assessment is explicitly left to the customer's own review rather than mapped in writing to the German consent statute. 10 9 9 2 10
Snippet performance & flicker
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead
The numbers I can take to our dev team are published: an 11.5 KB snippet with a stated load time under 30 ms, delivered through Cloudflare, plus an optional anti-flicker script with a configurable four-second hide that the documentation itself warns may negatively affect Core Web Vitals and SEO. I found no public information on measured Core Web Vitals impact of the snippet itself, a self-hosting or first-party-domain option, or per-project bundles containing only active experiments. 11 11 11 4 10
The E-Commerce Manager
Snippet weight and load time are published (11.5 KB, under 30 ms on typical connections), delivery runs through Cloudflare, and the anti-flicker script is optional with a configurable four-second hide — including the honest caveat on the page that it can hurt Core Web Vitals and SEO. Flicker prevention is otherwise documented as variants applied before render plus placement of the snippet in the head. We found no public information on self-hosting the script, per-project bundles containing only active experiments, or tooling showing what my own configuration costs the page. 11 11 10 4
The Product Engineer
The vendor publishes its own numbers — an 11.5 KB snippet loading in under 30 ms, delivered through Cloudflare — and the optional anti-flicker script with its configurable 4-second hide timeout is documented together with the honest caveat that it may hurt Core Web Vitals and SEO. We found no public information on a self-hosting or first-party-domain option, per-project bundles containing only active experiments, or measured Core Web Vitals impact, and server-side testing is a listed expert feature rather than a documented edge path for flicker-sensitive pages. 10 11 4
The CRO Consultant
Weight and loading are published — an 11.5 KB snippet loading in under 30 ms — with delivery through Cloudflare, an optional anti-flicker script whose configurable four-second hide and possible Core Web Vitals downside are documented, and head placement recommended when flicker appears. We found no public information on self-hosting, per-project bundles or measured Core Web Vitals impact for the standard snippet. 11 11 12 1 4 10
The Data Protection Officer
An 11.5 KB snippet with a stated load under 30 ms, delivered via Cloudflare, plus an optional anti-flicker script that hides the page for a configurable four seconds and whose downside the vendor states itself — a possible negative effect on Core Web Vitals and loading time. We found no published measurements of Core Web Vitals impact, and no self-hosting, first-party-domain or per-project bundle option on the captured pages. 10 11 4 12
The Skeptic
The anti-flicker script is documented with its trade-off: it hides the page for a configurable four seconds before the snippet, and the documentation itself warns of a possible negative effect on Core Web Vitals through extended load time, with head placement and the late-loading cause of flicker also covered. Snippet weight of 11.5 KB and load time under 30 ms are stated on a marketing page without measurement methodology, delivered via Cloudflare. We found no published Core Web Vitals measurements, no self-hosting or per-project bundle option, and the server-side route for flicker-sensitive pages is a menu entry rather than a documented path. 11 11 4 10
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
The export story is the strongest part for defending uplift to finance: results export from Varify, a documented GA4 connection showing results in the dashboard, Adobe Analytics, etracker, econda, Matomo, Piwik Pro and PostHog, and a BigQuery integration that delivers the raw data "unfiltered, not aggregated, line by line" into our own project with no sampling. The Experiment API appears only as an expert function without documented limits, and the warehouse path is GA4/BigQuery-centric rather than warehouse-agnostic. 6 8 13 14 13
The E-Commerce Manager
Results export is documented, the GA4 and Google Tag Manager integrations are spelled out down to the custom dimension name, and the list runs from Adobe Analytics to Matomo, Piwik Pro, econda and PostHog. The BigQuery path is the strongest part for me: raw, line-by-line experiment data in my own project with no sampling, events there usable as goals — a result I can verify in my own data rather than take on trust. The Experiment API exists as an expert function; we found no public information on its rate limits or on CDP audience integrations. 13 14 8
The Product Engineer
Results land where I want them: the BigQuery integration writes experiment data raw and line-by-line into the customer's own project with automatic setup, no sampling, BigQuery events usable as goals and segmentation by any GA4 dimension, alongside GA4, Adobe Analytics, Matomo, Piwik Pro, etracker, econda, PostHog and server-side GTM. Results can be exported from the dashboard and an Experiment API is listed under expert functions, but we found no public information on its rate limits or on webhooks. 14 13 13
The CRO Consultant
Results are computed in the client's own stack, which is what makes a finding defensible: the GA4 connection shows uplift and significance in the dashboard, the BigQuery integration puts raw, unsampled, line-by-line data in the client's own project with GA4 events importable as goals, and Adobe Analytics, Matomo, Piwik Pro, etracker, econda, PostHog and server-side GTM sit among twenty-plus integrations alongside an Experiment API. We found no public information on API limits or a CDP audience integration. 4 13 14 13 1 13
The Data Protection Officer
Results export from the dashboard, twenty-plus integrations including Google Analytics 4, Adobe Analytics, Matomo, Piwik Pro and server-side Google Tag Manager, and a BigQuery integration that puts raw, unsampled experiment data line by line into the customer's own project with BigQuery events usable as goals. The experiment API appears only as a listed expert function with no documented limits, and we found no public information on CDP integration for audiences. 14 13 13 4
The Skeptic
The strongest piece is BigQuery: experiment data raw, unaggregated and line by line in the customer's own project, with no sampling, events importable as goals and results segmentable by any GA4 dimension. GA4 results surface in the vendor dashboard, and Adobe Analytics, etracker, econda, Matomo, Piwik Pro and PostHog integrate alongside Google Tag Manager, server-side GTM and an export of results. The Experiment API is named as an expert function without stated limits, and we found no public information on CDP audience integration — though the vendor states it refrains from its own tracking and evaluates on the customer's analytics. 8 13 14 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
A German contracting entity (Varify Software GmbH, Amtsgericht München HRB 289569) and application hosting on AWS in Frankfurt are stated, with sub-processors and transfer bases referenced in the annex of the data processing agreement. But the snippet that runs on every visitor is delivered through Cloudflare's global network — Cloudflare, Inc. of San Francisco — and non-EEA transfers rely on adequacy decisions and standard contractual clauses; the captured pages also give different statements on where Varify processes data, one saying the EU and another the USA. 2 2 4 2 3
The E-Commerce Manager
The contracting entity is German (Varify Software GmbH of Grünwald, registered at Munich Local Court) and the application runs on AWS in Frankfurt, with a data processing agreement referenced in the plans and named for Enterprise customers. However, snippet delivery runs through Cloudflare's global network — Cloudflare, Inc. of San Francisco — and the transfer bases stated in the privacy statement point to some processing outside the EU; the captured pages also give different company names for the controller at the same Grünwald address. 3 4 2
The Product Engineer
A German company in the Munich commercial register hosts the application on AWS in Frankfurt with EU processing through Amazon Web Services EMEA, and references a DPA whose annex lists sub-processors and transfer bases. Snippet delivery runs through Cloudflare's global network — Cloudflare, Inc. of San Francisco — and the stated transfer bases of adequacy decisions, standard contractual clauses and Data Privacy Framework participation indicate processing beyond the EU; the captured privacy statements also give different figures for where the A/B testing provider processes meta and communication data. 3 4 2
The CRO Consultant
The contracting entity is German with a Munich court registration, application hosting in AWS Frankfurt is stated as standard, and subprocessors are named with their locations in the privacy statement. Snippet delivery nonetheless runs through Cloudflare's global network with a US entity named and standard contractual clauses documented as a transfer basis, the captured privacy pages give different figures for where A/B testing data is processed, and the data processing agreement is referenced in the hosting details and the Enterprise plan but its content is not published on the captured pages. 2 4 2 3
The Data Protection Officer
A German contracting entity registered at Munich local court and application hosting stated as AWS Frankfurt are solid, but the snippet that runs on every visitor is delivered through Cloudflare's global network, and the privacy statement itself names Cloudflare, Inc. of San Francisco with processing in the USA. The service's subprocessor list sits in an annex to a data processing agreement we could not see on the captured pages, and the two privacy-statement captures give different statements on where the A/B testing provider processes device and IP data (USA in one, EU in the other); the imprint and the privacy statement also name the entity differently (Varify Software GmbH versus Varify GmbH). 4 2 2 3 4
The Skeptic
A German contracting entity with a Munich register number and application hosting in AWS Frankfurt are documented, and the pages reference a subprocessor annex to a data processing agreement. Against that, snippet delivery runs through Cloudflare, Inc., a US-incorporated provider, and the privacy statement names standard contractual clauses and adequacy decisions as transfer bases; the data processing agreement itself was not confirmed on the vendor's own captured pages, and the pages give different names for the entity — Varify GmbH in the privacy statement, Varify Software GmbH in the imprint. 4 2 3
Pricing transparency
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
All tiers are public in both billing periods — Growth at 249 € per month or 199 € per month billed annually at 2,388 € per year, Pro at 349 € or 249 € at 2,988 € per year, Enterprise from 799 € per month at 9,588 € per year — and "no traffic-based billing" with unlimited traffic removes exactly the monthly-tracked-user estimation my budget fights about. Full computability stops there: AI credit packages carry no public rates, seats, minimum term and VAT treatment are not stated, multiple domains are on request, and the captured pages give different figures for the entry price — one homepage capture shows "€119 per month" while the plans pages start at 199 €. 1 4 4 1 4
The E-Commerce Manager
Growth and Pro are fully priced in both billing periods with limits printed (one domain, unlimited traffic, five active experiments on Growth at 249 € monthly / 199 € monthly billed annually; Pro at 349 € / 249 €), Enterprise from 799 € per month billed annually, and a 15-day full-product trial without a credit card — best of all for my December peaks, the vendor states there is no traffic-based billing at all. Still not public: seat counts, VAT treatment, the price of the AI credit packages, and anything beyond the 'from' figure for Enterprise; the captured pages also give different entry prices (119 € on one homepage capture, from 199 € on the plans page). 4 4 1
The Product Engineer
The two self-serve tiers are fully computable — Growth at 249 € per month or 199 € per month billed annually, 2,388 € per year, with one domain and 5 active experiments, Pro at 349 € or 249 €, 2,988 € per year, unlimited experiments — and traffic is explicitly unlimited with no traffic-based billing, which removes the estimation problem this category usually forces on buyers. Enterprise is published only as "from 799 € per month costs annually · starting from 9,588 € per year", and we found no public information on AI credit package prices, multi-domain pricing, seats, minimum term or VAT treatment; an earlier homepage capture also gives a different entry figure of €119 per month. 4 4 1 1
The CRO Consultant
Flat-rate pricing with unlimited traffic removes the traffic estimate from the contract entirely, and every tier is public with its billing period: Growth at 249 € per month or 199 € per month billed annually (2,388 € per year), Pro at 349 € or 249 € (2,988 € per year), Enterprise from 799 € per month billed annually (from 9,588 € per year). The captured pages give different figures for the entry price (€119 per month on one page against 199 € on the plans page), and AI credits, additional domains and the Realtime Tracking setup quoted individually on monthly tracked users are not publicly priced; we found no public information on seats or VAT treatment. 1 4 4 1 4
The Data Protection Officer
Growth and Pro are published with both billing periods and annual totals (249 € per month billed monthly or 199 € per month billed annually at 2,388 € per year for Growth; 349 € or 249 € at 2,988 € per year for Pro), traffic is stated as unlimited on every plan with no traffic-based billing, and a fifteen-day full-product trial runs without a credit card. Enterprise is only a from-price of 799 € per month billed annually, AI features are billed in credit packages whose prices are not published, we found no public information on seats, minimum term or VAT treatment, and the captured pages give different figures for the entry price — €119 per month on one homepage capture and from 199 € per month on the pricing pages. 4 4 4 1 1
The Skeptic
Growth and Pro are fully priced for monthly and annual billing with stated limits (one domain, five active experiments, ten active deploys on Growth, unlimited traffic), the vendor states there is no traffic-based billing, and a 15-day full-product trial requires no credit card. Open items remain: AI features are billed in credits from the Pro plan without public credit prices, Realtime Tracking is set up individually based on monthly tracked users, seats, minimum term and VAT treatment are unstated, and Enterprise is a from-price ("from 799 € per month", "starting from 9,588 € per year"). The captured pages also give different figures for the entry price — €119 per month on one homepage capture, "ab 199€/Monat" on a later one. 1 4 1 4
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in DE
unverified
Why unverified?The privacy statement names "Varify GmbH" while the imprint names "Varify Software GmbH", but both carry the same Grünwald address and no excerpt mentions a parent company. |
2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The homepage markets EU-only hosting ("Hosted in the EU"), but snippet delivery runs through Cloudflare's global network and the DPA's listed transfer bases indicate some processing/transfers outside the EU. |
2/4 pts | 4 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Varify.io
Is Varify.io European?
Yes. whats-best.ai classifies Varify.io as EU-Made. Its vendor, Varify Software GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does Varify.io store data?
Varify.io stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 22 Sep 2026.
Does Varify.io have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Varify.io?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Webtrends Optimize (3/5) and Kameleoon (2.5/5) highest among the other 45 Conversion Optimization products evaluated. The highest-rated European alternative is Webtrends Optimize (UK / wider Europe, United Kingdom). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Varify.io alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The privacy statement names "Varify GmbH" while the imprint names "Varify Software GmbH", but both carry the same Grünwald address and no excerpt mentions a parent company.
- Weak sourcing — Hosting location. The homepage markets EU-only hosting ("Hosted in the EU"), but snippet delivery runs through Cloudflare's global network and the DPA's listed transfer bases indicate some processing/transfers outside the EU.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 141 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 37 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 35 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 27 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 16 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage varify.io Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 19 Oct 2026, 22 Sep 2026 Details →
- 2 Privacy policy varify.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 3 Legal notice varify.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 4 Pricing page varify.io Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 30 Sep 2026 Details →
- 5 Experiment types & delivery — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 6 Experiment types & delivery — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 7 Statistical method & guardrails — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 8 Statistical method & guardrails — found from sitemap varify.io Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Oct 2026 Details →
- 9 Consent & visitor tracking — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 10 Consent & visitor tracking — found from sitemap varify.io Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 1 Oct 2026 Details →
- 11 Snippet performance & flicker — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 1 Oct 2026 Details →
- 12 Snippet performance & flicker — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 13 Analytics, data export & integrations — found from sitemap varify.io Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 14 Analytics, data export & integrations — found from sitemap varify.io Checked 16 Nov 2026 Details →
- 15 Structured-data backfill: markup only, no text or screenshot varify.io Checked 8 Nov 2026 Details →