Introduction

VeroXM is an experience management system: it gives your team a dashboard for modeling content, running experiments, and shaping how every audience experiences it, and gives your application a Content API for reading and writing that content from anywhere - a website, a mobile app, or another service. Content modeling is the foundation, not the whole story: the same project that stores your fields and entries also runs the A/B tests, media library, and localization that turn stored content into a tuned experience for each visitor.

Content management vs. experience management

A traditional headless CMS stops once content is validated and stored: it hands your application a JSON blob and considers the job done. VeroXM keeps going. Every entry can carry A/B test variants, every project can serve multiple locales, and every read can be shaped by the same platform that manages the underlying content - so the question your team gets to ask isn't just "what content do we have," but "which experience performs best."

How a VeroXM project is put together

Everything in VeroXM lives inside a project. A project has its own collections, fields, content, media library, experiments, and API tokens, so several projects (a marketing site, a mobile app backend, an internal tool) can run side by side without sharing data.

A project itself lives inside a Department, which in turn belongs to a Tenant - see Organization & Access for how that hierarchy, and the admins who manage each level of it, is structured.

• Collections define the shapes of content you want to manage - Blog Posts, Products, Team Members - each made up of fields.
• Fields are typed - text, rich text, number, relation, media, and more - so the dashboard can render the right editor and the API can validate and shape values consistently.
• Content is the actual entries created against a collection's fields, with draft/publish states and optional per-locale variants.
• Experiments let a content entry run two or more variants side by side, with traffic split by weight and results tracked as impressions and conversions, so the winning experience - not just the first draft - is what ships.
• Media Library holds the images and files your content references, uploaded once and reused across entries.

Reading and writing content

Once a project has collections and content, the Content API exposes it over HTTPS: list and filter entries, fetch a single entry, and - with a token that has the right abilities - create, update, or delete entries and media. Add ?experiment=1 to a content request and the API resolves a live A/B test on your behalf, returning a weighted-random variant instead of the base entry - see Content Experiments for the full flow. Prefer asking for exactly the fields you need in one round trip, including nested relations? The same content is also reachable through a read-only GraphQL API - same token, same cache, same data, just a different shape of request.

See it by industry

The same collection/field/experiment model looks different in practice depending on what you're building. The Examples section walks through worked setups for e-commerce, SaaS, media & publishing, and healthcare teams.

Where to go next

• New to VeroXM? Start with Creating A New Project.
• Modeling content? See Collections and Field Types.
• Integrating an application? Jump to Content API Authentication and Endpoints.
• Optimizing an experience? See Content Experiments.
• Setting up Tenants, Departments, or gating publishing behind review? See Tenants, Departments, and Approval Workflows.