Frequently Asked Questions

Prodegy Vault is a security platform for governed secrets and secure data workflows across Prodegy Vault, Legal Vault, Family Vault, and Credentials Vault.

It combines zero-knowledge data protection with blockchain-verifiable audit integrity for confidence in both confidentiality and accountability.

Sensitive payloads are encrypted client-side before storage. The service stores ciphertext and governance metadata, not plaintext secrets.

This design reduces insider risk and protects customer confidentiality even during infrastructure-level incidents.

Critical workflow events are transformed into deterministic hashes and anchored as integrity proofs.

This allows independent validation that audit evidence has not been altered after creation, strengthening forensic and compliance defensibility.

Prodegy Vault: enterprise secrets, API keys, service credentials, governance controls.

Legal Vault: matter workspaces, protected legal records, retention and evidentiary workflows.

Family Vault: secured family continuity documents with emergency and trustee-oriented controls.

Credentials Vault: credential lifecycle operations, bulk ingestion, rotation campaigns, and break-glass controls.

Yes. Product-line registration maps users to relevant menus, routes, and workflows so the UI stays focused on the vault experience they selected.

Yes. Teams can integrate using API keys, REST endpoints, automation hooks, and environment-based runtime retrieval patterns.

This keeps secrets out of source code and enables controlled secret usage across build, deploy, and runtime phases.

Access requests can be submitted, approved, or rejected through governed workflows with full audit capture.

Approval decisions and state transitions are logged and can be included in integrity verification flows.

The platform is built with compliance-oriented controls including policy enforcement, retention governance, and tamper-evident audit posture.

Data residency and deployment models can be aligned to regional and organizational policy requirements.

Yes. It is designed for high-scale enterprise operations with role-based access, workflow governance, observability, and integration readiness.

Start with a product-line-focused pilot (for example Credentials Vault or Legal Vault), onboard a single team, and validate governance flows, audit verification, and operational rollout before wider deployment.