Skip to content

Document billing overlap and instance fallback in Postgres pricing #6282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Blargian merged 1 commit into from
May 26, 2026
+2 −0
Merged

Document billing overlap and instance fallback in Postgres pricing #6282

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/cloud/managed-postgres/pricing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,4 +126,6 @@ As the product evolves during Beta, pricing and packaging may be refined ahead o
- Network egress pricing will be introduced after GA. Applications colocated with the database are expected to incur minimal egress costs.
- Additional backup charges may apply at GA for retention periods beyond a limit that is still being defined.
- We expect Native CDC via ClickPipes to remain free or minimally priced at GA when Postgres and ClickHouse are colocated in the same region, aligning with the vision of a unified OLTP + OLAP platform.
- Scaling, failover, and standby provisioning briefly run two instances in parallel to keep your database online — you may see overlapping charges for both instances while the transition completes. The duration of this window varies based on instance type and storage volume.
- When your selected instance type is temporarily unavailable in the chosen region, we may provision a comparable instance type to keep your database online. You will be billed at the rate of the provisioned instance.
- Existing pricing may evolve and be subject to change closer to GA as we learn more about real-world customer usage patterns, workload characteristics, and infrastructure requirements during the Beta period.
Loading