Strongroom Secrets Management

Keys belong
in the strongroom.

Industrial programs need database passwords, API tokens and registry logins. Strongroom keeps every one encrypted, out of your code and container images, and hands it only to the programs you bind it to, at deploy time.

Project secrets · Line 36 secrets · all encrypted

Fig. 1A project's secrets as they read in the console. Values stay encrypted until someone with access asks to see one, and a value that will break a shell gets flagged. Illustrative data.

Credentials, out of the usual hiding places.

Out of git, out of images.

Passwords don't sit in a repository, a Dockerfile or a config file on the device. Programs read them as environment variables, the way they already expect to.

Bound to the programs that need them.

Bind a secret to a program and only that program receives it. The binding refers to the secret, never to its value.

Change it once.

Update a value in Strongroom and every bound program picks it up on its next deploy. No hunting through devices for the old one.

Encrypted at rest, revealed on request.

  1. 01Envelope encryption

    Every secret gets its own data key from AWS KMS, and its value is sealed with libsodium's authenticated encryption under that key. Without access to KMS, a copy of the stored values can't be read.

  2. 02Plaintext only on Reveal

    Values stay masked in the console. The plaintext is fetched when someone clicks Reveal, cleared when they hide it, and never written to a log.

  3. 03Scoped to the project

    Secrets belong to a project environment. Access follows project membership and requires two-factor sign-in; a secret from another project simply isn't there.

  4. 04Delivered at deploy

    Bound secrets travel with the deployment to the mutexer agent, which passes them to the program as environment variables when it starts.

  5. 05Values checked before they bite

    Leading spaces, stray line breaks, control characters, shell characters and quotes are flagged when a value is saved. Warnings advise; they never block.

  6. 06Deletion that cleans up

    Remove a secret and every program binding that used it is removed with it. Nothing is left pointing at a key that no longer exists.

Managed where the program is built.

Strongroom sits inside the mutexer workspace as its own tab. Engineers add, find and bind secrets without leaving the project or filing a ticket.

Find any secret

Search by MRN, name or key, and copy any field in one click. Values are the one field that needs a Reveal first.

Bind from the device tree

Choose a program's secrets where you configure the program. The list shows what's available and what's already bound.

Registry logins, too

Credentials for Docker Hub, Amazon ECR, Azure and private registries are stored in Strongroom, so pulling a private image never means pasting a password into a build.

Technical specifications.

Encrypted secrets for programs on field-deployed devices.

Encryption at restPer-secret data keys from AWS KMS, XSalsa20-Poly1305 via libsodium
ScopePer project environment
AccessProject members, two-factor sign-in
Plaintext accessExplicit reveal only, never logged
DeliveryEnvironment variables, at deploy
BindingPer program, by secret reference
Key formatLetters, numbers and underscores, not starting with a number
Value sizeUp to 32,768 characters
Value checksWhitespace, line breaks, control characters, shell characters, quotes
Registry credentialsDocker Hub, Amazon ECR, Azure, custom registries
Device runtimemutexer agent
Supported devicesAny Linux-capable device (x86, ARM)

Lock the keys away.
Ship the program.

Add a secret, bind it to a program and deploy. Encrypted from the first save, in every mutexer project.