Skip to content

Security

Jarvis Automation runs on your own hardware, and on the server nothing that needs the internet is on by default. This page is the short version for running a server; the details are in the security model.

Staying fully local

Every outbound-internet capability of the server is opt-in and defaults to off; the desktop agent's self-update is on until you turn it off. See Network Egress & Offline Mode for the toggles.

What to know as an operator

  • Three ports. A fresh install listens on 7700 (the API), 7710 (the web admin) and 1884 (MQTT for nodes). Keep them on your home network. To reach Jarvis from outside, use a tunnel or reverse proxy with TLS instead of opening the ports.
  • Finish setup promptly. Until the first account exists, the setup wizard asks for the one-time setup token from the server's data directory, so nobody else on the network can claim the server. After that, people join with an invite code.
  • Every caller is authenticated. People sign in with a password and get short-lived RS256 tokens; each node has its own key and its own MQTT login. See Authentication.
  • Protect the data directory. ~/.jarvisd/ (or /var/lib/jarvisd for the Linux service, %ProgramData%\jarvisd for the Windows service) holds the database and the token signing key, readable only by the service user. The database also holds, unencrypted, the API keys of any remote model provider, the Twilio credentials and the Hugging Face token. Backups contain all of these too.
  • Command secrets are encrypted for the node. API keys and account tokens for commands are encrypted between the mobile app and the node with the node's key, K2. The server stores and relays them only encrypted and never keeps K2, but for desktop agents and nodes keyed without the setup hotspot, K2 passes once through the server's memory while it is delivered. This protects them from a stolen database or backup, not from a compromised server. See Command secrets.
  • The desktop agent updates itself. It follows the server's version from GitHub releases by default; run it with --no-auto-update (or auto_update: false) to stop that.
  • Updates are signed. jarvisd upgrade and Update in the web admin refuse a release whose minisign signature or checksum does not match.

More

The security page of the old Docker install is kept under Legacy.