Invite-Beta Journey

Non-production boundary

This is an invite-only, disposable DEV beta. It is non-production and has no backups, no restore, no SLA, and no production guarantee.

Complete this journey in order:

1. Use the operator-authorized verified OIDC email and sign in through OIDC so first-login provisioning can create the customer record.

2. On Tokens, mint a customer token and copy its plaintext from the one-time view.

3. Obtain the installer from https://releases.zerokie.com/install.sh. It resolves the current immutable source-bound release and verifies its embedded SHA-256 before installation.

4. Log in against the explicit HTTPS API endpoint:

   zerokie login --endpoint <DEV_API_HTTPS>

   At the Token: prompt, paste the copied token with hidden input from an interactive terminal. Do not put the token in command arguments.

5. Create one static app in the dashboard or with zerokie apps create --name <name>.

6. Upload the already-built directory with zerokie apps deploy <name> --dir ./dist.

7. Verify the exact generated HTTPS hostname returned for the app.

8. Revoke the token in the dashboard and prove the revoked token is rejected by a subsequent CLI request.

9. Delete the disposable app from the OIDC-authenticated dashboard and account for cleanup.

Replace every placeholder with the exact value supplied or returned for the operator authorization. Do not infer an API hostname.

The implemented product boundary is the operator-authorized verified OIDC email plus first-login provisioning. A successful login does not widen that authorization.

What this beta does not provide

There is no public signup and no mutable release feed. The public installer selects only the current immutable source-bound beta artifact. Repository builds, connect, webhooks, rollback, Docker, custom domains, and CI/CD are unavailable and server-side closed in this beta.

Only direct static upload and the generated HTTPS hostname are supported. Read how to obtain the CLI, then follow the first-deploy walkthrough.