TigerBeetle compatibility
Current Parix support boundaries, provider constraints, and product limitations.
This page documents Parix compatibility as implemented in this repository. It is not an exhaustive upstream TigerBeetle feature matrix.
Access model
Product compatibility assumes:
- gateway-only access to TigerBeetle operations
- no broad public raw TigerBeetle network access
- provider-aware routing through Parix infrastructure
Provider support
The repository centers on AWS and GCP provider paths.
Productized surfaces include:
- AWS-backed cluster workflows
- GCP-backed cluster workflows
- manual backups for active AWS and GCP profiles
- restore from eligible completed backups
- parameter changes for GCP deployments
Current limitations
Operators should assume these limitations unless a page says otherwise:
- no cross-region replication or multi-region HA
- no broad public control-plane REST API
- no point-in-time recovery workflow
- no dedicated shipped Parix CLI binary
Restore from backup is available only when the selected backup passes the current eligibility checks. See Backup and restore for those constraints.
Change visibility
The cluster Changes tab is derived from durable control-plane state, not from every workflow event.
You should expect visibility for:
- CDC changes
- cluster shape changes
- storage changes
- TigerBeetle version upgrades
- applied cache-grid overrides
- initial cluster creation fallback rows
You should not expect full historical visibility for:
- direct-connect toggle history
- provider or region migration history
- workflow-only events that never materialize into durable state
Compatibility guidance
If you are designing around current behavior:
- treat the dashboard and docs as the product contract
- treat unsupported areas as unavailable, not implicitly coming soon
- assume gateway and workflow orchestration are part of the platform boundary