Creation is a state machine, not a loading animation
The system records provisioning progress through explicit states. Validation, tenant creation, product creation, capacity, domain, ownership, blueprint, data, content/media, TLS and health checks are separate steps. A failure can therefore be recorded and retried without claiming that an incomplete product is ready.
READY is the handoff point
At READY, BADWEB can provide the customer with the product URL and the relevant administration/workspace URL. An activation link is queued to the customer email so the owner can choose a password.
Why trial timing matters
A customer should not lose evaluation time because external infrastructure is still preparing the product. The platform contract therefore reserves the trial during provisioning and starts the configured trial clock only after READY.
READY is not a promise of permanent zero downtime
READY means the product passed the platform’s creation/readiness flow at handoff. Like any online service, later availability can still be affected by maintenance, incidents, provider outages, credentials, DNS/TLS or other operational conditions.