Skip to content
Language: EN
Menu

Secret management

Haven

Beta

It holds other systems’ credentials, so it fails closed.

Visit Haven Documentation Contact us

A secret manager for the credentials that sit behind a business: database passwords, API keys, signing keys and certificates. It issues them with an expiry, scopes what each application may reach, and records every request before it runs. Its master key never touches disk, and after a restart it stays locked until enough of your named holders combine their shares to open it, so possession of the server is not possession of the secrets.

Who it is for. Organisations that must show where a credential came from, who could use it and when it was withdrawn, and that want credentials to expire on their own.

Status
Beta
Part of
Core platform
Product site
haven.rodmena.co.uk
Tags
Secret managementExpiring credentialsSplit-key unlockAudit trail

What it does

  • Locked until your people open it

    The master key is never written to disk. After a restart, three of five share holders must combine their parts before anything can be read, so a stolen server or a copied backup gives up nothing.

  • Separation between teams

    Each tenant has its own encryption key, its own policies and its own secrets, and the boundary is enforced inside the database. A caller cannot ask to be treated as another tenant; that is fixed by the credential it presents.

  • Credentials that expire on their own

    A database password is issued per process with a lifetime attached, created when it is asked for and withdrawn when the time is up, so a leaked password stops working without anyone noticing it leaked.

  • Applications hold no keys

    Haven encrypts and decrypts on their behalf, so the key never reaches the application. Rotating a key leaves everything already encrypted readable.

  • A private certificate authority

    Short-lived certificates are issued per service, with the domains a role may ask for constrained by that role.

  • An audit trail that is checked

    Every request is recorded before it runs, and each record is chained to the one before it by a hash. Verification walks the chain and recomputes it.

Documentation and access details are on the product site, haven.rodmena.co.uk. For a pilot, an integration or procurement questions, contact us.

Screens

All 6 screens of Haven