TigerTrust Secrets Manager (SM) is a Vault-compatible engine that runs inside the platform — there is no separate server binary to deploy. Clients speak Vault’s HTTP API (/v1/*) directly, so you use the upstream vault CLI or any Vault-compatible SDK.
Unlike CLM (one agent) or PAM (four binaries), SM’s server side lives in the TigerTrust backend. On the client side you install the vault CLI (or vault agent sidecar) and point it at your workspace’s SM URL.

What ships

ComponentRuns onPurpose
SM engineTigerTrust backendKV, transit, PKI, database dynamic secrets, wrapping
vault CLIAny workstation or CI runnerStandard HashiCorp CLI, works against /v1/*
vault agentAny host / podRenders secrets into files via templates, handles lease renewal

1. Install the vault CLI

brew tap hashicorp/tap
brew install hashicorp/tap/vault

2. Point vault at TigerTrust and log in

export VAULT_ADDR=https://api.tigertrust.io
vault login -method=oidc          # opens browser
# or, for scripted use:
export VAULT_TOKEN=<workspace token from Settings → Secrets Manager>

vault kv get   secret/prod/db/password
vault kv put   secret/prod/db/password [email protected]
vault kv list  secret/prod
vault write    database/creds/prod-postgres     # dynamic short-lived creds
vault write    pki/issue/web-server common_name=web.example.com
Supported v1 paths cover KV v1/v2, transit, PKI, database, AppRole, wrapping, and the standard sys/* endpoints (sys/mounts, sys/policy, sys/health, sys/wrapping/*).

3. Install vault agent (for workloads)

vault agent runs alongside a workload and renders secrets to files or env vars — the workload never needs to know about SM. It handles token/lease renewal, template re-rendering on secret change, and signalling the child process. It ships with the same vault binary.
sudo mkdir -p /etc/vault-agent
sudo tee /etc/vault-agent/agent.hcl <<'EOF'
vault {
  address = "https://api.tigertrust.io"
}

auto_auth {
  method "approle" {
    config = {
      role_id_file_path   = "/etc/vault-agent/role_id"
      secret_id_file_path = "/etc/vault-agent/secret_id"
    }
  }
  sink "file" {
    config = { path = "/run/vault/token" }
  }
}

template {
  source      = "/etc/vault-agent/db.env.tpl"
  destination = "/run/secrets/db.env"
}
EOF

sudo tee /etc/systemd/system/vault-agent.service <<'EOF'
[Unit]
Description=Vault Agent (TigerTrust SM)
After=network-online.target
[Service]
ExecStart=/usr/local/bin/vault agent -config=/etc/vault-agent/agent.hcl
Restart=always
[Install]
WantedBy=multi-user.target
EOF

sudo systemctl daemon-reload
sudo systemctl enable --now vault-agent
Example template (/etc/vault-agent/db.env.tpl):
DATABASE_URL=postgres://{{ with secret "database/creds/prod-postgres" }}{{ .Data.username }}:{{ .Data.password }}{{ end }}@db.internal:5432/app
The agent renews the lease before it expires and re-renders the template when the secret changes.

4. Auth methods on the client side

Which auth method you use depends on where the client runs:
WhereRecommended authVault command
Developer laptopBrowser OIDC loginvault login -method=oidc
CI runner (GitHub Actions, GitLab CI)JWT / OIDC federationvault write auth/jwt/login role=… jwt=$TOKEN
Kubernetes podServiceAccount JWTvault write auth/kubernetes/login role=my-role jwt=$SA_TOKEN
Generic Linux hostAppRolevault write auth/approle/login role_id=… secret_id=…
Cloud VMCloud IAM (AWS/Azure/GCP)vault login -method=aws
Configure the auth method under Settings → Secrets Manager → Auth Methods.

SM overview

Engines, secrets, leases, and the compat surface.

Rotation policies

Scheduled rotation for KV values and database roles.

Policies

Vault-syntax HCL policies scoped to the workspace.

Access methods

OIDC, JWT, AppRole, Kubernetes, cloud IAM.