Vox documentation
A data system for commerce and retail
It can own your business data, mirror data that other systems own, or do both. Whatever the source, the data is available to everything that needs it, through APIs and events.
Get startedConceptsGuidesAPI reference
Run the demo shop and add Vox to your own application.
Entities, owned and mirrored data, calculations, contexts and events.
Step-by-step instructions for common tasks.
Endpoints for every entity type.
What Vox does
Vox is a .NET engine that you host as part of your own application. You describe your entities, such as products, categories, prices, stores and campaigns, and Vox takes care of what every entity needs:
- Storage, an API and an admin UI for every entity type, with filtering, sorting, relations and search.
- Data it owns and data it mirrors, side by side. Data that Vox owns is changed through actions, with checks that stop two people from overwriting each other's changes. Data that other systems own is imported as it changes, in the format the other system already uses.
- One entity from several sources. A product can get its texts from the PIM, its prices from the ERP and its availability from a calculation in Vox. Each part has its own owner.
- Business logic as calculations. For example, whether a product can be sold in a market, based on the product, its categories, the prices, the stock and the market itself. Vox keeps track of what each calculation depends on, and recalculates when any of it changes.
- Events and subscriptions. Other systems are told what changed, through webhooks, message queues or streams, filtered to what each one needs.
- Languages, markets and channels. Values can vary by context, such as a name per language, and entities can belong to contexts, such as the products in the web shop.
- History and audit. Who changed what and when, version by version.
- Users, roles and permissions. Vox can hold the users itself, or let them sign in with your existing identity provider. Permissions go down to which fields a role may edit, in which languages or channels.
- Prototyping without code. Entity types and fields can be added while the system is running, so people who don't write code can shape a new app together. Once the app takes shape, the model is moved to code.
Vox is built on Nexus, which runs its imports, calculations and events as queues and jobs that can be followed, retried and run again.