Deliberate access to agent credentials.
We are exploring a dedicated credential service with scoped grants, revocation, and rotation. Delivery methods and security boundaries are still being designed; vault9 is not a replacement for the current run9 or drive9 secret features.
Scope is subject to change. No public release or API is announced.
Choose who may use a credential, and how.
The concept starts with an explicit credential owner, a recipient, and a permitted use. Different delivery methods expose credentials differently, so storage, access, rotation, and revocation need clear boundaries rather than one blanket secrecy guarantee.
1. Identify the credential owner and intended use. 2. Grant access to a defined recipient and scope. 3. Review delivery, rotation, and revocation behavior.
Store. Grant. Deliver.
We are exploring credential management with explicit ownership and exposure rules.
Credential ownership
Explore centralized credential storage and rotation, with clear ownership, retention, and access controls.
Scoped authorization
Explore grants for a specific recipient and purpose. Expiry and revocation semantics, including credentials already delivered, remain to be defined.
Defined security boundaries
Explore delivery methods for different workloads. Whether a process receives the secret value, and where it may persist, depends on the selected method.
Secret features available in separate products.
run9 and drive9 already provide distinct secret features. Their behavior does not imply a shared vault9 integration.
Managed network secrets
Project Secret rules substitute HTTPS headers for allowed hosts on Boxes using managed networking. Normal networking does not apply these rules.
run9 → drive9Vault storage and grants
Store secrets, delegate access, and inject values into command environments. Retrieval and read-only vault mounts can expose values to authorized processes.
drive9 → db9Postgres database
Create and query Postgres databases, with database branching for separate work.
db9 → owl9Session records
Capture and review native transcripts from supported agent runtimes with collection enabled.
owl9 →What credential boundary do you need?
Tell us who should own a credential, who needs to use it, and how it should reach the workload.