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

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 FAQ

How do I choose between /zig and /rust for PostgreSQL?

Pick /zig for a pure Zig runtime path. Pick /rust for the mature Rust driver path with protocol negotiation, pipeline, and COPY operations.

Are gateway and SDKs part of the driver page now?

No. /drivers is now reserved for direct PostgreSQL runtimes only. Use /gateway for API runtime concerns and /sdk for client SDK integration.

Where should I go for Qdrant?

Use /qdrant for the vector runtime. It is a separate runtime surface and is not part of the direct PostgreSQL driver index.

Where do I verify benchmark methodology before rollout?

Use /zig/docs/benchmarks.html for the current qail-zig benchmark snapshot and /benchmarks for the unified benchmark index and methodology pages.

How should I follow release changes across the driver lines?

Track /changelog for workspace-level chronology, then use /zig/changelog for the Zig-specific release track and the dedicated driver pages for current details.