Kept for IT & Security.
The infrastructure has opinions only your veterans can explain. Three films on keeping the knowledge that keeps you up.
All industriesFor executives
The box nobody reboots is a control gap with an owner.
Somewhere in your estate is a system that works because one person remembers why it must never be touched on Tuesdays.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Somebody knows why that firewall rule exists. They left in the spring, and nobody dares remove it.
System ownership and incident decisions live in individuals, which is an operational risk that shows up during an outage.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new admin asks whether rule 41 can go. Kept answers with the reason and the risk, cited to the engineer who set it.
Procedural and system context stays in place through turnover and incidents. Kept. Keep the knowledge behind the work.
Tribal infrastructure knowledge is a finding waiting for an auditor: the legacy job that feeds the ERP, the firewall rule with no ticket, the recovery procedure that exists as one engineer's muscle memory. When that engineer leaves, your continuity plan quietly becomes fiction.
Kept captures what your team knows, in their words, and keeps it as cited memory behind real access control: people see what they are permitted to see, with answers designed to name available sources and make missing evidence clear. Review important answers. Continuity you can evidence, not just assert.
For managers
The runbook is fiction. The truth is on call.
Your incident response works because the same three people always answer. That is not a process. That is luck with a rota.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Somebody knows why that firewall rule exists. They left in the spring, and nobody dares remove it.
You’re the escalation path for access questions because the procedure was never written down.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new admin asks whether rule 41 can go. Kept answers with the reason and the risk, cited to the engineer who set it.
Access questions stop routing through you. Kept. Keep the knowledge behind the work.
Every environment accumulates truths that never reach the wiki: the service that must start second, the alert that lies, the vendor escalation path that actually works. On-call quality depends on who picks up, and cross-training means hoping the veteran enjoys explaining things at 2am.
Kept interviews your engineers about how the estate actually behaves and keeps their answers cited and queryable. The next incident gets the veteran's knowledge without the veteran's phone. You see coverage across the team. It does not score your engineers, ever.
For partners
You fixed it at 2am. It should stay fixed at 2am without you.
Being the person who knows the legacy stack means your phone is part of the disaster recovery plan.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Somebody knows why that firewall rule exists. They left in the spring, and nobody dares remove it.
You inherit a system with no owner and rules with no reasons, and you’re on call for it.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new admin asks whether rule 41 can go. Kept answers with the reason and the risk, cited to the engineer who set it.
Every rule you inherit comes with its reason. Kept. Keep the knowledge behind the work.
Kept talks with you about the systems you actually run and keeps your knowledge in your words. The quirks, the ordering, the fix that works and the one that looks like it works. When it breaks on your night off, the answer that comes up is yours, cited, instead of your ringtone.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in it & security.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a it & security team:
- Questions asked of Kept per week, and the share answered with a source
- The ten most repeated questions, and whether each has a kept answer
- Systems and processes with a kept, cited answer for “how do we use this here”
- Partners with capture on who use the systems in scope, through the whole window
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance