Air-Gapped Mercurial: A Discipline of Control and Integrity

Air-gapped deployment is not theory here—it’s the rule. No internet. No shortcuts. No silent background updates phoning home. You control every bit that enters and every bit that leaves. When you run Mercurial in this kind of locked-down environment, the smallest mistake can cause hours or days of lost productivity.

Air-gapped Mercurial setups demand discipline. You need a full clone of your repositories ready to work without network access. This means mirroring every dependency, every hook, every extension you rely on. Forget to bring one, and the build breaks. Bring something wrong, and you risk corrupting history across your team.

The process starts by preparing a complete mirror of your Mercurial repositories in a secure, connected staging area. Pull and verify all commits. Run integrity checks. Export with hg bundle to create portable archive files you can move across the gap. On the secure side, import with hg unbundle and verify again. Automation helps, but validation is key. In an air-gapped system, there is no “just pull again.”

Extensions are where teams often stumble. Many Mercurial extensions fetch code or metadata from outside sources. In an air-gapped deployment, every extension must be self-contained and bundled locally. Audit them. Remove or replace anything with unresolvable dependencies.

Security in this environment is not just about keeping threats out. It’s about ensuring every bit of code is exactly as intended. Version control integrity checks and cryptographic verification with PGP or SHA256 hashes are standard practice. You need a clear, enforceable procedure for signing and verifying everything that crosses the air gap.

Air-gapped deployment of Mercurial is not slower—it’s cleaner. It forces you to know exactly how your version control works and what it needs to function. You get a repository that is predictable. Traceable. Controlled down to the byte.

If you want to skip the painful trial-and-error and see an air-gapped Mercurial workflow that just works—mirrors, bundles, imports, and verifications included—check out hoop.dev. You can see it live in minutes.