System Features
Secure Phased Execution & Air-Gapped Trust Boundaries
Secure Phased Bootstrapping & Multi-Layer Unlock
Caedist never ships with vault infrastructure or any default passwords. It will not operate without verified cryptographic identities. Separate certificate identities are required to unlock the System and User vaults. The database connection string must be retrieved from the unsealed vault before the application can start.
Hexa-Vault Architecture
We employ a distributed 6-Vault architecture to keep our strict promise never to store secrets in code or environmental variables. This includes 2 separate vaults dedicated to PKI (Root and Intermediate CAs). We use separate vault infrastructures to enable you to guarantee the same strict confidentiality boundaries to your customers. Zero secret cross-contamination is enforced. While not strictly required, deploying Vault for Caedist is significantly accelerated (taking 4–8 minutes instead of up to 6 hours) by using the Caedist Vault Description Language (CVDL).
Assume Breach Fail-Closed Model
Authentication to your development environment is strictly managed via Caedist identities backed by Auth0. Full system traceability is integrated at the file system level. All changes run through a Virtual File System with cryptographic change management and supply chain risk logging.
Local Inference & MCP Isolation
We enforce local inference by default to protect proprietary data. External inference requires explicit ACL registration. Caedist completely refuses requests from traditional MCP and logs them as malicious activity. Includes software bill of materials (SBOM) scanning, LLM Guard against prompt injection, and antivirus checks on all input surfaces.
Opaque Command Execution & Stasis
No direct shell execution or direct file system access is allowed. Commands are parameters. The system returns no feedback on command success or failure to prevent side-channel leaks. All commands are pre-assessed for harm against Confidentiality, Availability, and Integrity, and remain in stasis until approved by a human.
Non-LLM Core & Database Isolation
The main orchestrator is a deterministic, rule-based program that cannot be socially engineered by LLMs. All entities operate under strict access control lists (ACLs). LLMs have no awareness of the database schema or access paths, and possess absolutely zero CRUD access to the storage layer.