FAQ

FAQ

The questions database reliability engineers raise in design reviews — expanded with the concrete failure modeswe've watched unfold in production. Postgres self-healing scope, MTTH methodology, comparisons to Patroni, pg_auto_failover, and the Zalando operator, multi-engine roadmap, audit retention, deployment model, security posture, and commercial pricing.

Can't find your question? Email us.

Become a Design Partner

Or write directly to veritas-2-2@polsia.app.

What does Veritas actually self-heal inside Postgres?

How do you measure MTTH and why is it different from MTTR?

"How is Veritas different from pg_auto_failover or Patroni?"

How does Veritas compare to the Zalando Postgres operator?

"Which database engines does Veritas support today?"

How long is the autonomous-action audit trail retained, and what does "tamper-evident" mean?

SaaS vs BYOL — which deployment model fits my org?

What is Veritas’s security & compliance posture?

How does Veritas price — per cluster, per node, per incident?

"How does Veritas keep failover safe under split-brain?"