More than storage.
Better access habits.
Explore Vault by the work your team needs to do: organise, share, protect and operate.
The right item, at the right moment.
- 01A clear nameRecognise the service
- 02A deliberate collectionKnow where it belongs
- 03A trusted domainCheck before filling
Illustrative planning view · no account connected
Access that has an owner.
- 01PurposeWhat work requires access?
- 02RoleWhat permission is enough?
- 03ReviewWhen should access end?
Illustrative planning view · no account connected
Prepare for the less ordinary day.
- 01RecoveryA lost factor or device
- 02EvidenceA review of access
- 03ContinuityA tested restore
Illustrative planning view · no account connected
Find it quickly.
Use it deliberately.
The small decisions that make a password manager useful every day.
Make the list readable.
Use a consistent naming convention so teammates can distinguish similar services.
What this example means
Fictional labels only. Nothing here stores or reveals a credential.
ServiceDesign workspace
OwnerDesign operations
CollectionCreative tools
Sample context only. No account action is performed.
Begin with a unique value.
Generate a fresh password for each service and check its requirements.
What this example means
The local generator is on the overview. It does not test passwords against a live service.
LengthChoose the service requirement
CharactersCheck accepted symbols
ReuseUse a different value elsewhere
Sample context only. No account action is performed.
Give access a purpose.
And an owner.
Walk through a team handover. The useful question is who needs access, to what, and for how long.
Start with the role.
A new person does not need every credential. Begin with the work they are responsible for.
What this example means
Roles shown here are planning examples. Confirm the actual permissions in your Vault deployment.
PersonNew design teammate
CollectionDesign tools
ReviewConfirm the appropriate role
Sample context only. No account action is performed.
Share a defined collection.
Keep the scope visible as a project changes hands. Review who owns the account as well as who can use it.
What this example means
This preview does not invite anyone, share a password or change a permission.
ProjectAutumn campaign
CollectionCampaign accounts
ReviewOwner, membership and end date
Sample context only. No account action is performed.
Close access deliberately.
Review membership and active sessions, then identify credentials that may need rotation.
What this example means
Removing access cannot erase a secret someone previously copied. Follow your organisation’s offboarding and rotation process.
PersonDeparting teammate
ReviewAccess and active sessions
Follow-upRotate exposed credentials where needed
Sample context only. No account action is performed.
One Vault.
Different moments.
Organise at your desk. Find a login in the browser. Keep unlock decisions on the right device.
Studio login ••••••
Project note ••••••
Service key ••••••
The place to organise.
A central workspace for items, collections and team settings.
Native mobile apps are listed as roadmap. These views do not connect to an account or invoke biometrics.
Check current compatibility ↗Find the right item.
Example account
example.test · sample onlyCloser to the moment of use.
The published Chrome extension offers item search and autofill. Confirm the supported browser and your Vault domain.
Native mobile apps are listed as roadmap. These views do not connect to an account or invoke biometrics.
Check current compatibility ↗Vault remains locked.
Device verification belongs in the actual application.
ILLUSTRATION / NO DEVICE PROMPTAn intentional unlock.
The desktop companion is listed for biometric unlock. Check the supported operating system, hardware and recovery path.
Native mobile apps are listed as roadmap. These views do not connect to an account or invoke biometrics.
Check current compatibility ↗A vault needs
an operating rhythm.
Build the routine before the team depends on it.
01Review access
Assign collection owners and a review cadence. Validate current membership and rotate exposed credentials when necessary.
02Prepare recovery
Review the supported recovery method, keep material securely and test a non-sensitive account. Avoid a single untested recovery dependency.
03Plan a restore
Agree who owns backups and updates. Verify a restore of a non-sensitive environment before trusting the process.
04Know the evidence
Confirm log coverage, retention and export format. A successful sign-in test does not prove every security control.
Eighteen capabilities.
One useful filter.
Public feature descriptions, paired with the practical checks for your deployment.
18 results
DAILY USEVault items
Give each credential a clear home.
Explore
DAILY USEPassword generator
Unique values, shaped to the service.
Explore
DAILY USERecognisable entries
Find the correct domain at a glance.
Explore
APPSChrome extension
Search and autofill near the login form.
Explore
TEAM ACCESSOrganisations
Keep team responsibilities distinct.
Explore
TEAM ACCESSRole-based sharing
Share with a purpose and a scope.
Explore
TEAM ACCESSActivity centre
A starting point for access review.
Explore
SECURITYAudit log
Review the record behind an action.
Explore
SECURITYMulti-factor authentication
Add a second check to sign-in.
Explore
SECURITYClient-side protection
Make key custody part of the review.
Explore
SECURITYRecovery preparation
Plan for a lost factor or device.
Explore
APPSDesktop companion
A deliberate device-unlock step.
Explore
ADMINISTRATIONAdministrative controls
Keep policies and ownership visible.
Explore
ADMINISTRATIONImport and export
Move in carefully. Keep a route out.
Explore
ADMINISTRATIONOnboarding
Introduce the vault with a plan.
Explore
ADMINISTRATIONSettings and profile
Review the account behind the access.
Explore
ADMINISTRATIONSelf-hosting
Choose who operates the service.
Explore
ADMINISTRATIONData ownership
Know how records are stored and restored.
Explore
No matches. Clear the search or choose another group.
Source reviewed 6 September 2026: published Vault catalogue ↗. Availability should be confirmed against the running product.
A little more clarity.
Open a question, or search for what you need.
6 answers
Is every feature available on every plan?
The public catalogue describes a common core, but deployment, identity integrations, support and retention can differ. Confirm the exact plan and release before purchase.
Can I try a password generator here?
The Vault overview includes a local browser generator. It is a standalone utility, not connected to an account or a team policy engine.
Does revoking access erase copied passwords?
No. Review access and active sessions, then rotate credentials that may have been copied or exposed.
Are native mobile applications available?
The published integrations page lists native iOS and Android apps as roadmap. Check current availability before making mobile apps a requirement.
Can Celia read secret values?
The preview demonstrates assistance using permitted metadata, not passwords. Do not put passwords or recovery material in an AI prompt.
How should we evaluate imports?
Use a small non-sensitive sample from the exact source version. Compare fields, collections and attachments before planning a controlled migration.
No matching answers. Clear the search to see all questions.
Keep the decision
moving forward.
Explore the next page or bring your requirements to the Vault team.