Skip to main content
Platinur is a single-tenant Docker Compose stack. The control plane is the operator UI and API. The worker performs source loading, dbt runs, Evidence rebuilds, assistant validation, and Prefect orchestration work.

​
Runtime services

  • Control plane: FastAPI web app, portal UI, API, metadata, settings, promotions, and run summaries.
  • Worker: dlt source actions, dbt execution, Evidence rebuild calls, Assistant runtime, and bounded tools.
  • ClickHouse: source and analytics runtime.
  • dbt Core: transformations from selected source schemas into staging, warehouse, and marts layers.
  • Evidence: dashboard project and preview service.
  • Prefect: runtime scheduling and operational workflows.
  • GitHub: governed promotion boundary between Staging and Prod.
  • OpenAI Platform: Assistant and Initial Run generation.

​
Source-to-production path

  1. Data lands in ClickHouse through Platinur Integrations or an external customer process.
  2. The operator selects schemas and tables in Operations.
  3. Initial Run generates a validated dbt proposal in Staging.
  4. The proposal is applied to the staging workspace and branch.
  5. dbt and Evidence validate the staged work.
  6. Promotions creates a GitHub PR from the staging branch to the production branch.
  7. After merge, production runs use the configured production branch as source of truth.
  8. Monitoring records runs, failures, and audit activity.

​
Metadata model

Platinur stores product-owned metadata in the portal database: users, sessions, audit events, source state, run summaries, proposals, validation status, promotion state, and compact references to external artifacts. Detailed tool artifacts remain owned by dbt, Evidence, Prefect, GitHub, and ClickHouse.