PDQ Deploy and Inventory vs. ManageEngine Endpoint Central for Air-Gapped Patch Management

The biggest question is how often your machines disappear from the network. PDQ Deploy is primarily push-based, so a computer that is offline when a deployment runs can miss the update. Its Heartbeat schedules and Inventory collections can help: the deployment can trigger when a machine returns, and Inventory can identify systems missing a particular cumulative update. For an isolated environment, you would export packages from the connected console and import them into the offline one. Make sure the licensing tier includes the scheduling and inventory features you need.

PDQ Deploy and Inventory is straightforward and works well for manually managed patch workflows. Its per-administrator pricing can also be attractive if you have a large number of devices. The export/import process supports moving packages between a connected console and an air-gapped console, but I would verify that the exact third-party applications and update sources you need are supported.

Endpoint Central uses an agent, so machines can check in after reconnecting and receive whatever approved patches are waiting. Its disconnected setup generally involves downloading the patch content on the internet-connected side and transferring the patch repository into the closed network. That workflow may fit your environment more naturally, although the interface can feel clunky and configuration takes some getting used to.

I would run a small trial of both products using a few machines that stay offline for a week or two. Then reconnect them and see whether they catch up automatically, how much manual package handling is required, and how clearly each product reports failures. That test will probably matter more than the feature comparison, especially since remote support and vulnerability scanning are not your primary requirements.