Site
Live on testnetRuns on 
Each deploy uploads a folder and seals it as a release with its own preview URL. Production is a pointer on the contract. You move it with quay promote and move it back with quay rollback.
Commands
quay init quay deploy ./dist -m "harbour office" quay promote 1 quay rollback
How Harbour Board uses it
- Harbour Board has seven releases. Production is 7 and the previous release is 6.
- Every release still answers at
/r/<id>/, so the home page can load any of them. - Bytes shared by two releases are stored once, so all seven hold 137,411 B.
Proof on testnet
| The account and contract | 9He5iL5N… |
|---|---|
| Release 7 sealed and promoted | DrGVTiLy… and G82qz1qK… |
| A publish-only key refused promote | 58YRcXZZ…, on quay-i7qkbbp3.testnet |
Check it without a key: view get_status '{}' shows production, previous and the stored bytes. The view helper is in the repository README, and scripts/judge.sh runs these checks.
What you trust
Nothing to replace. The releases are on your account, and any RPC node reads them. A full-access key can replace the contract wasm, so a release is not owner-proof against that key. Keep it off CI and use quay keys create --ci there.
Limits
| Files | 64 per release, 800,000 B each |
|---|---|
| Releases | 32 live at once |
| Payload | 2,000,000 B per account |
| Cost | 0.01 NEAR locked per 1,000 B, unlocked when you delete a release |
Every flag is in the command reference, generated from quay deploy --help, quay promote --help, quay rollback --help.