Projects, plans, quotas, and billing

Projects

Projects isolate databases and operational context inside an organization. Use names that reflect environment or product. Switching projects changes the data shown across the console.

Quotas

• Database count limits how many active databases a project may own.
• Storage limits apply to retained database data.
• Connection limits protect cluster capacity.
• Backup retention determines available restore history.
• Plan-specific operations may require an upgrade.

How usage is measured

• Compute-unit hours are recorded only while PostgreSQL is doing work; an idle database does not accrue active compute usage.
• Storage is accumulated as GB-month from sampled retained bytes.
• Usage samples are append-only and scoped to the owning organization, project, and database.
• The billing page shows period-to-date usage, included allowances, estimated charges, and a month-end projection.

Budgets and safeguards

Organization owners, administrators, and billing operators can set a monthly budget and choose whether Renviq should only notify or block new capacity after the limit is reached. Production databases are never automatically stopped by a billing safeguard.

• Alerts are emitted once at 50%, 75%, 90%, and 100% of the configured budget.
• Block growth prevents new capacity while preserving existing workloads.
• Enforcement is fail-safe and remains inactive until the platform explicitly enables enforced metering.

Billing lifecycle

Plans & billing shows the active plan, included allowances, overage rates, provider availability, invoices, and budget settings. Upgrades should apply new quota only after payment confirmation. Downgrades may require reducing usage first.