Skip to content
Vaylix logo Vaylix logo Vaylix Docs
Vaylix

A secure, consensus-backed key-value database for operational state.

Technical documentation for operators and integrators working with the current Vaylix release line.

  • Raft-style quorum replication
  • Encrypted WAL and snapshot persistence
  • Authentication and RBAC enabled by default
  • Structured binary protocol (VTP2)
  • Deterministic error codes
  • Production-oriented runtime and recovery path

Minimal example

Terminal window
docker run --rm \
  -p 9173:9173 \
  -v vaylix-data:/var/lib/vaylix \
  -e VAYLIX_USER=vaylix \
  -e VAYLIX_PASSWORD=vaylix \
  ghcr.io/vaylix/vaylix:latest


./vaylix-client --url 'vaylix://vaylix:vaylix@127.0.0.1:9173'


vaylix> set control:epoch 42
OK
vaylix> get control:epoch
42

What Vaylix Is

  • Transport-first architecture with the protocol surface isolated from the storage engine.
  • Deterministic durability through WAL-backed writes, snapshotting, startup validation, and explicit failure on corruption.
  • Explicit failure semantics for protocol, storage, auth, and replication paths.
  • Designed for operational state rather than application data modeling.

Use cases

  • Configuration storage
  • Feature flags
  • Coordination metadata
  • Internal platform state
  • Distributed control planes

What Vaylix Is Not

  • Not a Redis-compatible data-structure server.
  • Not a document database.
  • Not a distributed SQL engine.
  • Not a caching tier.

Architecture Overview

client → transport → server → engine
replication → WAL → snapshot
  • Transport is isolated from the engine and owns framing, negotiation, compression, and request/response encoding.
  • The engine is unaware of authentication and RBAC; those are enforced at the server layer.
  • Replication runs over the main protocol surface instead of a separate side channel.

Guarantees

  • Quorum-backed write acknowledgement.
  • No committed entry is lost.
  • Encrypted persistence for WAL and snapshots.
  • Deterministic startup validation before accepting traffic.
  • Explicit failure on corruption or continuity mismatch.