PDQ Connect publishes its pricing, a genuine advantage in a category where NinjaOne, ConnectWise, and Kaseya all require sales conversations before revealing cost. Three per-device annual tiers: Basic at $12/device/year, Plus at $18/device/year, and Premium at $28/device/year. All tiers require a minimum of 100 devices billed annually. A 14-day free trial covers up to 250 devices with no credit card required.
The published rates make PDQ Connect one of the easier products to budget for in the patch management category. The variables that change the real bill are tier selection, the 100-device minimum's impact on smaller teams, volume discounts for larger deployments, and whether the team eventually needs capabilities (monitoring, Linux patching, PSA) that PDQ Connect does not include and that require a second product.
Editorial policy: How we review software · How rankings work · Sponsored disclosure
Use this PDQ Connect pricing page to understand commercial fit, rollout assumptions, and where pricing conversations need more detail.
The Basic tier at $12/device/year covers device inventory, prebuilt and custom packages, custom fields, and basic reporting for Windows and macOS. This tier requires manual deployment triggering: there is no automated scheduling. For teams that want to patch on their own schedule and do not need remote desktop or RBAC, Basic is the right starting point. At the 100-device minimum, Basic costs $1,200/year.
The Plus tier at $18/device/year is where most production teams land. It adds automated deployments (scheduled patching without manual intervention per cycle), remote desktop, role-based access control, and custom scanners. The automation alone justifies the $6/device uplift for any team managing more than a handful of endpoints. Manual deployment triggering does not scale. At 100 devices, Plus costs $1,800/year. At 500 devices, $9,000/year.
The Premium tier at $28/device/year adds vulnerability scanning with CVSS and PDQ risk scoring, one-click CVE resolution, API access for custom integrations, and priority support. The vulnerability scanning is the primary differentiator: it turns PDQ Connect from a patching tool into a basic vulnerability remediation tool.
At 100 devices, Premium costs $2,800/year. At 500 devices, $14,000/year. Teams that do not need vulnerability scanning or API access should stay on Plus. The $10/device uplift from Plus to Premium is significant at scale and only justified if CVE visibility is a real operational requirement.
The full PDQ suite (Deploy, Inventory, and Connect together) is available as a custom bundle for teams that need both on-premises and cloud management during a migration. Bundle pricing is not published and requires contacting sales. If the team is running Deploy today and plans to migrate to Connect, ask for bundle pricing that covers the transition period rather than paying for both products at full list price.
Pricing source: official pricing page, verified 2026-03-17.
PDQ Connect pricing should be evaluated in the context of rollout scale, admin ownership, and the commercial metric that drives expansion cost over time.
Pricing pages should connect what the vendor charges to what implementation scope, support needs, and operational complexity mean for total ownership. Use this page to frame vendor conversations before final procurement.
For teams managing 100 to 300 Windows endpoints where patching and software deployment are the primary requirements, Plus at $18/device/year is the most defensible tier. It covers automated patching, remote desktop for occasional troubleshooting, and RBAC for teams with multiple administrators. The total cost, $1,800 to $5,400/year, is competitive against Automox PatchOS ($12/endpoint/year but custom pricing above that tier) and significantly cheaper than NinjaOne's estimated $1.50–$3.75/device/month base rate.
For teams under 100 devices, the 100-device minimum inflates the effective cost. A team managing 50 endpoints on the Plus tier pays $1,800/year: an effective rate of $36/device/year, double the published price. Action1's free tier (up to 200 endpoints) or Automox PatchOS ($1/endpoint/month with no published minimum) may be more cost-effective in this scenario. Do not pay for 100 devices to manage 50.
For teams managing 500+ devices, request a volume discount quote from PDQ. Published rates are list prices. Larger deployments should be negotiated. Compare the volume-discounted PDQ Connect quote against Automox and ManageEngine Patch Manager Plus at equivalent scale before committing.
For teams that need monitoring alongside patching, model the combined cost of PDQ Connect plus a separate monitoring tool against NinjaOne or Atera, which include both in a single platform. PDQ Connect's lower per-device rate is only a savings if the team does not end up paying for monitoring separately.
The 100-device minimum means teams managing fewer than 100 endpoints pay more per device than the published rate. Calculate the annual cost divided by actual managed devices, not the published per-device rate, to get the true unit cost. If the effective rate exceeds $20/device/year at the Basic tier, consider Action1's free tier or Automox as alternatives.
Basic lacks automated deployments, so most production teams need Plus at minimum. Price the evaluation at $18/device/year (Plus), not $12/device/year (Basic), unless the team is genuinely willing to trigger every deployment manually. The headline $12 rate is the entry point, not the realistic operating cost for most teams.
PDQ publishes initial rates, but clarify whether pricing changes at renewal and whether device count reductions mid-contract are permitted. Most per-device vendors lock the device count for the annual term: over-provisioning in year one is cost that does not come back.
PDQ Connect does not include monitoring, alerting, ticketing, PSA, or Linux patching. If the team needs any of these, a second product is required. Model the combined cost of PDQ Connect plus the additional tool against alternatives that include those capabilities natively (NinjaOne for monitoring, Atera for PSA, or Automox for Linux) before assuming PDQ Connect's lower per-device rate translates to lower total cost of ownership.
PDQ Connect publishes three annual tiers: Basic at $12/device/year, Plus at $18/device/year, and Premium at $28/device/year. All tiers require a minimum of 100 devices. Volume discounts are available for larger deployments but are not published. Contact PDQ sales for a quote above 100 devices.
At the base tier, PDQ Connect Basic ($12/device/year) matches Automox PatchOS ($1/endpoint/month, or $12/year). PDQ Connect Plus ($18/device/year) is more expensive than Automox PatchOS but includes remote desktop and RBAC that Automox charges separately for in higher tiers. The key difference: Automox supports Linux, PDQ Connect does not. If Linux coverage is needed, Automox wins regardless of price.
No permanent free tier. PDQ Connect offers a 14-day free trial for up to 250 devices with no credit card required. For a permanently free option, Action1 covers up to 200 endpoints with no feature restrictions and no time limit.
All PDQ Connect tiers require billing for at least 100 devices per year, regardless of how many devices you actually manage. At the Basic tier, that means a $1,200/year minimum. Teams managing fewer than 100 endpoints should calculate the effective per-device cost and compare against alternatives without minimums before committing.
PDQ offers a bundled suite that includes PDQ Deploy, PDQ Inventory, and PDQ Connect for teams that need both on-premises and cloud management. Bundle pricing is not published. Contact PDQ sales for a custom quote. The bundle is most relevant for teams migrating from Deploy to Connect who need both products during the transition.
These are the public references, pricing pages, and editorial inputs used to support this page. Readers should still confirm final commercial or product details directly with the vendor when the decision becomes real.
pricing · verified Mar 17, 2026
Official pricing pagePDQ Connect pricing reference
Use the next pages below to move from pricing back into category context, product detail, alternatives, comparisons, and glossary terms.
Return to the category hub when the team needs broader buying context before narrowing further.
Check which tools in this category offer free tiers, trials, or community editions.
Check the commercial model, official pricing notes, and what to validate before procurement treats the pricing as settled.
Use alternatives when the product is credible but the buying team still needs stronger pressure-testing against competing fits.
Use comparison pages once the candidate set is specific enough for direct vendor-to-vendor evaluation.
Use glossary terms when the product page raises category language that needs a clearer operational definition.
