AirGap sits in front of the Tether gate and guards every action that carries a file. A file is taken apart, stripped of anything active, and rebuilt clean on the far side — and nothing is released without a permit decision on what that file actually is.
There is no straight line from the outside world into the secure zone. Every file travels one way through five stages — and the original never makes the trip.
Files arrive from the untrusted side — email, uploads, shared drives. Everything is suspect on arrival.
One way in. There is no path back — nothing inside the zone can reach out through the crossing.
Several independent checks: what the file claims to be vs. what it really is, what active content hides inside it, and whether it is already known-bad.
Macros, scripts, hidden metadata and external links are stripped — and the file is rebuilt clean. The original bytes never cross.
Only the rebuilt, cleared copy arrives — and only after the gate’s permit decision allows the release.
Tap a file and follow it through the crossing. Every step of every file’s journey is written to a tamper-evident audit log — change one entry and the chain no longer verifies.
Choose a file above to walk it through the crossing.
The licensee sets the policy. For each kind of finding, choose what happens: strip it and let the clean file through, flag it for a human, or block it outright — and the whole layer can be switched on or off. Try the controls:
Tether is the deterministic permit gate for AI agents: every action needs a signed permit, checked before it executes. AirGap extends that same discipline to the files an action carries.
Before a cleaned file is released, AirGap presents what the file is — its identity, what was found, what was removed — and the gate issues or denies the permit for that release. No permit, no release.
The gate was never meant to wash files. AirGap does that work in front of it, so what crosses is only ever the rebuilt, disarmed copy — never the original, never anything active.