Deployment Storage
Deployment Storage is cloud storage for the build output and Edgenivo Function bundles retained with your deployments. A Deployment Retention Policy controls when each deployment becomes eligible for deletion. Exceptions to the policy can keep a deployment and its output longer.
You use retained deployment output to:
- Open an earlier Preview deployment to investigate a regression
- Promote a tested deployment without rebuilding it
- Roll back to an eligible Production deployment during an incident
- Inspect previous release output during an audit
Each successful deployment can add two types of Deployment Storage:
| Usage metric | What it includes |
|---|---|
| Deployment Storage | Build outputs and static assets |
| Functions Storage | Edgenivo Function bundles stored in each region where Edgenivo deploys them |
Three factors affect Deployment Storage:
| Driver | Effect on usage |
|---|---|
| Number of retained deployments | Each retained deployment can add stored assets and Function bundles. |
| Output size | Larger assets or Function bundles add more storage per deployment. |
| Retention period | Longer periods keep each deployment's output for more time. |
To review your usage:
- Select your team in the Edgenivo dashboard.
- Open Usage.
- Select Deployment Storage.
- Open Deployment Storage or Functions Storage.
- Select Projects to compare usage by project.
Review both metrics. A project can have low Deployment Storage and high Functions Storage, or the reverse.
Edgenivo measures Deployment Storage and Functions Storage in GB-months. A GB-month measures how much data Edgenivo stores and how long it stores that data.
| Usage metric | Pro list price |
|---|---|
| Deployment Storage | $0.10 per GB-month |
| Functions Storage | $0.10 per GB-month |
For each metric, Edgenivo records the maximum stored amount for each project on each billing day. It adds those daily project amounts across the billing period. Storing 1 GB every day in a 30-day month equals 1 GB-month.
A deployment stops contributing to Deployment Storage and Functions Storage the moment it is first deleted, whether you delete it manually or a retention policy deletes it. You are not charged during the recovery period, the window after deletion when Edgenivo can still restore the deployment. A restored deployment counts toward Deployment Storage and Functions Storage again.
Enterprise rates follow your contract. Your plan or contract may also include an allowance. Use Usage and your invoice to confirm your team's allowance, rate, and charge.
Use a Deployment Retention Policy to control how long Edgenivo keeps deployments.
- The team policy sets the default for new projects. You can also apply it to all existing projects.
- A project policy changes retention for that project only.
Shorter retention can reduce storage over time. It also reduces the deployment history available for inspection, promotion, and rollback.
Deployment Storage is separate from other Edgenivo storage products:
| Product | What it stores | Main control |
|---|---|---|
| Deployment Storage | Output linked to retained deployments | Output size and retention |
| Remote Cache Artifacts | Task output that later builds can reuse | Cache use and retention |
| Edgenivo Blob | Files that your application uploads and manages | Application upload and deletion logic |
A change to one product does not always change usage for another product.
For help reducing Deployment Storage usage, see the optimization guide.
Was this helpful?