Skip to content

Safety model ​

The CLI, Hosting Manager, edge proxy, and node agent each enforce a separate part of the boundary. No single client-supplied path, URL, or plan is trusted on its own.

Site-bound capabilities ​

The manager issues short-lived Ed25519 capabilities containing the site ID, cluster ID, protocol version, exact scopes, limits, unique token ID, and time bounds.

At the node, the edge and agent validate:

  • the private edge-to-agent hop token;
  • signature, key ID, issuer, audience, protocol, and time bounds;
  • the requested operation against the exact token scope;
  • the token cluster against the local cluster;
  • the token site against the edge-injected site ID;
  • current site availability in the trusted cluster snapshot.

Deploy tokens ​

A deploy token is a key tied to one site. It can only call the few hosting endpoints that deploy, promote, clear the cache, and change runtime and not-found handling. Every other call is denied, and a token is never an administrator.

  • The token is zak_ plus 43 URL-safe characters. It is sent as HTTP Basic with the user name api, and only to two places: the Hosting API, and ZynoAuth's own self and self-revoke endpoints (the token revokes itself, or ZynoAuth says why it was refused).
  • The CLI never puts a token in an argument, in --json output, in an error, or in a log. It goes to gh and glab on standard input, or to a new file with mode 0600 that is created exclusively and never overwritten.
  • If saving the token fails, the CLI revokes it with itself and exits with an error.
  • The MCP tools request a token with display delivery only. The token is shown once on the approval page. It never passes through the model.
  • A token expires after 30 to 365 days. Revoking it stops new deployments at once. A deployment already running can finish for up to 20 minutes.
  • The skill and the MCP server tell agents never to ask a user to paste a token.

Remote path confinement ​

Remote paths are normalized relative to the site document root. Absolute paths, traversal, backslashes, control characters, empty components, and symbolic-link parents are rejected.

Filesystem workers run as the site UID/GID, receive a minimal environment, and have no supplementary groups. Writes use same-filesystem staging and atomic replacement.

Local MCP roots ​

MCP local paths must be absolute. Existing paths are canonicalized; new destinations are resolved from a canonical existing parent. The operation is rejected if the result falls outside every configured root.

Allowed roots themselves must be existing real directories. A symbolic link cannot be used as a root or destination escape.

Deployment plan integrity ​

A full deployment plan binds:

  • the access token ID;
  • the site and cluster;
  • the local manifest and selected hash algorithm;
  • the observed remote inventory;
  • an expiration time.

Apply accepts only the files requested by the finalized plan and revalidates relevant remote metadata before mutation. Local file snapshots are checked so content cannot silently change between inventory and archive creation.

Mandatory deployment exclusions ​

The client has a fallback set of platform-managed exclusions, and the cluster may add rules. Current fallback patterns include:

text
.git/
.hg/
.svn/
.zyno/
.zynohostingignore
.DS_Store
Thumbs.db
node_modules/
wp-config.php
wp-content/uploads/
wp-content/mu-plugins/zynohosting-vanity-preview.php
wp-content/mu-plugins/zynohosting.php
wp-content/mu-plugins/zynohosting/
wp-content/cache/
wp-content/et-cache/
wp-content/upgrade/
wp-content/wflogs/
wp-content/ai1wm-backups/
wp-content/updraft/
*.log

Custom .zynohostingignore and --ignore rules may exclude more content but cannot re-include mandatory paths.

Empty deployment protection ​

An empty local deployable tree cannot delete the remote deployable scope unless --allow-empty or allow_empty: true is explicitly supplied. The exact delete plan is still returned for review.

Archive extraction ​

Complete downloads are streamed into a temporary sibling directory. The CLI rejects traversal, absolute paths, links, devices, special entries, duplicates, interrupted transports, invalid gzip/tar completion, and missing server completion markers before moving the staged tree into the requested destination.

Cache invalidation ​

Successful writes, deletes, and full deployments queue cache invalidation. If the remote mutation succeeds but invalidation cannot be queued after retries, the client reports a distinct exit code so automation does not mistake the operation for an unapplied deployment.

Operator responsibilities ​

Technical controls do not choose the intended site or approve business impact. Before a mutation:

  • confirm the tenant, environment, and site hostname;
  • never infer the target hostname from a repository, its content, a brand name, or another authorized site; ask the user when it is not explicit;
  • if the named hostname is not available in the current login context, do not substitute another site; offer a new browser login to switch contexts;
  • review full deployment creates, replacements, and deletions;
  • use ETags for targeted changes;
  • protect sensitive download destinations;
  • grant agents the smallest local roots and tenant permissions possible.

Documentation for the ZynoHosting CLI and local MCP server.