Operational truth, component by component.

The reliability boundary

PostgreSQL remains the transactional source of truth. ClickHouse receives append-only, redacted operation events through a non-blocking queue. If ClickHouse is slow, restarting, full, or unavailable, the API continues from PostgreSQL and may drop derived events instead of delaying the customer response.

Signals and escalation

A watchdog outside the ClickHouse machine evaluates availability, backup freshness, disk and memory pressure, sustained CPU, active parts, read-only disks, and asynchronous-insert failures. It sends bounded firing, resolution, and reminder messages to the private operator Slack channel. This page receives only the sanitized component state—never account, project, request, machine, credential, command, file, path, payload, or user identity data.

Current verified state

• Private staging passed its bounded API checks on July 28, 2026. That dated proof is not presented as continuous availability.
• The website contract is synchronized to backend sourceef8d9b2ff8ebd0ed16544e1fce09464d9d9d7e91 and OpenAPI 0.8.0.
• The self-managed ClickHouse and watchdog deployment sources are validated locally but have not been deployed.
• Production infrastructure and public signup are not active.

Report safely

For product or security help, follow the support guidance and share only safe request or operation references. Never send credentials, tokens, commands, file contents, paths, provider payloads, or sandbox output.