Gateway

The gateway is the bridge between Parix routing and native TigerBeetle client operations.

Responsibilities

tb-gateway currently handles:

• provider-routed HTTP requests from Cloudflare-side services
• request validation and signed-header checks
• target resolution for TigerBeetle cluster access
• translation from HTTP operations into TigerBeetle client calls

Private routing path

The request path is:

1. Cloudflare-side caller sends the request.
2. app-dispatcher resolves the target provider route.
3. Workers VPC bindings send traffic through tb-tunnel.
4. tb-tunnel routes private HTTP traffic to tb-gateway.
5. tb-gateway performs the TigerBeetle operation.

Current modes

The gateway supports two write modes:

• stub: validates the request and returns a structured non-persistent success response
• live: performs real TigerBeetle writes through the Node client module

Current endpoint families

The public API surface exposes TigerBeetle operations through:

• POST /api/v1/databases/{databaseId}/tb/{operation}

Supported operations are:

• query_accounts
• query_transfers
• create_accounts
• create_transfers
• lookup_accounts
• lookup_transfers
• get_account_balances
• get_account_transfers

The provider gateway also has private health, ping, tenant, and signed internal provider routes. Those are operator infrastructure, not the public application API.

For header and endpoint details, see API reference.