docs
Where your credentials live
MihraOps is a desktop client, not a hosted panel. Your infrastructure credentials never reach our servers, and this page says exactly where they do go.
On your computer
Server records — host, user, SSH key or password — are stored in a local file encrypted with your operating system secure storage: Keychain on macOS, DPAPI on Windows, the desktop secret service on Linux. If that facility is unavailable, MihraOps refuses to save rather than falling back to plain text.
Known host fingerprints are kept in a separate file. It holds public fingerprints only, so it is not encrypted.
On your server
Git and registry credentials you ask MihraOps to remember are stored on the server you control, under ~/.mihraops/secrets, encrypted with a key at ~/.config/mihraops/keys/master.key. They travel there over your SSH connection and are never routed through our backend.
What licensing receives
Only what licensing needs: the license key you entered, a one-way hash of the machine identifier, a one-way hash of the installation identifier, the device label you can edit, and your platform, operating system version and app version.
Raw machine identifiers never leave your device. The Free plan makes no license calls.
Optional active-installation measurement
Separately from licensing and the server Agent, the desktop asks before sending an active-installation presence signal. Nothing is sent until you explicitly allow it. When enabled, at most one signal per UTC day contains a stable one-way pseudonym derived from a random local installation id, the platform, distribution channel and app version.
The signal contains no managed server, address, SSH data, container, email, license key, file, command, error content or raw machine identifier. It is pseudonymous rather than anonymous because the same installation must be counted across days. Turning it off requests deletion of the previous server-side record and rotates the local identifier.
What it cannot see
SSH private keys and passphrases, server passwords, registry and Git tokens, your source code, container data, environment values, logs and terminal output. None of it passes through our infrastructure, because the connection is between your computer and your server.