Procela was designed for organizations where data can't move and every action has to be accountable — defense, financial services, healthcare, and critical infrastructure.
The Procela edge connector runs inside your environment and sends only metadata to the platform. Source data stays put — making Procela suitable for the most restricted environments.
The connector deploys via Kubernetes or Helm and reads schema, table, and column metadata where the data lives — never row values. It authenticates with a bearer token over outbound HTTPS and carries a tamper-evident audit log of everything it does.
Classifications, assignments, and policy changes are captured in an append-only trail tied to a named principal — human or AI — so audits become a query.
The principal model scopes exactly what each steward, owner, and agent may do. AI agents operate under review-gated controls, so proposed changes are approved before they take effect.
Single sign-on via OIDC or SAML, SCIM provisioning, multi-factor authentication with passkeys (WebAuthn), and role-based access across five tiers. Connector credentials and other secrets are encrypted at rest.
Procela's architecture — no data egress, an edge connector over outbound HTTPS, and tamper-evident audit trails — is designed to support governance programs operating under frameworks like:
Creates, updates, and deletes across the program are captured in a tamper-evident log — the answer to who changed what, and when.
Procela surfaces ownership gaps, ungoverned assets, and coverage holes across your program — so you can close them proactively.
We'll walk your security and compliance teams through the deployment model and controls.