PAGES
← all tools
◆ Endpoint Management (UEM/RMM)

PDQ Deploy & Connect

commercial

Free plan: not checked yet

What you can do now

Checking Plays…

Summary

PDQ Deploy & Connect is a commercial endpoint-management server that deploys software, patches third-party applications, runs scripts, and changes configurations on on-premises or VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection.-connected Windows devices, with newer remote administration for Windows and macOS. It is aimed at IT administrators managing fleets rather than security analysts, and its documentation presents it as a central server used with PDQ Inventory; one licence covers both. Packages, schedules, deployment history, device access, and patching are managed centrally, with a 14-day trial available. Its project history shows ongoing releases, including remote shell and live file browsing.

How PDQ Deploy & Connect helps

Which of my devices still need a particular application or update?

targets individual devices or PDQ Inventory collections, deploys the selected package, and reports each deployment’s status and target details; devices that are offline are reached when a heartbeat detects them.

Which third-party applications across my fleet need recurring updates?

schedules package deployments for targeted device groups at chosen times or intervals, using maintained packages from the application library; it does not establish that every device is reachable or that an installation succeeded beyond the deployment results.

Did the software deployment finish successfully on every target?

records current and completed deployment status, the package used, and target details, with optional post-deployment confirmation emails; the result reflects the deployment process rather than independent validation of the application’s behavior.

How do I apply the same configuration change or scripted task to selected Windows devices?

runs custom multistep packages that can install software or execute scripts against chosen machines; the material limits this capability to on-premises or VPN-connected Windows devices.

What happened on a managed device when a deployment failed?

provides an interactive remote shell for running commands and reviewing output in real time, while keeping the user’s screen unobstructed; it does not guarantee that the available output identifies the root cause.

Where is a needed log or script on a live device?

browses and searches the device file system, and lets an administrator retrieve logs or upload scripts without starting a remote desktop session; this applies to the live managed device and does not describe historical file versions.

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities

Built from PDQ Deploy & Connect's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What PDQ Deploy & Connect offers you

  • Built-in AI assistant1
  • Command-line interface1

All capabilities 4 capabilities
Dashboard customization Administrators can show, hide, reorder, and resize dashboard widgets, and access built-in widgets including a most-vulnerable-devices view, a configurable low-disk-space threshold indicator, and an OS patching visualization. 2 releases · first seen Oct 2026
Live File Explorer Lets administrators browse, search, upload, download, and delete files on a managed device's live file system without launching a remote desktop session or interrupting the user. 1 release · 1 other source · first seen Oct 2026
Remote Shell Provides an interactive terminal inside PDQ for running commands and reviewing output in real time on managed Windows and macOS devices without taking over the user's screen. 1 release · 1 other source · first seen Oct 2026

Also counts toward: Command-line interface

AI assistant Uses package, deployment, and device context to explain deployment results, break down output, and suggest targeted diagnostics, with administrator approval required before any action runs on a device. 1 release · first seen Oct 2026

Also counts toward: Built-in AI assistant

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for PDQ Deploy & Connect, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail PDQ Deploy & Connect puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

1 entry

  1. October 20261

    1 entry

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.