Release 0.2609.5
· 2 min read
This release makes resource costs easier to estimate and understand, and simplifies deployment configuration.
Highlights:
- Redesigned the pricing calculator with compact app, worker, and database cards. Add, duplicate, or remove resources and adjust replicas, CPU, RAM, and storage to compare costs
- Added resource-specific deployment estimates with expandable calculations and remaining free capacity
- Improved billing breakdowns with separate Apps, Databases, and Workers tabs, named embedded processes, and clearer usage, free allowance, billable usage, rate, and amount columns
- Added clearer usage details to new invoices and downloadable receipts while preserving previously issued invoices
- Added support for a free allowance shared across projects owned by the same account, with individual resource allowances and notices explaining scheduled pricing changes
- Updated app and worker deployment defaults to 0.01–0.1 vCPU and 128–256 MiB RAM, with CPU controls displayed to two decimal places
- Simplified deployment forms and improved embedded worker and cron configuration
Fixes:
- Aligned deployment estimates with the project owner's billing terms, including scheduled pricing changes
- Improved billing accuracy for fractional usage, embedded cron runtime, and standalone workers
- Improved retry handling to prevent duplicate usage charges and credit deductions
- Replaced internal billing terminology in customer pages and error messages with plain-language explanations
- Improved resource-name validation
Notes:
- Shared free allowances roll out separately. Existing billing cycles retain their assigned terms; check your billing page for any scheduled change
- Shared allowances belong to the project owner. Joining a project does not add another free allowance or transfer its charges to a member
- Embedded workers and cron usage appear under their app; standalone workers have their own breakdown. Builds and standalone cron are excluded from the shared-allowance billing calculation
- Deployment defaults do not resize existing resources. Estimates are indicative; final charges depend on usage and the billing terms for the applicable cycle