VARUX AXIS Deterministic PostgreSQL Write-Path Control
v0.6 · Pilot Readiness
AXIS Documentation / Security / mTLS & Network

mTLS & Network

Partial — mTLS not completedPorts 6543 / 5432 / 3000

The v0.6 pilot runs over HTTP on the trusted lab network. TLS configuration variables exist; a complete, reviewed mTLS story is a documented production requirement, not a shipped feature.

Topology

Application HTTP :6543 (POST /query) plaintext in pilot AXIS Gate LISTEN_ADDR :6543 pgwire lab :6544 (disabled) API PostgreSQL :5432 · axis_executor protected target pool Control Plane :3000 (Next.js) server-side proxy /api/axis/* Operator browser https / localhost http never holds backend URL or token Direct DB client :5432 (bypass) must be closed by deployment Protection boundary: AXIS controls the HTTP write path and (lab) the wire path. It cannot control credentials or networks that bypass it.
Pilot networking: HTTP API on :6543, PostgreSQL on :5432, Control Plane on :3000; direct :5432 access is the documented bypass to close.

Ports and listeners

PortOwnerPurpose
6543AXISHTTP API (LISTEN_ADDR, default 0.0.0.0:6543)
6544AXIS pgwire labNative wire listener, disabled by default (AXIS_PGWIRE_ENABLED=false)
5432PostgreSQLProtected database (DB_HOST/DB_PORT)
3000Control PlaneOperator UI; proxies /api/axis/*
6545AXIS (prod-like)Production-like instance in the extended demo stack
65430 / 54320Reviewer stackAXIS + PostgreSQL for the reviewer/demo environment

TLS variables

VariableDefaultNotes
AXIS_TLS_ENABLEDfalseMaster TLS switch; false in the v0.6 pilot
AXIS_TLS_CERT_PATH / AXIS_TLS_KEY_PATHCertificate and key file paths
AXIS_TLS_CA_PATHClient CA for mutual TLS validation
AXIS_TLS_REQUIRE_CLIENT_CERTfalseRequire and validate a client certificate (mTLS)
AXIS_TLS_MIN_VERSIONMinimum TLS version (e.g. 1.2)
PGSSLMODE-related / DATABASE_URL optionsAXIS → PostgreSQL connection security; not part of the complete v0.6 story

mTLS status

ItemStatusDetail
Server TLS on AXIS listenerPartialVariables exist; not validated in the v0.6 pilot
Client certificate (mTLS) enforcementPartialAXIS_TLS_REQUIRE_CLIENT_CERT exists; complete mTLS review pending
Control Plane HTTPSImplementedProduction mode uses HTTPS; pilot runs HTTP on localhost
AXIS → PostgreSQL TLSPartialVariables exist; not part of the complete v0.6 story
Production mTLS requirementRequiredDocumented review gate: mTLS between AXIS and clients before production

Control Plane proxy details

The pilot runs on a trusted lab network over HTTP. For any production use, complete the mTLS and TLS-to-PostgreSQL review gates first.

Related: Security Model · Deployment · Security Review