Governance your platform team will actually sign off on.
Quality gates enforced inside the Spark run, contracts that block bad schema before it burns compute, and an audit trail behind every action. Compliance as a property of the pipeline, not a spreadsheet.
Quality gates, in-engine
Nine rule types — uniqueness, not-null, accepted values, regex, freshness and more — enforced inside the Spark run itself, with a structured per-rule report on every run, pass or fail.
Data contracts & drift radar
The schema-drift radar continuously diffs pipeline expectations against the live source. Contract gates block a run before it spends compute when the upstream schema breaks.
SSO & role-based access
OIDC with PKCE, JWKS validation and group-to-role mapping. Admin, operator and viewer roles with project-scoped memberships — one identity provider, least-privilege by default.
Encrypted secrets
Connection credentials are encrypted at rest with AES-256-GCM and masked in every API response, log line and audit record. Nothing is stored or shown in the clear.
An audit trail you can hand over
Audited execution, security, identity and configuration actions record who did what per tenant on a hash-linked ledger. The in-app posture reports audit coverage and the scheduled verifier keeps its latest chain verdict. Read the governed window in the app, or stream it to a SIEM sink you configure.
Git release artifacts
A pipeline version is promoted as a reviewable Git artifact: the manifest, the contract gates it passed and the metadata needed to roll it back. Where a repository and a token are configured, the platform can open the review branch for you; where they are not, it prepares the artifact and hands you the exact command — it never claims a merge it did not make.