> Quotas, what suspension looks like, and the features we have not built yet. # Limits and what is not here | | Default | |---|---| | Branches per project | 10 | | Compute | 0.25–4 CU, autoscaling | | Compute per month | 200 CU-hours | | Size, per branch | 10 GB | | Restore history | 7 days | | Postgres | 18 | | Idle timeout | 5 minutes | | Maintenance window | Mondays, 01:00–02:00 UTC | Every one of these is per project and raisable. They exist so that a runaway query loop is a suspended database rather than a surprise invoice — for you as much as for us. ## What happens at a quota The compute is suspended until the next billing period, or until the limit is raised. **Your data is untouched**, connections are refused, and the studio says so. That is the same mechanism used if an account is suspended for non-payment, and it has the same property: nothing is destroyed and nothing needs re-deploying when it is lifted. Your connection string still works the moment it is. ## Rate limits The API — one endpoint, [connection details](/docs/data-api/connection-details) — shares the platform's limit of **600 requests a minute per key**. Connections to the database itself are not rate limited by us at all; that is Postgres and your compute size. ## Not here yet Each of these exists in the engine underneath and is not exposed. Say if you need one; that is what moves it up the list. | | | |---|---| | **Read replicas** | A second endpoint for read-heavy workloads | | **Choosing a region per database** | It follows the project's today | | **Logical replication** | Off; streaming changes out to another system | | **IP allowlists** | Anything with the string can connect | ## Deleting a database Two ways, and they are not the same. **Delete the database** — on the project's Database page. It removes the database, every branch, and the compute behind them, and stops the charge immediately. The project keeps its keys, its files and everything else. **It is irreversible and has no window.** You type the project's address to confirm, and when it returns there is nothing of ours holding a copy — which is the point of the promise, and the reason the confirmation is not a single button. **Delete the project** — the reversible one. The project and its database are suspended for **30 days** and destroyed after that. If there is any chance you want the data back, this is the path to take. After either, gone means gone: no backup of ours survives it, because what we would be keeping is a copy of your product's data that you asked us to destroy.