Beyond raw billing export data, Stack Dyno benefits from lightweight lookup tables that translate project IDs into ownership, lifecycle stage, and margins.

Recommended lookup tables

ETL flow

1. Source metadata from your CMDB or spreadsheets.
2. Load into a staging table (CSV imports work fine).
3. Merge into the canonical dataset with simple SQL.

MERGE `my-project.stackdyno_metadata.projects` AS target
USING `my-project.tmp.projects_staging` AS src
ON target.project_id = src.project_id
WHEN MATCHED THEN UPDATE SET
  business_unit = src.business_unit,
  env = src.env,
  product = src.product
WHEN NOT MATCHED THEN
  INSERT(project_id, business_unit, env, product)
  VALUES(project_id, business_unit, env, product);

Consuming inside Stack Dyno

• Update frontend-user/src/state/FrontendUserDataContext.tsx to enrich the dataset before rendering.
• Mirror the logic in frontend-reseller so both apps stay in sync.
• Surface missing metadata (e.g., unlabeled projects) as checklist items in the docs so teams know how to help.

Once the lookup tables land, screenshots, alerts, and dashboards all reference the same friendly naming conventions.