Product walkthrough
From an unowned key to a recorded rotation.
A secret can be safe in your vault while its owner and next deadline are unclear. See how KeyGuardRail keeps that work visible to your team.
Recorded in an example workspace with fictional data. Silent video with English descriptions; a full text walkthrough follows.
Read the full walkthrough
Find the gap
The example workspace contains three credentials. A payments API key has no accountable owner and is due for rotation in four days. Its secret value remains in the provider.
Assign responsibility
Open the Payments API key record, select Jordan as the accountable member, and save. The record holds the provider, environment, owner, lifecycle dates and rotation policy. It has no secret-value field.
Plan the work
Set the planned rotation to tomorrow. Planning records the intended work; it does not move the existing deadline or count as a completed rotation.
Rotate in the provider
Your team performs the actual rotation in its provider or vault. That step is outside this recording. In this fictional example, Jordan completes it earlier than planned, on the recording date, before continuing.
Record completion
Choose the completion date and select Mark rotated. KeyGuardRail records the date and calculates the next deadline from the record’s 90-day rotation policy.
Check the history
The record history shows the owner change, planned rotation and recorded completion, with the actor and date. This is team-recorded evidence, not independent verification from the provider.
Review the inventory
Back in the inventory, Jordan owns the payments credential and the next rotation is due in 90 days. No secret value was copied into KeyGuardRail.
Ready to evaluate the fit? Review supported integrations, compare plans, or follow the setup guide.