Product — Features
Five modules, one single metamodel, zero integrations to maintain.
Each beVault module can be presented on its own, but they share the same metamodel, the same security and the same lineage. That's what avoids gluing together a modeler, a generator, an orchestrator and a quality tool bought separately.
The journey
What happens between a source and a figure
The path is always the same: describe business meaning, integrate sources, control quality during loading, orchestrate processing, publish consumable views, then run it all in your target environment.
What changes from one platform to another is the number of tools you need to assemble to cover this journey — and the integration work that this assembly then imposes, year after year.
The modules
What you manage day to day
- 01
metaVault — Data Vault modeling and automation
Design hubs, links, and satellites in a visual interface. The model becomes the single source of truth: SQL code, loads, and documentation are automatically derived.
- 02
Orchestration
Loads run according to the model's dependency graph: error recovery, parallelism and monitoring included. AWS Step Functions is supported as an external orchestrator.
- 03
Data Quality and MDM
Versioned quality rules, source-based scoring, exception management, and master data reconciliation — integrated into loading, not branched separately.
- 04
Information Marts
Governed business views — dimensions, facts, point-in-time snapshots — fed by the Raw Vault and ready for Power BI, Tableau or Looker.
- 05
Versioning and environments
Models versioned in the Git Store and audited dev → test → production promotions, without rebuilding the warehouse for every change.
Go further
The decisions that follow choosing the modules
Once the features are understood, two questions shape implementation: where the platform runs, and how it's exposed to your applications.
Deployment and sovereigntyThe full REST API and the MCP Server make the platform controllable by your scripts, your CI pipelines and your agents. Source integration and the metadata catalog complete the picture.
API and AI agentsThe perspective
A platform, not a collection
What you don't buy separately, you don't have to integrate or maintain.
Next step