# Croct vs. Storyblok

Storyblok stores and delivers content. Croct decides which version of that content each visitor
sees, resolves it on the server, and measures what the change does to conversion. Teams run
both: Storyblok for blocks and the visual editor, Croct for who sees what.

## How they compare

| Capability                        | Storyblok | Croct |
|:----------------------------------|:---------:|:-----:|
| Document-based headless CMS       |    Yes    |   No  |
| Reusable components               |    Yes    |  Yes  |
| Content localization              |    Yes    |  Yes  |
| Management, content and data APIs |    Yes    |  Yes  |
| Customer data infrastructure      |     No    |  Yes  |
| Advanced audience segmentation    |     No    |  Yes  |
| Content personalization           |     No    |  Yes  |
| Bayesian A/B testing engine       |     No    |  Yes  |
| Dashboards and analytics          |     No    |  Yes  |
| First-class developer experience  |     No    |  Yes  |

The rows where both say yes are where the two overlap. The rows only Croct answers are what you
would otherwise buy from a CDP, an experimentation tool and an analytics vendor.

## 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.

## Adopting Croct

Croct runs alongside Storyblok, so adoption is incremental rather than a migration. The
[Storyblok integration](/integrations/storyblok) wires the two together.

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, publish variations in Croct, and leave
everything else where it already lives.

## Frequently asked questions

### Do I have to replace Storyblok?

No. Storyblok keeps holding your content. Croct decides which visitor sees which version of it
and reports what that does to conversion.

### What does Croct add that Storyblok does not do?

Audience segmentation, real-time user profiles, server-side personalization, Bayesian A/B
testing and the analytics that measure them, without a separate CDP.

### Does it work with the visual editor?

Yes. Blocks keep rendering through Storyblok, and Croct adds the dynamic content that makes each
block adapt to the visitor in front of it.

### 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.

### 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.