PostQS/Platform/Enclave Data Platform
EDP

SQL execution and secure storage - reimagined.

A general-purpose data platform that integrates encryption, identity, and execution into the core behavior of the system - instead of treating them as separate layers.

What EDP is

A relational engine designed around a different set of assumptions.

Familiar SQL workflows, on protected data representations by default.

  • Relational SQL execution engine
  • Persistent, encrypted storage model
  • Native enforcement of identity and access
  • Distributed and multi-container deployments
# Standard SQL - encrypted execution stays the default postqs=> SELECT id, status, total FROM orders WHERE region = 'EU' AND created_at >= '2026-01-01'; rows: 2,418 plan: in-memory, record-ref authZ: enforced by EnclaveVault storage: encrypted
Execution model

Operates on protected data representations - not on broad plaintext.

Execution stages work over record references and metadata. Intermediate results are minimized. Access checks are evaluated as part of execution flow.

Record-referenced execution

Relational operators propagate identifiers rather than materialized rows.

Minimized intermediates

Reduces unnecessary data movement while preserving SQL semantics.

Authorization in-line

Access checks evaluated as part of execution - not bolted on afterward.

Storage

In-memory-first, with persistent encrypted state.

Persistence is achieved through coordinated use of encrypted memory structures, encrypted write-ahead logs, and encrypted blob-based storage. Storage behavior is configurable without altering execution semantics or security guarantees.

  • Encrypted memory structures
  • Encrypted write-ahead logs (WALs)
  • Encrypted blob-based storage
  • Deterministic behavior across restarts
RUNTIME In-memory execution ยท record references ENCRYPTED MEMORY Working set held in protected memory structures ENCRYPTED WAL Durability without altering execution semantics ENCRYPTED BLOB STORAGE Adaptable to deployment without changing guarantees Same architectural guarantees across configurations
Index-free design

Predictable behavior across encrypted datasets.

EDP does not rely on traditional secondary index structures. Records are addressed through deterministic references; relational operators propagate identifiers rather than materialized rows.

  • Reduced index maintenance overhead
  • Deterministic record references
  • Consistent execution across encrypted state
Access control

Identity enforced by EnclaveVault - across execution and storage.

All access to EDP is enforced through EnclaveVault. Identities are defined natively, authorization is evaluated internally, and access policies apply consistently across execution and storage.

Read about EnclaveVault
Interfaces & integration

Standard interfaces. Purpose-built execution.

Connect with familiar tools. Internal execution remains distinctly PostQS.

Drop-in PostgreSQL wire

Point an existing Postgres app at EDP - your standard clients, drivers, and tools connect without code changes.

Native direct protocol

For new applications, talk directly to EDP - materially better performance and direct access to execution primitives.

Apache Arrow API

Columnar interchange for analytics and pipelines (planned), alongside SQL and native access.

Bring SQL to a platform built for how data is actually used.

Talk to us about pilots, integrations, and detailed materials available under NDA.