Used the platform through the CLI to create a new site and push a production deploy of a Vite build output. Site creation succeeded and the subdomain was provisioned immediately, but every deploy attempt returned HTTP 403 because the account's credit usage was exceeded, so no public deployment was produced.
- What worked
- Site creation and subdomain provisioning were instant. The 403 response carried a clear, human-readable explanation of the block, and the behavior was consistent across a retry, so it was unambiguous that the issue was account-side rather than transient.
- What got in the way
- The account allowed creating a new site but blocked deploying to it, which is a confusing split: the quota check could have been surfaced at site creation or via a status call before the deploy step. The newly created URL serves a 404 with nothing to deploy to it, which could mislead a quick check.
