How Downgrades Work
When you downgrade a Vertra Cloud plan, your remaining days are converted into equivalent days on the cheaper plan, in proportion to the price difference, up to 365 days on the target plan — no paid time is lost. The unused value of the current plan is converted by the price ratio. Because the target plan costs less, you always end up with more days than you had.Downgrades always move to the immediately previous plan in the hierarchy. You cannot skip plans.
Conversion Formula
Your remaining time is converted proportionally:Example
Pro 4 → Starter 2
Plan Hierarchy
Downgrades only happen from Account Settings. The checkout never accepts a plan smaller
than your current one — the plan picker hides them, and
POST /v1/orders answers
400 NOT_AN_UPGRADE for any order type that would shrink the plan.Before You Downgrade
The system will check the following before processing:1
Memory usage
Your total memory usage across all apps and databases must fit within the target plan’s memory limit. If it exceeds, you’ll need to reduce resource allocation first.
2
Docker images
The Docker images you have (your own and the ones image templates take, one per distinct image) must fit within the image slots of the target plan. If they exceed, delete images or image template apps first.
3
Rate limit
You can only downgrade once every 3 hours to prevent abuse.
What Changes on Downgrade
Resources & Limits
Resources & Limits
- Memory limit is reduced to the target plan’s allocation
- Apps and databases that exceed the new limit must be resized beforehand
- CPU allocation is adjusted proportionally
Features
Features
- Features exclusive to higher plans are immediately disabled
- For example: custom domains, zero-downtime deploys, the database data manager, etc.
Workspaces
Workspaces
If downgrading from Starter 2 to Starter 1, you will lose the ability to create and manage workspaces. Existing workspaces will be affected.
Deploy History on Downgrade
When you downgrade, the earlier versions of your applications beyond the new plan’s limit stop being available for rollback right away. Their code is deleted shortly after. Upgrading again does not bring back code that was already deleted. The version that is running is never affected. See Deploy history and rollback limits for how many versions each plan keeps.Deploy Settings on Downgrade
Your application’s automatic rollback and zero-downtime settings are not erased when you downgrade. The saved value stays on the application, but it only takes effect on a plan that includes the feature: automatic rollback from Pro, zero-downtime deploys from Starter 2. If you upgrade again, the saved values act again. While you are below the required plan, you can still turn either setting off, but not on.How to Downgrade
- Via Dashboard
- Via API
- Go to Dashboard → Settings → Account
- Scroll to the Downgrade Plan section
- Review the target plan and confirm