Sovereign secrets management for European businesses

hiVault stores keys, passwords and certificates in encrypted form on infrastructure in the European Union. The master key is split between trusted people and is never kept whole on a server.

  • Hosted in the European Union
  • Master key never stored whole
  • Access recorded in an audit trail

Three decisions behind hiVault

The master key is never stored ready for use

The key that protects your secrets is split into shares held by trusted people. It is rebuilt in memory only during an unsealing ceremony and is never written to disk in one piece.

Built and operated in the European Union

hiVault runs on infrastructure located in the European Union and is operated by a European company. Where your secrets are kept is an architectural decision, not a line in a contract.

Security considered from the first line

Secrets are encrypted at rest and in transit. Access follows the principle of least privilege, and reads and changes are recorded in an audit trail.

How hiVault protects the master key

A vault is only as safe as the key that opens it. This is what happens to that key in hiVault.

  1. The key is split

    The master encryption key is divided with Shamir's Secret Sharing. A defined number of shares is needed to rebuild it; fewer shares reveal nothing about the key.

  2. Each share has its own guardian

    Every share is encrypted with a separate password and kept by a different person, away from the server.

  3. People unseal the vault

    Unsealing is a deliberate ceremony carried out by authorised people. It is not a file that the server reads on its own.

  4. A restart seals it again

    After a restart the vault is sealed. Secrets stay unavailable until the guardians unseal it again.

What the MVP includes

The MVP is an early version with a deliberately small scope. This is what works today and what comes next.

Available now

  • Encrypted storage

    Keys, passwords and certificates are stored in encrypted form. Each secret is protected with its own data key, which is in turn protected by the master key.

  • Sealing and unsealing

    The vault starts sealed and is opened by people, with a threshold of key shares.

  • Scoped access

    Access tokens are limited to the secrets and operations they need, and can be revoked.

  • Audit trail

    Reads, writes and changes are recorded, so you can see who used a secret and when.

Planned

  • Automatic rotation of keys and passwords
  • .NET SDK
  • Controlled access for AI agents through MCP

Features and limits may change during the MVP.

For organisations that know where convenience ends and control begins

Businesses with data residency requirements

You need to know where your secrets are stored and who operates the system that stores them.

Regulated organisations

hiVault is designed to make compliance easier: access is scoped, recorded and reviewable. It does not replace your own assessment.

Development teams

You want secrets out of configuration files and repositories, without depending on providers outside Europe.

Request access to the MVP

Tell us who you are and what you would like to use hiVault for. We will reply by email.

Your details

Fields marked with * are required.

We will reply to this address.

A sentence or two is enough. Do not include passwords, keys or other secrets.

We collect only what you enter here and the time of your request. No profiling and no tracking.