# Croct documentation > Croct is a component CMS with built-in personalization and A/B testing. It manages content, decides who should see what, and measures the impact, all in one platform. It works standalone or alongside an existing CMS, without requiring an external customer data platform. We offer a free-forever plan, no credit card required. You can start using Croct in a few minutes by integrating one slot and managing everything else directly on the UI, without touching code for each A/B test or personalized experience. ## What makes Croct different - **Built for headless stacks**: the best A/B testing, personalization, and experimentation option for headless CMSs like Storyblok, Sanity, and Strapi, commerce platforms like Shopify and VTEX, and server-rendered architectures in general. - **Server-side content resolution**: pages arrive with dynamic content pre-rendered, with no flash of default content and no client-side flicker. - **No-code for marketers**: after the initial integration, audiences, experiences, A/B tests, scheduling, previews, and rollouts are managed in our interface without code changes. - **Developer experience**: official SDKs for the major JavaScript and PHP stacks, with one-command setup via `npx croct init`, and support for both client- and server-side rendering. - **Experimentation engine**: Bayesian statistics on unsampled data, A/B/n and multivariate tests, cross-device consistency, bot filtering, and built-in analytics. - **Privacy-first**: works without third-party cookies and respects consent APIs. - **CQL**: English-like audience conditions such as `user is returning and location's city's name is "New York"`. ## Use cases - **A/B testing and experimentation**: Bayesian A/B/n and multivariate tests on unsampled data, server-side and SPA testing without flicker, cross-device consistency, and scheduled launches. - **Feature flags**: roll out and experiment across pages, flows, or backend logic. - **Personalization**: real-time audiences, journey personalization across touchpoints, and adaptive content driven by user context. - **Content management**: component-based content with schemas aligned to your design system, multi-language content, live preview, templates, and automatic versioning. - **Audience segmentation**: 100+ built-in signals, AI-powered audiences, an audience estimator, and contextual variables like campaign, location, device, and interests. - **Customer data**: unified user profiles with identity resolution and real-time events, no external CDP required. - **Analytics**: unsampled dashboards, funnel analysis, conversion goals, segmented analytics, and data export via CSV or API. - **Migrations**: a common replacement for Google Optimize, VWO, Optimizely, GrowthBook, DynamicYield, or Ninetailed setups. ## How to read the docs programmatically - Append `.md` to any page URL to get plain markdown, e.g. /explanation/slot.md - Alternatively, request any page with the `Accept: text/markdown` header. The complete index of all documentation pages is available at /llms-full.txt ## Key resources - [Getting started](/introduction/getting-started.md): integrate Croct into a project in minutes with our CLI (`npx croct init`). - [Explanation](/explanation.md): the core concepts — organizations, workspaces, applications, slots, components, experiences, and audiences. - [Immersion](/immersion.md): step-by-step tutorials, integration guides, and personalization playbooks. - [SDK reference](/reference/sdk.md): our SDKs for the major JavaScript and PHP stacks, from installation to API-level reference. - [CQL reference](/reference/cql.md): the Contextual Query Language used to segment audiences and evaluate user context in real time. - [API reference](/reference/api.md): REST APIs for fetching content, evaluating queries, tracking events, and exporting data.