Installation lifecycle
Beta

Know what changes before the installer changes it.

Prepare the server, verify prerequisites, use an approved artifact, complete initial setup and confirm every critical service before hosting customer workloads.

What this means

Scope, operating value and boundaries.

The product installer exists in controlled testing; public commercial distribution is not yet approved.

Preflight

Confirm OS, hostname, DNS, network, MySQL, access and recovery readiness.

Verified artifact

Use only a versioned installer from the future approved channel.

Fail-closed phases

A failed phase must not be reported as an active release.

Strict verification

Validate panel routes, services, permissions and release identity after installation.

Safe preflight

Confirm the server baseline before requesting an installer.

This read-only command reports the operating system, architecture and root filesystem capacity. It does not install EzePanel or change the server.

Operating path

A deliberate route from intent to outcome.

Prepare serverStart from the documented baseline.
InstallRun the approved versioned artifact.
Verify and onboardComplete setup and confirm health before customer use.
EZEPANEL IS UNDER DEVELOPMENT

Evaluate the product with its current boundaries visible.

Review current capabilities, planned commercial availability, technical requirements and documentation.