Skip to main content

Who Vox is for

  • Developers and architects who need a data layer for a new app, a new integration, or a system they're building themselves, and don't want to rebuild storage, APIs, imports and events every time.
  • People building with AI, who want the AI to focus on the UI and the experience on top of data that's already shared, structured and connected.
  • Product owners and business people who prototype a new app in a shared environment, or who manage the data that Vox owns in its admin UI.
  • Analysts who want business data, including the calculated parts, in one place for reports and BI.

What Vox isn't​

Vox is the data layer. Many things can be built on top of it, but it isn't those things itself:

  • Not a CMS, a PIM or a storefront out of the box. You can build those on top of Vox, but Vox doesn't come with the editing experience or the shop.
  • Not a backend for a specific front end. Vox stops at the entity. Shaping data for a particular app, such as a product page with its categories and prices in one response, is the job of the application that serves it.
  • Not an integration platform. Vox takes in imports and sends out changes, but it doesn't orchestrate or transform other systems' data on their behalf.
  • Not a search engine. It can use Elasticsearch for its queries, and can feed search, but searching for the shop is a separate concern.
  • Not a no-code platform for production. Changing the model while the system runs is for prototyping. The model in code is what counts.
  • Not a hosted service. Vox runs in your own .NET application, against your own database.