DataBP POC
DataBP POC / Next steps

Next steps

Where the POC goes from here, multi-tenant first; each step builds on what is already running.

The POC answers the reconciliation question for one data provider on synthetic data. These are the steps from here to DataBP's platform, in the order we would take them. Each one builds on what is already running; none needs the POC rebuilt.

1. Multi-tenant

DataBP serves many data providers on one platform, and each signed-in user must get only the metrics that user may run, over only the rows of the clients that user may see. The POC already carries the tenant in every key from silver up: the platform's tenant_id and Salesforce's tenant field qualify each subscriber's and product's business key, and the app shows one data provider. Serving all of them follows a design we have worked out, Multi-tenant access: the design (knowledge 111 item 822). The app connects to Snowflake as one service user and stamps each session with the signed-in user, in a session attribute that cannot change. Two maps then decide what the user gets: a metric map, which the app checks before every Semantic Layer query, so Morgan never needs to know it exists; and a row map, which Snowflake's row access policy reads with the stamp, on every query. When nothing is allowed, nothing comes back. If requirements call for label-based security, the same policy can compare a label on each row with the user's clearance. Where a data provider wants the data in its own Snowflake, a secure share per client carries it. It can be added to the POC if needed; the diagram below opens each part.

2. Real feeds

The same platform takes real feeds: one data provider's SQL Server, Salesforce and usage reports in place of the generator. The answer key then comes from the provider's own reconciled months, and the same tests hold the platform to it. Openflow's connector takes the new tables by name; dbt's staging views map their columns.

3. Your BI tool

The app runs in Hex for convenience. In Tableau, the dashboard connects to the same Semantic Layer through dbt's connector, so the 17 metrics, their definitions and Morgan's answers stay exactly as they are; only the dashboard is rebuilt.

4. Since the last close

The checks extend from each month's state to what changed since the last month-end close: usage reports restated after the close, rows deleted at the source, licenses added late. The connector already carries every change and deletion, so the history is there to read.

5. Volume

The generator's second phase adds 200 subscribers, so the platform is measured at a volume closer to a data provider's, with the same answer key method behind every figure.

Entitlement and billing reconciliation

See it running

The live app and Morgan answer from the same governed metrics, on the platform this site describes.