Airgap
Product developmentThink about recovery before an agent needs access.
Product and connector development around retained copies, visible backup status and restoration that stays under human control.
01 / The business behind the work
A practical question behind agent access.
Giving an AI agent access to everyday business tools makes another question more urgent: what happens when important information changes or disappears? Airgap is being developed around retained copies and a person deciding what should be restored beside the existing work.
The product thinking starts with the recovery boundary. Backups should remain separate from the credentials available to an agent, and the operator should be able to understand the state of a backup and the options for recovery.
02 / The work in practice
Connect the product to the difficult details.
The engineering work brings together an application, command-line and MCP entry points, connector backup components and browser recovery orchestration. Google connector work includes handling document hierarchy, mail labels and reporting gaps in a run.
Those details matter because different tools expose different kinds of information. A useful recovery experience needs to show incomplete coverage and explain limitations rather than hide them behind a reassuring status label.
Access & accountability
Where control matters.
The recovery direction separates backup credentials from agent access and keeps restoration under human control. Development evidence is not a recovery guarantee.
The commercial purpose
Why it is worth building.
Let businesses consider recovery as part of adopting agents, before an incident makes the question urgent.
A similar challenge in your business?
Let’s talk it throughNext project / Agentic fund operations
An investment team
Give agents useful work, with a clear place for judgement.