Security
What a heartbeat contains
Hostname, goethe version, OS and kernel, uptime, environment (bare metal, VM, container, cloud), network addresses, the API address, GPUs with memory use, and installed and loaded models, and the node's API keys (name, key, model scope and expiry).
The API keys are stored encrypted, in a table separate from the rest of the node's data, and are never part of the console's regular updates. A key is decrypted only when an operator, admin or owner who can see the node clicks Reveal.
What it never contains
API key hashes, engine keys, prompts, traces, learning notes, file paths, environment variables and process command lines.
Credentials
- The node token is random, shown to the node once, and stored on the platform only as a hash.
- Credentials on the node are kept in
GOETHE_HOME/platform/with owner-only permissions. - Install links and auth keys work once, expire (install links after 1 hour), and are stored only as hashes.
- Removing a node in the console, or
goethe logout, revokes its token immediately.
Transport and limits
- Nodes talk to the platform over HTTPS only. Plain HTTP is accepted only for local development hosts.
- Requests are size limited and validated field by field.
- Pairing, enrollment and heartbeats are rate limited, and approval codes lock after repeated wrong attempts.