Overview

Parix keeps TigerBeetle behind a managed gateway path. Use this page to understand what your application connects to before choosing a client or API integration.

Connection model

The connect flow resolves a database-specific gateway route from:

• the stored database profile, when available
• a control-plane helper that builds the database gateway URL

The public application boundary is the Parix API. Provider-local gateway addresses remain private infrastructure.

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

The repository exposes two connection styles:

• client examples through the dashboard Connect page
• HTTP TigerBeetle operations through /api/v1/databases/{databaseId}/tb/{operation}

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.