PostQS
Request a demo
PostQS/Platform/Protocols & Interfaces

Standard interfaces for a modern data platform.

Rather than requiring custom clients or proprietary protocols, EDP exposes standard access mechanisms while maintaining a purpose-built internal execution and security model.

Design philosophy

Protocols are access layers - not signals of internal architecture.

Internal platform behavior remains consistent regardless of how access is performed.

  • Compatibility with existing tools and applications
  • Incremental adoption without rewrites
  • Separation between external interfaces and internal execution
# SQL via standard PostgreSQL drivers import psycopg with psycopg.connect("postgresql://app@postqs.local/app") as c: with c.cursor() as cur: cur.execute("SELECT id, total FROM orders WHERE region=%s", ("EU",)) rows = cur.fetchall() # Same data, columnar, via Arrow import pyarrow.flight as pf client = pf.connect("grpc+tls://postqs.local:8815") table = client.do_get(ticket).read_all()
Drop-in or direct

Two ways to connect. One platform underneath.

Whether you're migrating an existing PostgreSQL application or building a new service from scratch, EDP gives you the right access path - without changing the platform behavior beneath it.

Drop-in

Bring your existing PostgreSQL app. No code changes.

EDP implements the PostgreSQL wire protocol. Your existing drivers, ORMs, and tools talk to it exactly as if it were Postgres - but the data, identity, and execution stay protected by default.

  • One connection-string change - migration done
  • Works with psql, JDBC, psycopg, pgx, ActiveRecord, Prisma, and more
  • Encryption and EnclaveVault apply automatically
  • Side-by-side deployment with legacy databases for incremental cutover
# Same code. Same drivers. New connection string. DATABASE_URL="postgresql://app@postqs.local:5432/app" # Encrypted execution + identity included - nothing to enable.
Native

Skip the wire. Connect directly for maximum performance.

For new applications, the EDP native protocol bypasses Postgres emulation entirely. The application speaks directly to EDP - materially lower latency, lower overhead, and finer-grained access to execution and storage primitives.

  • Materially lower latency than wire emulation
  • Direct access to record references and execution context
  • Streaming-friendly results via the Arrow API layer
  • Same EnclaveVault identity model as every other access path
# Native protocol - no emulation, no translation overhead client = postqs.connect("postqs://app@postqs.local", identity=token) rows = client.execute("SELECT ...", params) transport: native authZ: EnclaveVault
DROP-IN PATH · EXISTING APPS Your App unchanged Postgres Driver standard PostgreSQL Wire emulated by EDP PostQS Core encrypted execution NATIVE PATH · NEW APPS Your App PostQS SDK Direct Native Transport no Postgres emulation in the path PostQS Core encrypted execution
All interfaces

Familiar at the edge. Distinct underneath.

Every interface routes to the same encrypted execution engine, under the same EnclaveVault identity model.

PostgreSQL wire protocol

For drop-in compatibility. Standard SQL clients, drivers, ORMs, and ops tools connect to EDP exactly as they would to Postgres - no code changes required.

Native direct protocol

For new applications. Skip the emulation layer and talk directly to EDP - materially better performance, with the same trust model and identity guarantees.

Apache Arrow API

Columnar data access, efficient interchange for analytics, streaming-friendly result delivery, reduced serialization overhead. (Planned.)

Admin & service APIs

Administrative operations, automation, and service-to-service communication - all enforced under the same EnclaveVault identity model.

Local & distributed communication

Inter-component comms follow the same trust and authorization rules as external access.

  • Shared-memory transport for same-node components
  • Encrypted RPC for distributed deployments
  • Identity-aware at every hop
Stability & evolution

Existing protocols stay stable. New ones live alongside.

Compatibility is preserved across platform updates so the platform can grow without forcing disruptive changes.

Designed for adoption

Practical to introduce. Modern at the core.

EDP supports gradual migration from existing systems, side-by-side deployment with legacy databases, and use of familiar tools and workflows.

Migrate gradually

Use existing drivers and tools while adopting EDP step by step.

Run side-by-side

Deploy EDP alongside legacy databases for incremental cutover.

Keep your tooling

Standard SQL, drivers, ORMs, and analytics tools work as expected.

Standard at the edge. Purpose-built underneath.

Detailed protocol specifications and integration guides are available under NDA and appropriate authorization.

Talk to us Read the architecture overview