The Power tab gives administrators direct control over the runtime state of their deployment, including shutdown and hard reset options.

The Power tab provides confidence and control by letting administrators manage shutdowns, resets, and resource retention while balancing performance and cost considerations.

When shutting down a preview, the system first attempts a safe (graceful) shutdown to avoid data corruption. If that fails, a forced shutdown may occur.

Yes, a forced shutdown may compromise data integrity. For maximum safety, administrators are encouraged to shut down from the command line instead.

Even when powered off, the deployment’s data, IP address, CPU, and RAM remain reserved. This ensures consistency but means resources are still billed.

Yes. A powered-off deployment continues to incur costs for reserved resources and data transfer. To stop billing, the deployment must be destroyed instead of simply shut down.

Shutting down preserves your server’s data and reserved resources, while destroying permanently removes them and ends billing.

Power Cycle performs an immediate hard reset of the server. It should only be used when the system is unresponsive and a normal shutdown is not possible.

Yes, since a power cycle bypasses the graceful shutdown process, there is a risk of data corruption. It is a recovery measure rather than a routine action.

Use Power Cycle only if the deployment is frozen or unresponsive. For regular shutdowns, always use the Turn Off option to preserve data integrity.