Snapshot the client's environment; the snapshot holds no secret

A traditional AI integration puts the provider key in an environment file, and a snapshot records every file. Every backup, clone, and "can you send me a copy of staging" becomes another place the key lives.

On Hoody the client's app authenticates to the AI gateway as container-client-acme. Nothing in the filesystem is a credential. Snapshot it, POST /copy it to a second server, hand a clone to the client's new developer: the copy is a new container with its own identity, and the disk image carries nothing that works anywhere.

So you snapshot freely. Before every risky change, on every milestone, whenever a client asks for a copy. Nothing to scrub, nothing to rotate afterward.