Let every change to a credential stay on record as its own version, with a password history that no typo and no staff change can erase. Your settings, database connections and deployment values live in one place, so a new hire finds any value right away. When you need to, export the whole vault with one click.
The Agentic Part
An agent working inside your operational systems gets its own restricted account: it reads and changes the same settings your staff use, while stored passwords and documents stay closed to it. A live test confirms this continuously: it can fetch a current setting and cannot reach a stored password. Every change it or a staff member makes creates a new version automatically, the previous one is never lost.
Main Features
- Every save creates a new version, showing exactly which field changed
- Fixed categories for credentials, consistent across the whole vault
- Encryption built into the database, recoverable from an isolated copy
- A strong-password generator built into the browser
- The same version history also covers stored documents
- Clear split between application config and deployment config
- Consistent naming ready for a future central settings system
- Automatic check that keeps both files in sync
- Fixed, traceable process from inventory to final check
- Every application's settings gathered and labelled by environment and source
- Genuine access values only, secrets elsewhere excluded
- Every environment kept as its own record, treated the same way everywhere
- Servers checked directly against what your hosting provider runs
- A tested way to rebuild the whole overview without data loss
- Access rights granted individually, same rules for people and agents
- Ungranted tools stay invisible to the agent
- Proof both ways: live setting fetched, stored password blocked
- Separate areas inside the same store, each with its own, unique labels
- Existing data migrates checked in the background, before cutover
- Applications keep the familiar name; a technical key matches behind the scenes
- Each former list gets a fixed place with a unique assigned number
- One CSV export of the whole vault, current version of each credential
- A separate command-line tool with direct database access
- A passphrase check before any password gets decrypted
- A row-count check that blocks an incomplete export file
Use Cases
- A password used to sit in a spreadsheet, and after a change the old value was gone for good. Now every previous version stays on record, a typo or a staff change no longer costs an account.
- An agent is meant to work inside your operational systems without reaching stored passwords. It gets its own restricted account, and a live test confirms it can read settings but not fetch a password.
- A second customer joins, and the previously continuous credential store gets hard to navigate. It splits into separate areas, with no existing row moving and no live reader noticing anything.
- An audit needs the full credential set as a list. The export button or the command-line tool both write the same CSV row per credential, checked for a matching row count.
What we build for you
- Your own categories and the actual credential records
- Files your project currently uses, and which are in source control
- Exact names your existing deployment already expects
- Values that count as sensitive for your business
- Your actual applications, servers and access details
- Which of your data the agent is allowed to touch
- The actual areas, customers or lists that apply to your business
- Which fields the export must carry for your compliance needs
- Where the exported file is stored once it is generated
