Deployments
Manage an instance
Understand start, stop, renewal, the grace period and release for fixed-term GPU nodes.
5 min read · UpdatedFrom running to released
Running means an active allocation in the local lifecycle. Stop changes it to stopped without altering its end date. Start is accepted only for a stopped instance whose paid term has not expired.
Released is final: it returns modeled capacity to the pool, and the instance cannot be started or renewed. Release asks for confirmation in the dashboard.
Renew manually or automatically
Renew adds another full term after the current end date, or after the current time if the old term has already expired. The renewal price is displayed on the instance card before the action.
Auto-renew is off by default unless you enable it. The scheduled worker looks for eligible instances during the 24 hours before expiry. It renews only when the account balance can cover the stored price. The local development server does not invoke scheduled events automatically; manual renewal is available for testing.
Expiry and the 72-hour grace window
When the lifecycle worker processes an expired instance, it enters grace. The grace deadline is 72 hours after the original expiry, not 72 hours after the worker happens to run. Starting is blocked until renewal succeeds.
After the grace deadline the worker releases the allocation. An expired node cannot be brought back merely by toggling start. These are local database transitions; production power, storage and data-retention behavior still require a provisioning integration.