Connecting
Overview
How Parix exposes cluster connectivity today and why the gateway sits in front of TigerBeetle.
Parix keeps TigerBeetle behind a managed gateway path.
Connection model
The current connect flow resolves a database-specific gateway URL from:
- the stored database profile, when available
- a control-plane helper that builds the database gateway URL
That URL is what the dashboard presents to applications.
What this means in practice
- you connect to a Parix-managed endpoint, not directly to provider replicas
- the control plane can keep provider routing private
- request authentication and routing context stay inside the platform boundary
Current access surfaces
Today, the repository exposes two connection styles:
- TigerBeetle client examples through the dashboard connect flow
- gateway HTTP endpoints for provider-routed operations
What it does not expose as a public product surface:
- a public raw TigerBeetle control-plane API
- direct public replica management endpoints
Continue with the Quickstart for the shortest path to a working connection.