Home Expressions
Docs
Rust Docs QAIL PG (Rust) Zig Docs QAIL Zig
Drivers Gateway SDKs Benchmarks
Changelog
Rust / Workspace qail.rs and workspace releases Zig qail-zig release track
GitHub
Rust / Workspace github.com/qail-io/qail Zig github.com/qail-io/qail-zig
Blog Status Roadmap
Database Protocols

Native PostgreSQL Drivers

Direct protocol-level runtimes for Rust and Zig. Designed for intense concurrency, raw throughput, and zero-overhead database interaction. For HTTP API gateways and SDKs, visit their dedicated pages.

High Performance QAIL Rust QAIL Zig Protocol 3.0+
Rust Docs Zig Runtime
Zig

QAIL-Zig Zig

Pure Zig PostgreSQL driver

Standalone Zig runtime with its own docs, changelog, benchmark write-up, pooling, TLS, COPY, and parity tracking against the Rust platform.

Rust

QAIL-Rust Rust

Rust PostgreSQL driver

Mature Rust runtime surface with protocol negotiation, pipeline execution, COPY paths, pooling, and the shared-core platform context.

Driver Pages

  • /zig - Zig runtime landing page with current benchmark and capability status.
  • /zig/docs - dedicated Zig docs book for install, hardening, parity, and API reference.
  • /zig/changelog - Zig-only release history.
  • /rust - dedicated Rust PostgreSQL driver page (qail-pg).
  • /zig/benchmarks - current qail-zig versus pg.zig benchmark report with the five-workload shared-surface matrix.
  • /benchmarks - unified benchmark index and methodology pages.
  • Protocol 3.2 + PostgreSQL 18.3 blog - operations and protocol context.

Related Surfaces

  • /gateway - AutoREST, OpenAPI, auth policy, and realtime runtime surface.
  • /sdk - TypeScript, Swift, and Kotlin client SDKs.
  • /qdrant - Qdrant vector runtime for filtered AST search.

Driver Rollout Tips

  • Choose /zig when you need a pure Zig runtime. Choose /rust for the mature Rust driver path with protocol negotiation, pipeline, and COPY operations.
  • Treat /drivers as the PostgreSQL runtime index only. Use /gateway for API runtime concerns and /sdk for client SDK integration.
  • Use /qdrant for the vector runtime; it is a separate surface from direct PostgreSQL drivers.
  • Verify methodology at /zig/benchmarks and use /benchmarks for the unified benchmark index.
  • Track release movement through /changelog and /zig/changelog before adopting changes in production.