Getting Started

Getting started with Fraxses usually begins with one question: which data should be made easier to discover, govern, and reuse?

1. Connect Sources

Fraxses is designed to connect data from multiple systems into a shared governed environment. A source might be a transactional database, a warehouse, a SaaS API, a flat file, or another operational platform.

The goal is not to move everything immediately. The goal is to make source data addressable, understandable, and governable through metadata.

2. Describe the Metadata

Metadata gives Fraxses its operating model. It captures what a source is, what fields mean, how access should work, and how a dataset should be presented to users.

Good metadata helps teams answer practical questions:

• Where does this data come from?
• What business concept does it represent?
• Who can access it?
• Is it virtual, cached, transformed, or materialised?

3. Create Data Objects

Data Objects are reusable virtual representations of data. They can describe a stable business concept, such as a customer, asset, policy, invoice, account, or transaction, even when the underlying data is spread across systems.

Start with a small number of useful Data Objects. Prefer high-value definitions that remove repeated work or make governed access easier.

4. Govern Access

Fraxses brings source connections, Data Objects, and policies into one environment. That lets teams manage access at the platform layer while still respecting the realities of the underlying systems.

5. Publish for Use

Once a Data Object is defined and governed, it can be made available for downstream use. Depending on the use case, that might mean exploration, API access, operational workflows, analytics, or future materialisation.

---
title: Customer Data Object
description: A governed virtual representation of customer records.
---

Use this page to explain the object, its source systems, and its access model.