Project working-storage growth
Separate database, uploads, logs, release artifacts and temporary recovery space. A hypothetical 20 GB database + 5 GB uploads + 2 GB release workspace = 27 GB before growth reserve. Compare that figure with the plan allocation and the space needed during migrations or restores; a recovery copy on the same disk is not independent.
Calculate outbound transfer from observed payloads
Multiply payload size by delivered responses and add exports, retries and release traffic. A 250 KiB response delivered 100,000 times is about 23.8 GiB. Cache hits may move transfer to another service rather than erase it, so record which system serves each byte.
Set review thresholds
Project the database and upload growth over the intended prepaid term. Review before either working storage or monthly transfer reaches the team’s chosen reserve threshold. PrivacyNodes does not publish an overage procedure here, so obtain that term from the owner before relying on excess usage.
Choose the resource that addresses the measured limit
Add storage for a demonstrated working-capacity need, reduce retention or artifacts when they have no operating purpose, and change transfer assumptions when payload measurements differ. Next, document an off-server recovery path independently of the disk choice.