Procela connects to the databases, warehouses, and transformation tools you already run — building a governed catalog from metadata alone, without ripping and replacing what's working.
Your databases, warehouses, and transformation tools stay where they are. Procela sits alongside them — reading schema, table, and column metadata to build a single governed catalog, and complementing the sources you already run.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans schema, table, and column metadata to build a governed catalog — audit-only, no data moved.
Scans collection and field metadata to build a governed catalog — audit-only, no data moved.
Reads model, source, and lineage metadata from dbt and dbt Cloud to enrich the governed catalog — audit-only, no data moved.
For on-prem databases, the edge connector runs inside your VPC or data center and pairs to Procela with a one-time code — no inbound ports. It reads schema, table, and column metadata plus row counts — never values — and sends only that metadata over outbound HTTPS with a bearer token. Cloud warehouses connect directly, reading the same catalog metadata. No column values, no records, no file contents ever leave your perimeter. Procela runs on AWS (ECS/RDS) or fully on-prem via Helm and Kubernetes.
Bring your sources — we'll show you how the edge connector builds a governed catalog from metadata alone.