My Emacs machine has never touched the internet.

Working with Emacs in an air-gapped environment is not a nostalgic throwback. It’s a deliberate choice. Isolation means control. No incoming data you didn’t ask for. No hidden telemetry. No forced updates breaking your workflow. Just you, the code, and a whitelisted set of trusted files. In a world of constant connectivity, this is freedom.

Running Emacs air-gapped starts with preparation. Before you shut the door to the network, you load your environment with everything it will ever need: packages, themes, documentation, and tools. Every dependency is downloaded, verified, and archived. You burn your init scripts into muscle memory. Then you pull the plug.

Package management is the hardest part. The solution is to mirror and cache every package you trust. Store them locally so you can install and reinstall without hitting external servers. Use package.el with an offline archive, or switch to straight.el with a pre-populated repo. Store docstrings, man pages, and org-mode references in the same vault. With this setup, your Emacs session never needs the internet again.

Security improves in an air-gapped Emacs environment. No code leaks, no supply chain attacks, no unexpected network calls. Compliance becomes straightforward. Auditing gets faster. The workflow runs quietly, without popups reminding you to update. Every change you make to your configs is intentional. Every plugin you run has been vetted.

Performance changes too. Without network hooks, startup speeds shrink. Idle CPU cycles stay idle. The memory footprint is predictable. You aren’t just faster because Emacs is fast — you’re faster because there’s nothing else in the room.

Air-gapped setups do not mean you stop learning or evolving. The flow is simple: test package updates in a connected sandbox, freeze the working set, then deploy them offline. The loop is controlled, repeatable, and safe. It’s version control for your editor and your workflow itself.

If you want to see how fast and secure developer environments can be when controlled end-to-end, hoop.dev builds it live in minutes. Spin it up. Test it yourself. Then decide if you want to stay plugged in. Or not.