Security as a core platform property - not a layer on top.
Protection, identity, and execution integrity are built into the core operation of the platform, shaping how data is stored, accessed, and processed from the outset.
Designed around modern operating realities.
Rather than relying on perimeter defenses or inherited trust, our products treat security as a core, platform-level responsibility.
Continuously accessible
Systems are continuously accessible.
Distributed
Environments are distributed.
Fluid trust boundaries
Trust boundaries are fluid.
Anticipated compromise
Compromise must be anticipated.
No separate "secure mode." No optional configuration.
Security behavior is consistent across environments and workloads.
- Data is protected as part of normal operation
- Identity and access are always enforced
- Execution does not assume trusted memory
- Persistence remains protected across memory and storage
Enforced by EnclaveVault - explicit and intentional.
- Identities are defined natively
- Authentication and authorization evaluated internally
- Access policies apply consistently across execution and storage
- External identity systems are not part of the trust model
Reduce the attack surface of long-lived plaintext.
EDP is designed to limit unnecessary data exposure during execution.
- Execution operates on protected data representations
- Intermediate results are minimized and constrained
- Access checks are evaluated as part of execution flow
Protected state - preserved through restart and recovery.
Recovery processes restore platform state without altering execution or security semantics.
- In-memory execution
- Write-ahead logging
- Persistent storage
Limit the impact of individual failures. Avoid single points of trust.
Platform components communicate using secure, controlled mechanisms. All communication is subject to identity and authorization rules enforced by EnclaveVault.
Same-node isolation
Shared-memory transport between local components, identity-aware.
Distributed isolation
Encrypted channels between distributed components, same trust model.
Threat awareness
Designed against unauthorized access, misconfiguration, compromise, and exposure.
Public concepts. Detailed materials under NDA.
PostQS balances transparency with responsible disclosure. Public materials describe security concepts and architectural direction at a high level. Detailed threat models, internal mechanisms, and implementation specifics are provided under NDA and appropriate authorization.
Request technical materialsDesigned to evolve. Designed to keep its guarantees.
Our products are designed to evolve over time, adapt to new threats, and maintain consistent guarantees across updates.
A security model designed together with the rest of the platform.
Detailed security documentation is available under NDA and appropriate authorization.