# Croct vs. VWO

VWO runs experiments in the browser. Croct decides content on the server before the page is
sent, which is why there is no flicker and no anti-flicker snippet. Segmentation, profiles and
content management come with it rather than as separate purchases.

## How they compare

| Capability                                    | VWO | Croct |
|:----------------------------------------------|:---:|:-----:|
| Fast load times with no flickering            |  No |  Yes  |
| Headless CMS with server-side rendering       |  No |  Yes  |
| Content localization                          |  No |  Yes  |
| Server-side content personalization           |  No |  Yes  |
| Runs without developer or support involvement |  No |  Yes  |
| Advanced segmentation with no third-party CDP |  No |  Yes  |
| Real-time user data processing                |  No |  Yes  |
| User data structuring and unification         |  No |  Yes  |
| Integration in hours rather than weeks        |  No |  Yes  |
| First-class developer experience              |  No |  Yes  |

## Why teams choose Croct

- **Server-side by design.** Content is resolved before the page is sent, so experiences
  arrive personalized with no flicker and no anti-flicker snippet blanking the page.
- **One platform, no extra vendors.** Segmentation, user profiles, experimentation and
  analytics are built in, so there is no separate CDP, feature-flag tool or analytics
  contract to buy and wire together.
- **Built for headless stacks.** Croct sits alongside Storyblok, Sanity, Strapi, Contentful
  or Shopify Hydrogen and makes the content they hold contextual, instead of replacing them.
- **Marketers ship without developers.** After setup, audiences, experiences, A/B tests,
  scheduling and preview all happen in the Croct interface.
- **Bayesian experimentation on unsampled data.** A/B, A/B/n and multivariate tests with
  cross-device consistency for identified users and bot traffic filtered out.

Against VWO specifically, rendering is the first difference. A client-side test swaps content
after load, which costs a paint and needs a blocking snippet to hide. Croct sends the variation
in the first response, so the visitor never sees the swap.

## Adopting Croct

Croct runs alongside your current site, so tests move across one at a time rather than all at
once.

Setup is one command, `npx croct@latest init`, which installs the SDK, wires the provider
and generates TypeScript types for every slot. Official SDKs cover Next.js, React, Vue,
Nuxt, JavaScript, PHP, Laravel, Symfony, Drupal, and Shopify Hydrogen. Most teams are live
the same day, and the forever-free plan needs no credit card or commitment.

Define slots where content should become dynamic, then move experiences across one at a time.
Existing profile data can be imported, and enriched profiles export to your warehouse or to any
tool you already run.

## Frequently asked questions

### Do I still need an anti-flicker snippet?

No. The page arrives with the variation already in it, so there is nothing to hide and nothing
to blank.

### Can non-developers run the tests?

Yes. After setup, audiences, experiences, tests, scheduling and preview all live in the Croct
interface.

### Does personalization slow the page down?

No. Content resolves on the server before the response is sent, with end-to-end response times
under 90 milliseconds at the 95th percentile.

### What statistics does the A/B testing use?

Bayesian, computed on unsampled data, with A/B, A/B/n and multivariate tests, cross-device
consistency for identified users, and bot traffic filtered out.

### How long does it take to get running?

One command to install, and most teams are live the same day. Marketers run experiments
afterwards without further development work.

### What does it cost?

The forever-free plan covers 10,000 monthly active users with 3 content slots and 1
experience or experiment, and needs no credit card. Growth starts at $100 per month billed
annually for 20,000 monthly active users. Scale is custom.