Strategic position

One platform the entire group works in — every country, every team.

Governance, risk and the business work one record — over the repositories you already run, or new ones FluenBox deploys.

One platform, many workspaces

A workspace is the unit of separation.

A country, a business unit, a legal entity. Group functions get their own. The structure below is illustrative — map your own onto it.

The organisation · multi-country, multi-business-unit · illustrative structure

Group

Group functions · 1 workspace

United Kingdom

3 business units · 3 workspaces

Spain

2 business units · 2 workspaces

Mexico

2 business units · 2 workspaces

Brazil

2 business units · 2 workspaces

Singapore

1 business unit · 1 workspace

Illustrative group structure. FluenBox does not publish or imply any named client architecture.

Reported in by API

Your pipelines and quality tooling keep running.

We do not take over your orchestration. Work executed outside FluenBox reports in, so the platform holds the status of work it never ran.

Job & pipeline runs

Every run outside FluenBox reports its status, timing and outcome.

Data-quality results

Checks executed in your own tools land here as standing evidence.

Platform & asset events

Schema and asset changes arrive as they happen, by API.

One record · every workspace

The marketplace — where nobody emails anyone for a dataset.

Every governed object is published with its owner, its maturity score and its evidence attached. Access is requested there, reviewed by the owner, and logged.

The Marketplace

Request access
Data products
Glossary terms
Critical data elements
Reports & dashboards
Access is requested, reviewed by the owner, and logged as evidence. That request trail is itself evidence.
Where the data lives

Two paths, and either one works.

The question a group CIO asks first. Both answers are available, and neither is a blocker.

Either

Connect what you already run

Point FluenBox at an existing lake, warehouse or database — Redshift, Snowflake, Databricks, S3, on-premise. Nothing is moved or copied.

Or

Have a new one deployed

No repository yet? FluenBox provisions a lake per workspace, in your own AWS account, governed from the first day it exists.

One account per workspace

Residency and separation are structural rather than a setting — the boundary is an account boundary, not a filter in a query.

No migration prerequisite

A mature estate does not have to migrate to buy this, and an immature one does not have to build a lake first.

Self-hosted and air-gapped

For estates that cannot reach the internet at all, FluenBox runs fully isolated — the knowledge it reasons over is stored locally and self-contained.

How subscriptions are isolated from each other

Map it onto your own group.

Tell us your countries, your business units and where the data sits today — we will show you the workspace model against it.