In development · now taking pilot firms
Court-ready PDFs that never leave the device
AirGap Utils is an offline PDF toolkit for law firms, healthcare practices and financial businesses. It gets documents ready for court e-filing and upload portals with no servers, no login and no network connections. Your IT team can check that for themselves.
- No vendor servers
- No accounts or login
- No telemetry
- Windows and macOS first
The product
The PDF work a filing needs, in one place
Add files once, by choosing them or dropping them anywhere in the window. They land in one tray, and the tools that apply are offered beside it. Each label shows what is built and what is on the way.
Make it ready
Drop the files, pick a size cap (2, 5, 10 or 25 MB, or your own) and switch on searchable text or metadata removal. You see what fails, press one button, and get a compliant copy.
Compress to a size cap
Only the heavy pages, usually scans and photos, are rebuilt. Text stays searchable. If a cap cannot be met at readable quality, the file is split into parts that each fit, and the app says so.
Merge, split and reorder
Merge works in the current build. Version 1.0 adds a thumbnail grid for reordering, rotating and deleting pages, and splitting by range, every N pages, or size cap.
Redaction that removes the text
Redacted pages are rebuilt from pixels with the boxes burned in, so nothing sits underneath to copy out. Scrubbing writes a new document, leaving metadata and edit history behind.
A checklist with every file
Each output is opened again and checked against its target: size, page count, searchable text, and no text under any redaction. A failed check blocks saving. The checklist saves alongside the file.
PDF/A and on-device OCR
PDF/A output for the courts that require it, and searchable text for scanned pages using the operating system's own OCR engine. Scans are read on the device, like everything else.
One engine behind every tool
Every tool is the same five steps with different settings. That means one code path to harden and test, and one behavior for your staff to learn.
- 1
Read
Open the file on the device
- 2
Keep or rebuild
Page by page, only what must change
- 3
Write
A new document, never over the original
- 4
Verify
Re-open it and check it against the target
- 5
Report
A checklist of what was checked
Security
Three promises, each one testable
Privileged files, health records and financial documents should not pass through someone else's server to be compressed. These are the three properties the product is built around.
Zero egress
The app makes no network connections.
Our code calls no networking API: no telemetry, no crash reporter, no update check. A guard installed at startup refuses any connection the app tries to open, and the operating system blocks them where it can.
Zero residue
No copy of a document is kept after it is closed.
Page images and text exist only in memory while a job runs. On close, buffers are cleared and scratch files deleted. A sweep at every launch removes anything a crash left behind.
Verified output
Every output is checked before it can be saved.
The result is opened again and tested against the target you picked. For redaction that includes searching the output for the redacted terms. A failed check blocks saving.
Zero egress is enforced and tested in the current build. Zero residue and the full verification checklist arrive with version 1.0.
Stated plainly
- Your original file stays wherever you keep it. The app never overwrites it, and cannot protect it.
- With no telemetry, we do not see crashes. A user who hits a problem sends a diagnostic bundle saved on their own machine.
- Compressed and redacted pages are rebuilt as images with a text layer. They stay searchable, but are no longer vector.
- The app reports that a file meets the checks you selected. It does not promise that a court or portal will accept it.
For IT
A kit you hold and deploy yourself
Nothing is hosted by us and nothing phones home. Each release is a versioned, signed kit that your IT team or managed service provider rolls out with the tools already in use.
What is in the kit
| Target | In the kit | How you deploy it |
|---|---|---|
| Windows | A signed installer with silent switches, and an .msix, for x64 and arm64 | Intune, an RMM tool, Group Policy, or by hand |
| macOS | A signed, notarized .pkg | Jamf, Intune, Kandji, or by hand |
| Every kit | Your license file, a signed SHA-256 manifest, an SBOM and third-party notices, release notes, and a short deployment guide | The guide shows how to verify zero egress yourself |
Windows and macOS ship first. iPhone, iPad and Android follow, distributed privately to your organization through Apple Business Manager and managed Google Play.
Do not take our word for it
Windows
The app refuses its own connections, and the installer adds a Windows Firewall rule blocking its outbound traffic.
You check
The firewall rule list, and your EDRmacOS
App Sandbox with no network entitlement, so the operating system refuses connections.
You check
codesign -d --entitlements - on the appUpdates cannot arrive over a network the app never touches, so an update is a new kit. You decide when it rolls out. Security fixes ship as out-of-band kits.
Licensing
Licensed to your organization, not to each login
Built for firms of 50 to 200 people. You sign one annual contract for an agreed head count and receive one signed license file. The app verifies it on the device and never contacts us.
- One license file for the whole organization
- Annual contract, with head count agreed once a year
- Checked offline: no activation, no login, no seat server
- No install counting. Your own device management is the record
- A warning before expiry and a grace period after it
- Updates arrive as new signed kits
Pilot program
We are choosing our first pilot firms
Version 1.0 is being built now. Pilot firms tell us which courts and portals they file with, how they deploy software, and their mix of Windows and Mac. That shapes what ships first.
Pricing follows head count. Tell us yours when you get in touch.
Request a pilotQuestions
What buyers and IT teams ask first
Short answers. If yours is not here, ask it in the form below.
Can we use it today?
Not in production yet. The current build adds files through one tray, merges PDFs and runs a self-test of the PDF engine and the network guard. Version 1.0 adds the ready check, compression to a size cap, split and reorder, redaction and scrubbing, for Windows and macOS. Pilot firms get builds first.
How do we know nothing leaves the device?
You check it yourself. On macOS the app is sandboxed with no network entitlement, which you can read with codesign. On Windows the installer adds a firewall rule blocking the app's outbound traffic, which shows up in your rule list and your EDR. The deployment guide in each kit walks through it.
Will a court accept the files it produces?
The app tells you a file meets the checks you selected: under the size cap, text searchable, metadata removed. Court and portal rules differ and change, so it never claims a filing is guaranteed to be accepted. Tell us where you file and we will make sure the targets cover it.
How do updates work with no network?
An update is a new signed kit, delivered to your IT team. They deploy it when they choose, the same way as the first one. The app shows a notice when its build is getting old.
Do you see our documents or how we use the app?
No. There are no vendor servers, no accounts and no telemetry, so we never hold your documents or any usage data. The cost is that we do not see crashes either. If something goes wrong, a user can send us a diagnostic bundle saved on their own machine.
What about single sign-on, audit logs or pushed policy?
Anything that needs a server of ours is out of scope by design. Where your own device management can provide it, it can. Items such as an audit log and managed policy are on the list for when a customer asks.
Does it run on phones?
Windows and macOS come first, because that is where filings are prepared. iPhone, iPad and Android follow, mainly for scanning, and are distributed privately to your organization.
Request a pilot
Tell us how your firm files
A few details help us answer usefully the first time. We reply by email, from a person.
- What we will ask next: which courts or portals you file with, and how software reaches your machines.
- What you get: early builds for Windows and macOS, and a say in what ships first.
- What this form does: emails your answers to us. This site sets no cookies and loads no trackers. See the privacy note.