Does multi-region always mean RPO zero?

No. Read replicas in a second region do not make writes survive. RPO zero needs consensus (or equivalent) on the write path.

Why does a write take longer on paid plans?

Cross-region consensus pays a speed-of-light tax. Geo-partitioning keeps most consensus local. We still tell you the tax exists.

Reliability

Multi-region explained

Multi-region is three different promises. DNS can send people to a healthy edge. Compute can run the app in more than one place. Data can accept writes in more than one place. Briovela uses multi-region compute for the application. Only paid plans use multi-region writes. If a marketing page says “multi-region” without saying which layer, ask which writes survive. That is the question this page answers.

Last updated 2026-09-10

Compute can move. Writes have to already be somewhere else.

Pinning rows to a home region

Most small businesses do not need a write in Arizona to wait on a replica in Europe. Paid topology can pin a tenant’s rows to a home region so consensus is usually nearby, while still surviving a region loss.

FAQ

Questions this page answers

Does multi-region always mean RPO zero?: No. Read replicas in a second region do not make writes survive. RPO zero needs consensus (or equivalent) on the write path.
Why does a write take longer on paid plans?: Cross-region consensus pays a speed-of-light tax. Geo-partitioning keeps most consensus local. We still tell you the tax exists.

Back to the pillar, the Security & Trust pages, or Product.

Launching 2026. Get Notified.

Stay Updated, or Apply to become a Founding Client.

Stay updated Apply to be a Founding Client