Direct Static Hosting

The only deploy path in this invite-only beta is a direct static upload of an already-built directory:

zerokie apps deploy <name> --dir ./dist

The app is served only from its generated HTTPS hostname. The beta does not run a customer process or build source code.

What one deploy does

The CLI:

1. walks the selected directory and builds a complete canonical manifest;
2. excludes hidden entries by default and always excludes .git/;
3. admits one exact deploy session and manifest;
4. uploads each admitted path with its exact length, content type, and bytes;
5. maintains the session heartbeat; and
6. asks the server to finalize the complete manifest and remove stale paths.

The resource limits apply before and during admission.

Non-atomic overwrite boundary

Provider-visible static content may be non-atomically changed by a failed overwrite. A successful provider write can become visible before every manifest entry is complete. A failure can therefore leave a mixture of earlier and newer content. There is no customer rollback or version promotion.

Use disposable content, avoid concurrent deploys, and inspect the generated hostname after the command completes.

cleanup_failed means bounded cleanup did not finish. If you see cleanup_failed, stop and contact the operator. Do not retry, delete the app, or use undocumented recovery knowledge until the operator resolves the state.

Closed capabilities

Repository builds, connect, webhooks, rollback, Docker, custom domains, and CI/CD are unavailable and server-side closed in this beta. Raw remote file-list/delete operations are also unavailable; the admitted manifest is the customer deploy boundary.