Browse this guideOperate the Provenience platform
For the platform operatorUpdated 2026-10-01

Operate the Provenience platform

This page is for Blue Data Works as the platform operator. The Registrar is not a customer tool, and businesses using Provenience do not provision Sites, manage releases, or monitor the fleet. Their administrators manage projects, rosters, categories, and the Review Queue instead.

The Registrar and Sites

A Site is the infrastructure serving one customer business. Blue Data Works operates that infrastructure. The Registrar will be the fleet control plane for provisioning and decommissioning tenant Sites, moving them through releases, and showing their health, resource use, errors, and running cost.

Each tenant is designed to receive a complete Site stack rather than a tenant key inside one shared application database. The Registrar keeps control-plane facts and vendor identifiers; it does not hold tenant project content or become a proxy for normal Site traffic.

Platform-operator workflows

Phase 1 is display-first. The Registrar will report fleet health and cost without auto-remediating or auto-scaling. It will send email for a short list of binary failures: a Site going down, a failed decommission, a halted release, a halted model canary, or a configured ingestion channel going silent.

Provisioning and decommissioning are workflows triggered by the platform operator. Destructive steps are designed to be explicit, auditable, and resumable rather than hidden inside a dashboard action.

What exists today

The repository currently contains the first local Site substrate: Postgres in Docker Compose and a composite Site health endpoint that reports database connectivity and the outcome of the Deposit token provider's last Auth attempt. The Registrar itself is not implemented.

For customer workflows, see how Provenience works.