Installation guide
Deployment guide
Bring an in-house HTQLDB cluster into production, step by step.
Enterprise access required
Before you begin: the cluster's release notes give the exact versions and commands for your release; System requirements lists what each node needs.
Size and prepare each node
Compute and memory sized for your workload, persistent and durable storage, a backup policy with its retention, and a private network with outbound access.
Download and verify the package
Download the approved release for your account and compare its checksum with the one published with the release before you install it.
Install the cluster on each node
Every node runs the HTQL engine on PostgreSQL 18, inside your security boundary.
Register the nodes with the Control Plane
Each node receives its identity and keys from the Control Plane, which manages the cluster.
Configure secure connectivity
Keep the database nodes private. Nodes reach each other over mutual TLS, and the cluster reaches out through Cloudflare Tunnel, so no inbound port is opened.
Join the peers
Peers replicate committed business events to each other over mutual TLS.
Open the gateway to your applications
Applications reach HTQLDB only through its governed gateway, signed in as a person or as an app; nothing connects to the database directly.
Validate before production
Check that replication keeps the nodes in sync, that a node recovers its service and data, and that only authorised users and systems have access. Then sign in with the HTQL CLI (
htql login) and send a first statement.