A native desktop client for HashiCorp Vault, for macOS and Windows. Listed on the Microsoft Store as Vaulted Desktop.
Installing
Windows — the Microsoft Store
Search the Store for Vaulted Desktop. Updates arrive through the Store.
The .msix attached to each GitHub release is not a download. It
is an archival copy of what was submitted, and it is unsigned until Microsoft signs it during
Store ingestion — double-clicking it gives you a certificate error, not an app.
On a Windows ARM64 device the x86_64 build runs under the operating system's emulation.
macOS — GitHub Releases
Download the .dmg for your Mac from the latest GitHub release, open it and
drag Vaulted to Applications. There are two:
Vaulted_version_aarch64.dmg— Apple Silicon (M1 and later)Vaulted_version_x64.dmg— Intel
Not sure which you have? Run uname -m in Terminal: arm64 is Apple
Silicon, x86_64 is Intel. Both are native builds; neither needs Rosetta.
Every release is signed with IronMade's Developer ID and notarized by Apple, so it opens normally on first launch, with no Terminal commands or right-click workarounds. After that, Vaulted updates itself: each update is also verified against a signing key built into the app, and a tampered download is refused.
This download is free and fully featured, with no trial.
“Vaulted is damaged and can’t be opened”
Current releases should never show this. If you see it, you have an early build from before notarization: download the latest release and replace it.
Connecting to a server
Vaulted supports five authentication methods: token, userpass, LDAP, AppRole and OIDC/SSO. OIDC opens your browser and returns through a local callback listener, so the browser must be able to reach the machine Vaulted is running on.
You can save a profile per cluster, each with its own address, namespace and TLS/CA settings, and switch between them.
The connection fails or times out
- Check the address and namespace on the profile — a namespace typo usually looks like a permissions error rather than a typo.
- If your cluster uses a private certificate authority, set the CA in the profile's TLS settings. A self-signed certificate with no CA configured fails as a connection error.
- Confirm you can reach the same address from the same machine, for example with
vault status.
My session keeps expiring
Renewable sessions renew themselves in the background, and the header shows a live countdown of the remaining time. A token that is not renewable cannot be extended — it will expire when its lifetime ends, and you will need to authenticate again. If you asked Vaulted to remember your token, it is stored in the operating system keychain, not in the app.
Search
Path search is fast and always available. Content search reads the values of secrets to match against them, so it is explicit and asks for consent before it runs — it is never silent, and never automatic. Either can be scoped to a single mount or run across all mounts.
Security
All communication with Vault happens in Vaulted's Rust process, which is the security boundary. The user interface only ever receives data that is safe to display.
Vaulted connects only to:
- the Vault servers you configure;
- your identity provider, if you sign in with OIDC/SSO;
- the update service for your copy: GitHub Releases for the macOS download, the Microsoft Store or the Mac App Store for store copies;
- the store's licence service, for store copies only, to check the trial or purchase. The macOS download makes no licence check.
There is no analytics, no telemetry and no crash reporting. Nothing about your secrets, your servers or your usage is sent to IronMade or to anyone else.
Update downloads for the macOS download are verified against a minisign public key built into the app, so an update that has been tampered with is refused regardless of where it came from.
What Vaulted stores and every connection it makes are listed in the privacy policy.
Reporting a problem
Email support@ironmade.site with:
- the Vaulted version, and whether you installed from the Microsoft Store or a macOS release
- your operating system and version
- your Vault server version, and the authentication method you used
- what you expected to happen, and what happened instead
Never send tokens, secret values or screenshots containing them. Nothing in a bug report needs them, and a support mailbox is not a safe place for a credential. If a secret has already been sent anywhere it should not have been, revoke it first and report afterwards.
