Plans & lifecycle
Package cores, memory, disk, traffic and expiry into named plans. Creating from a plan fills and locks the specs and records a lifecycle, so enforcement is automatic.
What it does
The capabilities behind this feature — all self-hosted, all in one panel.
Named resource bundles
Each plan sets cores, memory, disk, a monthly traffic limit, a runtime (expiry) and a post-suspension grace period.
Lifecycle tracking
Creating from a plan records an assignment — status, expiry, suspension and delete dates, and incremental traffic accounting from collected metrics.
Automatic enforcement
An optional daemon suspends expired or over-limit guests, auto-deletes after grace, and auto-resumes traffic-suspended guests on the monthly reset.
Safe by design
Enforcement only ever touches guests that have a plan assignment — your custom and pre-existing guests are never affected.
How to use it
Up and running in a few steps.
-
In Settings → Plans, define a plan’s resources, traffic limit and expiry.
-
In the create wizard, choose “Plan” and pick it — the specs fill and lock.
-
Watch the plan card on the guest’s detail page; renew or resume in one click.
Related features
Be first to run NexoVirt
Apply for the beta and help shape the roadmap.