VWO is an A/B testing, personalization and behavior analytics suite, now merged with AB Tasty under the Wingify brand. Pages here cover replacing it with self-hosted GrowthBook, or PostHog where heatmaps and recordings matter.
VWO's web testing and feature experimentation against self-hosted GrowthBook: visual editor and plan requirements, server-side flags, statistics, warehouse-native analysis, and what VWO bundles (personalization, heatmaps, recordings) that GrowthBook does not replace.
For teams using VWO for tests plus heatmaps and recordings: self-hosted PostHog covers experiments, heatmaps and session replay in one tool. This page covers where PostHog's free deployment tops out, the lack of support for self-hosted PostHog, and what you lose in no-code testing.
Moving from VWO to GrowthBook: inventorying running campaigns and flags, rebuilding visual tests in GrowthBook's editor or as coded experiments, swapping the VWO snippet and SDKs, defining metrics on your warehouse, and closing VWO campaigns without breaking live tests.
Cost of ownership by component: VWO's demo-only Growth, Pro and Enterprise plans per product and their limits on flags, environments, domains and recording retention, against GrowthBook's self-hosted plans, hosting, warehouse queries, migration and operations.
What the 2025 Everstone buyout and the September 2026 VWO and AB Tasty merger under the Wingify brand mean for customers: what is documented about the combined platform, what to check at renewal, and how to plan a move to self-hosted GrowthBook if you decide to leave.
Replacing VWO's behavior analytics, whose recordings are kept 1 to 3 months by plan: self-hosted PostHog or OpenReplay for session replay and heatmaps, or Matomo with its paid heatmap plugin, compared on masking, retention you control and hosting effort.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.