Move team vault items into projects
Connect
SPIRITT
OpenBaoOpenBao
Keys stay locked. Work ships.
Every SPIRITT workspace comes with an OpenBao vault. SPIRITT stores the keys your projects need in the workspace vault and hands them to apps, jobs and deployments only at the moment of use. Values never land in code, logs or chat.
What you can do with OpenBao.
Keys used, never shown
A credential is supplied to the one command or workload that needs it and is never echoed into reports, logs or conversations.
Scope that fits your team
Built-in integrations like Kubernetes, GitLab and sign-in realms can be shared across your organization's workspaces or kept to one when sibling teams must not use them.
Secrets wired into deployments
Apps in your Kubernetes namespace read their keys straight from the vault, so production secrets never sit in manifests or images.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace. Its OpenBao vault is ready from the first minute.
02
Store your keys
Share the API keys and credentials your projects need. SPIRITT stores each one in your workspace vault.
03
Delegate an outcome
Ask SPIRITT to build the integration, job or app that needs those keys. It uses them securely and reports results, never values.
Hand over a mission.
Choose a mission. Make it yours.
Put OpenBao to work.
Every key in its place
Questions
OpenBao, with SPIRITT.
01What is OpenBao in SPIRITT?+
It is the secure vault built into every SPIRITT workspace. Your platform integrations and the custom API keys you share are stored there, and SPIRITT reads them only when a job, app or command actually needs them.
02Will my keys ever show up in chat or logs?+
No. SPIRITT supplies a credential to the single command or workload that needs it and keeps values out of reports, logs and conversations. Status checks read metadata only, never the secret itself.
03What is the difference between workspace and organization scope?+
Built-in integrations such as Kubernetes, GitLab and sign-in realms can be shared with every workspace in your organization or kept inside one workspace. Keys you share for a project live in that workspace's vault.
04Can my deployed apps read secrets from the vault?+
Yes. Apps in your Kubernetes namespace receive credentials synced from the workspace vault as Kubernetes secrets, so production keys stay out of manifests, images and repositories.
05Can SPIRITT connect apps that have no built-in integration?+
Yes. SPIRITT builds a direct API integration for the service, stores its credentials in the vault and runs the integration as a job, app or workflow you can reuse.
06What happens if a credential is missing?+
SPIRITT reports exactly what failed, such as a missing record or a denied path, by name only. It never falls back to a different scope or instance and never prints a value while diagnosing.